企业架构 － 企业架构成熟度模型（EAMM）
本文更新版本已挪至 http://www.zhoujingen.cn/blog/4126.html
--------------------------
我认为任何工作都可以找到一种方法，而每种方法在实践时由于对方法掌握的熟练度总是会存在一个成熟度模型。通过成熟度模型，可以很好的发现我们现在的位置，以及发展的方向，也就是明确了在使用方法时的as-is和to-be。
企业架构有什么成熟度模型呢？在《NASCIO-EAMM》文档中专门对企业架构成熟度模型进行了描述，本篇将对它的主要内容进行整理一下，现在理解还不行，就翻译了一些简单的，先放这，以后也好再仔细看看。
评估的几个方面
EAMM从以下几个方面来对不同级别进行描述:
- Administration – 治理角色与职责
- Planning – 企业架构开发路标以及实现计划
- Framework – 流程和模板
- Blueprint – 实际的标准和规范集合
- Communication – 交流与发布EA和详细蓝图
- Compliance（一致性） – 遵循发布的标准、流程和其它EA元素，文档化流程并且能够跟踪变化
- Integration – touch-points of management processes to the EA
- Involvement – 整个组织对EA的支持
EA LEVEL 0 - NO PROGRAM
没有文档化的架构框架，虽然解决方案已经开发并实现了，但是并没有公认的标准和最佳实践的指导，组织完全依赖于独立个人贡献者的知识。
- Administration
没有架构治理 - Planning
没有开发企业架构的方法 - Framework
没有架构流程和模板 - Blueprint
IT技术标准没有文档化 - Communication
主要管理人员和机构人员不知道企业架构是什么 - Compliance
组织内没有统一的流程 - Integration
没有企业集成的程序 - Involvement
- There is no program in place for Enterprise Architecture awareness
- 多个独立部门或个人分别在解决同一个问题
EA LEVEL 1 - INFORMAL PROGRAM
定义了基本的企业架构和标准。大家对这些步骤达成基本一致，但是并不一定会遵守并执行，基本上是在非正式的情况下使用。这个状态下组织仍旧依赖于独立个人贡献者的知识。
- Administration
The need for committees to define the standards and processes has been identified - Planning
- Need for Enterprise Architecture has been identified
- EA活动没有正式化和结构化
- Framework
- 个性化和非正式的流程，流程不一致
- 在业务和技术上没有统一的架构流程
- Blueprint
非正式和非一致性的文档化业务驱动、技术标准等等 - Communication
- The need to create greater awareness about EA has been identified
- 在EA流程改善上很少沟通
- Compliance
- 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
- Integration
- 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
- Involvement
- 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
EA LEVEL 2 - REPEATABLE PROGRAM
基本架构和标准已经制定并跟踪验证，开发时作为可重用方法，产品和组件遵守标准，需求得到一致认同，对流程绩效也进行了度量。
- Administration
- A need for Architecture Governance has been identified
- 开始制定清晰的角色和职责
- Governance committees are starting to form
- Planning
- 组织已经开始开发企业架构愿景
- 组织开始标识EA任务和资源需求
- 组织决定使用一个方法论，并且开始开发一个EA计划
- Framework
- 编制了基本的EA程序
- 流程计划并跟踪
- The organization is beginning to reuse methods for capturing critical EA information
- Blueprint
- 明晰了业务驱动和策略信息
- The need for an EA repository for storage and dissemination of the captured EA information has been identified
- Communication
- The need for Enterprise Architecture is being communicated to Senior Management
- EA awareness activities are beginning to emerge or be developed
- Compliance
The organization has begun to develop a compliance process to ensure that projects and enhancements are consistent with EA standards - Integration
The need for integration to the EA Program Framework (Architecture Lifecycle Processes) has been identified - Involvement
- 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
对于企业架构团队，如果一开始没有EA意识，术语Level 0，我所在团队目前应该就属于这个级别，Level 2是我们的第一个目标。这个级别还有好几级，更多内容参考你可能需要的在线电子书中的TOGAF。
推荐：你可能需要的在线电子书
我的新浪围脖： http://t.sina.com.cn/openexpressapp 敏捷个人sina围裙：http://q.t.sina.com.cn/135484
欢迎转载，转载请注明：转载自周金根 [ http://zhoujg.cnblogs.com/ ]