隨筆檔案

The Architect (dedicated non-programming technical decision maker and problem solver for business):

架構(gòu)師（專用非編程技術(shù)決策者，業(yè)務(wù)問題解決者）

1. Has outdated programming knowledge and experience, loss of touch with modern development approaches and practices.                                                                                                                                                                                             過時的編程知識和經(jīng)驗，對現(xiàn)代的軟件開發(fā)方式和實踐缺乏關(guān)注。   


2. Don’t program and don’t know much about evolving system internals, but makes key technical decisions. Often has completely irrelevant and unreal picture what is happening with the system.                                                                       不進行軟件開發(fā)，對系統(tǒng)內(nèi)部知之甚少，但卻要做出關(guān)鍵的技術(shù)決策。對系統(tǒng)經(jīng)常有完全無關(guān)和虛幻的映像（不太會翻譯這句）。


3. Tends to complex, premature and generic solutions when the system is still in infancy and nothing is clear. Applies latest modern buzzword technologies as SOA, MDA, SaaS, Software Factories, etc. which look so beautiful in technical magazines, conferences and CV, but cause unnecessary headache for developers.                                      當系統(tǒng)仍處于起始階段，都還不明晰的時候，常會做出復(fù)雜的，不成熟僅僅通用的決策。使用在技術(shù)雜志、技術(shù)大會和CV上看起來如此美妙的現(xiàn)代最新的口號，諸如SOA，MDA，SaaS，Software Factories等等，只是給開發(fā)人員帶來不必要的頭痛。


4. Plays role of the middleman introducing complexity in coordination and project responsibilities. Represents software team in interactions with business customers reducing communication value for the rest of the team and impacting idea flow.                                                                                                                                                                          以中間人的角色，引入復(fù)雜的協(xié)調(diào)和項目的責(zé)任。代表開發(fā)組與客戶進行交流，屏蔽了其他成員的發(fā)言權(quán)和開發(fā)思想上的交流。（翻譯時候意思懂了，但就是表達不出來）


5. Reduces quality of decisions, which become limited to one perspective; decision making starts lacking diversity, independence and decentralization, which are essential attributes of collective intelligence.                                          決定僅僅局限在某個角度 ，降低了決策的質(zhì)量；最初的決定缺乏多樣性，獨立性和向下兼容，這些都是集體決策的本質(zhì)。                      


6. Creates tension with developers who experience mismatch between grand design and reality. Often continues pushing design decisions until the system becomes overly complex, difficult to change and becomes completely unusable.                                                                                                                                                                                             在缺乏大型設(shè)計和實現(xiàn)經(jīng)驗的開發(fā)者之間制造緊張氛圍。不斷的做出決定，系統(tǒng)變得過度復(fù)雜，難于改變，和應(yīng)用。


7. Secures job and justifies high salary - becomes authoritative center for solving business problems without much input from the team.                                                                                                                                                                            有穩(wěn)定的工作和高薪，成為解決業(yè)務(wù)問題的權(quán)威，但卻從未融入到團隊當中。


8. Causes loss of sense of ownership, motivation and accountability in developers by detaching them from the key architecture decisions.                                                                                                                                                                     把開發(fā)人員排除在關(guān)鍵架構(gòu)決策之外，讓他們?nèi)狈χ鲃有院拓?zé)任感。


9. Concentrates project knowledge and the big picture in one head, limiting (and sometimes preventing) complete understanding for others.                                                                                                                                                                 只精通工程知識和大局一面，對其他方面幾乎一無所知。


10. Contributes to creation of specialized IT verticals that hurt relations with the business.                                                     擅長在縱向?qū)ｉT的IT方面建立聯(lián)系，但同時卻切斷了業(yè)務(wù)上的關(guān)聯(lián)。

            完成該系統(tǒng)后，所完成的后期維護工作中，最大的以部分就是數(shù)據(jù)統(tǒng)計查詢分析功能的完善了。

       系統(tǒng)軟件框架提供了一套報表生成系統(tǒng)來完成數(shù)據(jù)統(tǒng)計查詢的功能。這條報表生成系統(tǒng)可以生成excel和pdf兩種格式的統(tǒng)計報表。

       這個系統(tǒng)使用報表的流程大致為：

       1.每個功能都提供一系列的報表，在軟件中這些報表以二維字符串數(shù)組的數(shù)據(jù)格式保存，每個字符串數(shù)組對象包括該報表的唯一鍵值，報表名稱，報表條件提供頁面以及生成該報表的具體的Java類。

       2.選擇需要生成的報表，系統(tǒng)將該報表的唯一鍵值傳入統(tǒng)一的報表控制類，首先是跳轉(zhuǎn)到生成該報表的條件頁面，按照功能劃分報表的主要原因就是每個功能的報表條件一致，可以使用統(tǒng)一的控制類。

       3.提交條件后，統(tǒng)一的報表控制類會調(diào)用該報表的生成類,這些類需要繼承統(tǒng)一的接口,提供了一個統(tǒng)一的方法，返回數(shù)據(jù)類型為Vector集合的對象，這個Vector對象容器數(shù)據(jù)對象要求為：

     兩個Vector對象，一個為表頭Vector，一個為表體Vector，這兩個Vector對象中存儲的數(shù)據(jù)為字符串數(shù)組對象。

   在具體應(yīng)用中，只要將數(shù)據(jù)填充到字符串數(shù)組中，再依次放入Vector中，報表框架會生成報表。

   這個框架的一個確定就是只能接受字符串數(shù)組對象，如果生成excel格式的報表，無法根據(jù)生成的報表進行計算，必須手動的將數(shù)據(jù)調(diào)整為數(shù)字型。