Enterprise Architecture-Enterprise Architecture Maturity Model (eamm)

Document directory

• EA level 0-no program
• EA Level 1-informal Program
• EA Level 2-repeatable Program

In my opinion, you can find a method for any job. In practice, there is always a maturity model for each method because of its proficiency in the method. Through the maturity model, we can well find our current position and development direction, that is, to-be and as-is in use.

What maturity model does enterprise architecture have? In the nascio-eamm document, the Enterprise Architecture maturity model is described. This article will sort out the main content of the Enterprise Architecture Maturity Model. If it is not understood yet, it will translate some simple information, put it here first, and then take a closer look.

Evaluation aspects

Eamm describes different levels in the following aspects:

1. Administration-governance roles and responsibilities
2. Planning-enterprise architecture development roadmap and implementation plan
3. Framework-process and template
4. Blueprint-a set of actual standards and specifications
5. Communication-exchange and release of EA and detailed blueprint
6. Compliance-compliant with release standards, processes, and other EA elements, documented procedures and the ability to track changes
7. Integration-touch-points of management processes to the EA
8. Involvement-ea support for the entire Organization

EA level 0-no program

There is no documented architecture framework. Although the solution has been developed and implemented, there is no universally recognized guidance on standards and best practices. organizations rely solely on the knowledge of independent individual contributors.

1. Administration
   No architecture governance
2. Planning
   No method for developing enterprise architecture
3. Framework
   No architecture process and template
4. Blueprint
   It standards are not documented
5. Communication
   The main management personnel and organization personnel do not know what the enterprise architecture is.
6. Compliance
   There is no unified process in the Organization
7. Integration
   No Enterprise Integration Program
8. Involvement
   • There is no program in place for Enterprise Architecture awareness
   • Multiple independent departments or individuals are solving the same problem.

EA Level 1-informal Program

Defines basic enterprise architectures and standards. You have reached a basic agreement on these steps, but they are not always followed and executed. They are basically used in informal situations. In this status, organizations still rely on the knowledge of independent individual contributors.

1. Administration
   The need for committees to define the standards and processes has been identified
2. Planning
   • Need for enterprise architecture has been identified
   • EA activities are not formulated and structured
3. Framework
   • Personalized and informal processes and processes are inconsistent
   • There is no unified architecture process in terms of business and technology.
4. Blueprint
   Informal and non-consistent Documented business-driven, technical standards, etc.
5. Communication
   • The need to create greater awareness about EA has been identified
   • Little communication on ea Process Improvement
6. Compliance
   • The need for compliance to standards has been identified
   • Compliance is informal and unstructured
   • Compliance cannot be measured between tively, because processes and procedures are not consistent between SS areas and/or projects
7. 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
8. 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

The basic architecture and standards have been developed and followed up for verification. As a reusable method during development, products and components comply with the standards, and the requirements are unanimously recognized. The process performance is also measured.

1. Administration
   • A need for architecture governance has been identified
   • Start to define clear roles and responsibilities
   • Governance committees are starting to form
2. Planning
   • The Organization has begun to develop the enterprise architecture vision.
   • The organization begins to identify EA tasks and Resource requirements
   • The organization decides to use a methodology and starts to develop an EA plan
3. Framework
   • The basic EA program is compiled.
   • Process Planning and Tracking
   • The organization is beginning to reuse methods for capturing critical EA Information
4. Blueprint
   • Clarified business drivers and policy information
   • The need for an EA repository for storage and dissemination of the captured EA information has been identified
5. Communication
   • The need for enterprise architecture is being communicated to senior management
   • EA awareness activities are beginning to emerge or be developed
6. Compliance
   The Organization has begun to develop a compliance process to ensure that projects and enhancements are consistent with EA standards
7. Integration
   The need for integration to the EA Program Framework (Architecture Lifecycle processes) has been identified
8. 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

For the enterprise architecture team, if there is no ea awareness at the beginning, the term level 0 should belong to this level currently, and level 2 is our first goal. There are several levels at this level. For more information, seeOnline e-books you may needIn togaf.

Recommended: online e-books you may need

My Sina bib: http://t.sina.com.cn/openexpressapp agile individual Sina apron: http://q.t.sina.com.cn/135484

Welcome to reprint, reprint Please note: Reprinted from Zhou jingen [http://zhoujg.cnblogs.com/]