企業架構 － 企業架構成熟度模型（EAMM）

我認為任何工作都可以找到一種方法，而每種方法在實踐時由于對方法掌握的熟練度總是會存在一個成熟度模型。通過成熟度模型，可以很好的發現我們現在的位置，以及發展的方向，也就是明确了在使用方法時的as-is和to-be。

EAMM從以下幾個方面來對不同級别進行描述:

Administration – 治理角色與職責

Planning – 企業架構開發路标以及實作計劃

Framework – 流程和模闆

Blueprint – 實際的标準和規範集合

Communication – 交流與釋出EA和詳細藍圖

Compliance（一緻性） – 遵循釋出的标準、流程和其它EA元素，文檔化流程并且能夠跟蹤變化

Integration – touch-points of management processes to the EA

Involvement – 整個組織對EA的支援

　　沒有文檔化的架構架構，雖然解決方案已經開發并實作了，但是并沒有公認的标準和最佳實踐的指導，組織完全依賴于獨立個人貢獻者的知識。

Administration

沒有架構治理

Planning

沒有開發企業架構的方法

Framework

沒有架構流程和模闆

Blueprint

IT技術标準沒有文檔化

Communication

主要管理人員和機構人員不知道企業架構是什麼

Compliance

組織内沒有統一的流程

Integration

沒有企業內建的程式

Involvement

There is no program in place for Enterprise Architecture awareness

多個獨立部門或個人分别在解決同一個問題

　　定義了基本的企業架構和标準。大家對這些步驟達成基本一緻，但是并不一定會遵守并執行，基本上是在非正式的情況下使用。這個狀态下組織仍舊依賴于獨立個人貢獻者的知識。

The need for committees to define the standards and processes has been identified

Need for Enterprise Architecture has been identified

EA活動沒有正式化和結構化

個性化和非正式的流程，流程不一緻

在業務和技術上沒有統一的架構流程

非正式和非一緻性的文檔化業務驅動、技術标準等等

The need to create greater awareness about EA has been identified

在EA流程改善上很少溝通

The need for compliance to standards has been identified

Compliance is informal and unstructured

Compliance cannot be measured effectively, because processes and procedures are not consistent across areas and/or projects

The need to document common functions that integrate with an EA Program has been identified

Projects and purchases are typically done in isolation, resulting in costly purchases and redundant development and training requirements

The organization has identified a need to make staff throughout the enterprise aware of the benefits and concepts of Enterprise Architecture

EA awareness efforts are informal and inconsistent

Some groups are unsupportive of the efforts and may cause unrest in the organization

　　基本架構和标準已經制定并跟蹤驗證，開發時作為可重用方法，産品群組件遵守标準，需求得到一緻認同，對流程績效也進行了度量。

A need for Architecture Governance has been identified

開始制定清晰的角色和職責

Governance committees are starting to form

組織已經開始開發企業架構願景

組織開始辨別EA任務和資源需求

組織決定使用一個方法論，并且開始開發一個EA計劃

編制了基本的EA程式

流程計劃并跟蹤

The organization is beginning to reuse methods for capturing critical EA information

明晰了業務驅動和政策資訊

The need for an EA repository for storage and dissemination of the captured EA information has been identified

The need for Enterprise Architecture is being communicated to Senior Management

EA awareness activities are beginning to emerge or be developed

The organization has begun to develop a compliance process to ensure that projects and enhancements are consistent with EA standards

The need for integration to the EA Program Framework (Architecture Lifecycle Processes) has been identified

The organization has begun to develop plans for EA educational sessions and materials to increase the awareness and understanding of the EA concepts and processes

EA concepts are beginning to be introduced and more consistently discussed in normal day-to-day meetings

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