EA Development Process

The Enterprise Architecture Development process has been adapted from the TOGAF ADM.

This is the process for the development of the Enterprise Architecture itself.
Based on the TOGAF Architecture Development Method (ADM) the Enterprise Architecture Development process defines a process for developing the Enterprise Architecture Framework and its contents (blueprints).
The Enterprise Architecture Development Process ensures that the different architecture viewpoints are integrated to meet the business and IT needs of the organisation.

Step Phase Description
1 Enterprise Architecture Framework Define Enterprise Architecture framework, meta model, deliverables, viewpoints, structure, and processes.
2 Architecture Strategy and Vision Define Principles, Goals, Objectives, Standards, Strategies and Vision for the organisation.
3 Process Architecture Develop a target state Process Architecture, with Business Service Model, Business Process Models and Workflow Models. Update current state Process Architecture.
4 Information Architecture Develop a target state Information Architecture representing Knowledge, Information and Data from Business Process, Application, and Technology viewpoints. Update current state Information Architecture.
5 Applications Architecture Develop a target state Application Architecture. Update current state Application Architecture.
6 Technology Architecture Develop a target state Technology Architecture. Update current state Technology Architecture.
7 Organisation Architecture Update Current Technology Architecture.
8 Opportunities and Solutions Identify opportunities for change and further development of the target state enterprise architecture.
9 Migration Planning Develop the Enterprise Architecture Roadmap and migration plan. Prioritise enterprise architecture work. Propose new programmes and delivery projects.
10 Implementation Governance Provide architectural oversight of the software delivery projects, from a governance and compliance perspective.
11 Architecture Change Management Establish procedures for managing changes to the enterprise architecture. Harvest Solution Architecture models from completed and closed projects to update the current state Enterprise Architecture
12 Architecture Demand Management Managing architecture requirements, including topics, issues and gaps.
13 Value Management Managing the value and performance of the Enterprise Architecture with metrics and measurement.


It will not be possible to develop the Enterprise Architecture all at once.

The Enterprise Architecture development process phases will be repeated for each piece of Architecture work (Architecture Requirements, Topics, Gaps, etc.) being worked on.
Each cycle, around the main Enterprise Architecture development process phases, is known as an Iteration.

Phases 1 and 2 are repeated on a less frequent basis, only if required.
Each iteration is driven by the currently agree scope and context, usually aligned to the scope of the current portfolio of delivery projects, EA Requirements and Questions.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License