企業架構 － 組織角色和技能

   　Scrum開發會有PO、Scrum Master和開發團隊三個角色，那麼開發企業架構又是由哪些角色組成的呢？每種角色又需要什麼技能才能夠承擔架構的工作呢？本篇介紹一下在架構開發中角色和技能要求，以便大家在實施TOGAF時知道誰來做，需要具備或提高哪些技能。

　　軟體開發管理就比較複雜，架構開發管理就更複雜了，由于還沒有具體實踐過，暫時還沒有這些内容的深入了解和細化，以下介紹大部分來自于TOGAF的架構能力架構。

　　企業架構師是思想帶頭人、幻想家和行業專家。在大多數公司裡，這是個新的角色，它将項目經理、解決方案架構師和業務分析人員的技能與執行的直覺聯合起來。

　　許多 IT架構師視角的普遍局限是他們是成熟的程式設計人員，并且目光易于局限于内部。雖然，這不完全是架構并設計“全局性”解決方案的障礙，但是，它是“構架”企業環境中不那麼理想的特征。企業架構師可能更加外向，并且善于利用專業的、工作的，甚至與業務所有者、業務上司、同僚和客戶之間的關系來說明、從架構地角度描述，并且幫助執行企業遠景。

　　<b>企業架構師</b>的職責常常與<b>城市規劃者</b>對比，而<b>建築架構師</b>的職責更容易與 <b>IT 架構師</b>角色聯系起來。建築架構師強調其推理的技能，而企業架構師角色常常強調類似于偵探的感應技能。

　　很重要的是，企業架構師扮演架構治理（常常在分類的業務和技術角色之間共享的功能，或者更糟，僅僅被忽略）中的關鍵角色。架構治理是為所有企業和項目架構活動提供環境和架構的粘合劑。

架構委員會（Architecture Board Members）：我感覺類似與IPD的IPMT，由總監級或資深産品專家組成，屬于管理決策層，最好是4－5個固定成員。

架構發起人（Architecture Sponsor）

架構經理（Architecture Manager）

企業架構師（Enterprise Architecture）

業務架構（Business Architecture）

資料架構（Data Architecture）

應用架構（Application Architecture）

技術架構（Technology Architecture）

程式員或項目經理（Program and/or Project Managers）

IT設計師（IT Designer）

其它（And many others）

通用技能（Generic Skills）: 上司力、團隊協作、人際關系等

業務技能和方法（Business Skills &amp; Methods）: 業務案例、業務流程、政策計劃等

企業架構技能（Enterprise Architecture Skills）: 模組化、建構塊涉及、應用和角色設計、系統內建等

程式和項目管理技能（Program or Project Management Skills）:  管理業務變更、項目管理方法和工具等

IT通用知識（IT General Knowledge Skills）: brokering applications, asset management, migration planning, SLAs, etc.

IT技術（Technical IT Skills）: 軟體工程、安全、資料互動、資料管理等

法律知識（Legal Environment）: data protection laws，contract law procurement law, fraud, etc.

　　每種角色對各種技能的要求是不一樣的，為了各自的掌握程度，定義了四種級别：不要求、了解、熟悉、精通

通用技能（Generic Skills）

業務技能和方法（Business Skills &amp; Methods）

企業架構技能（Enterprise Architecture Skills）

程式和項目管理技能（Program or Project Management Skills）

IT通用知識（IT General Knowledge Skills）

IT技術（Technical IT Skills）

法律知識（Legal Environment）

架構師的角色能夠彙總如下：

<b>明白和解釋需求（Understand and interpret requirements）</b>: 參考我的BABOK系列blog

<b>生成有用的模型（Create a useful model）</b>

<b>驗證、提煉和擴充模型（Validate, refine, and expand the model</b>）

<b>管理架構（Manage the architecture）</b>: 在架構開發期間，持續溝通共享架構，并不斷完善架構

有産品設計的技能和經驗（Skills and Experience in Producing Designs）

An enterprise architect must be proficient in the techniques that go into producing designs of complex systems, including requirements discovery and analysis, formulation of solution context,identification of solution alternatives and their assessment,technology selection, and design configuration.

技能面廣，并且對一兩個領域深入（Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines）

An enterprise architect should possess an extensive technical breadth through experience in the IT industry. This breadth shouldbe in areas of application development and deployment, and in the areas of creation and maintenance of the infrastructure to support the complex application environment. Current IT environments are heterogeneous by nature, and the experienced enterprise architect will have skills across multiple platforms, including distributed systems and traditional mainframe environments.Enterprise architects will have, as a result of their careers, skills in at least one discipline that is considered to be at the level of a subject matter expert.

方法驅動（Method-Driven Approach to Execution）

Enterprise architects approach their job through the consistent use of recognized design methods such as the TOGAF ArchitectureDevelopment Method (ADM). Enterprise architects should have working knowledge of more than one design method and be comfortable deploying parts of methods appropriate to the situation in which they are working working. This should be seen in the body ofdesign work the enterprise architect has produced through repeated successful use of more than one design method. Proficiency in methodology use is in knowing what parts of methods to use in a given situation, and what methods not to use.

項目全開發過程的經驗（Full Project Scope Experience）

While enterprise architects are responsible for design and hand-off of the project to implementors, it is vital that they have experience with all aspects of a project from design through development, testing, implementation, and production. This scope of experience will serve to keep enterprise architects grounded in the notion of fitness-for-purpose and the practical nature of system implementation. The impact of full project scope experience should lead the enterprise architect to make better designdecisions, and better inform the trade-offs made in those decisions.

上司力（Leadership）

Communication and team building are key to the successful role of the enterprise architect. The mix of good technical skill andthe ability to lead are crucial to the job. The enterprise architect should be viewed as a leader in the enterprise by the ITorganization, the clients they serve, and management.

個人和專業技能（Personal and Professional Skills）

The enterprise architect must have strong communications and relationship skills. A major task of the enterprise architect is to communicate complex technical information to all stakeholders of the project, including those who do not have a technical background. Strong negotiation and problem-solving skills are also required. The enterprise architect must work with the projectmanagement team to make decisions in a timely manner to keep projects on track.

一個或多個行業經驗（Skills and Experience in One or More Industries）

Industry skill and experience will make the task of gathering requirements and deciding priorities easier and more effective for the enterprise architect. Enterprise architects must understand the business processes of the enterprise in which they work, and how those processes work with other peer enterprises in the industry. They should also be able to spot key trends and correctflawed processes, giving the IT organization the capability to lead the enterprise, not just respond to requests. The mission ofthe enterprise architect is strategic technical leadership.

<b>　　通過上面的技能要求能看出來，架構師就是架構師，要求就是高。一個公司牛人就不多，牛的架構師就更不多了，又要讓大家在一起做一個統一的架構，怪不得企業架構難做啊，繼續努力......</b>

<a href="http://leodesousa.ca/2010/02/enterprise-architects-what-attributes-do-you-look-for/">Enterprise Architects – What attributes do you look for?</a>

 本文轉自 jingen_zhou 51CTO部落格，原文連結：http://blog.51cto.com/zhoujg/518630，如需轉載請自行聯系原作者