| ADM Phases | Objectives, Outputs and Outcomes | Essential Knowledge |
| Preliminary Phase | Determine the Architecture Capability desired by the organization Establish the Architecture Capability Delivery of a customized and cohesive Architecture Capability Request for Architecture Work | Organization Context Key Stakeholder Concerns, Preferences, Priorities, and Requirements Detailed options on how to integrate the Architecture Capability in a harmonious way with other frameworks, approaches, etc. |
| Phase A: Architecture Vision | Architecture Capability Assessment, Architecture Vision, and Communications Plan Statement of Architecture Work for permission to proceed to develop a Target Architecture to prove out the Architecture Vision deliverable | Key Stakeholders identified, along with their Concerns, Preferences, Priorities, and Requirements for the initiative/cycle Scope of initiative focused on realizing the Architecture Vision with quantifiable business value |
| Phases B, C, and D: Domain Architectures | Stakeholder-approved Target Architectures, Gaps, and Candidate Architecture Roadmap Components for the Business, Data, Applications, and Technology Domains, Architecture Definition Document, Architecture Requirements Specification | Key Stakeholder Concerns, Preferences, Priorities, and Requirements Architecture Gaps and associated Work Packages |
| Phase E: Opportunities & Solutions | A draft Architecture Roadmap of inter-dependent Work Packages that address the set of Gaps A draft of the Implementation and Migration Plan also outlining the Implementation and Migration Strategy | Key Stakeholder Concerns, Preferences, Priorities, and Requirements An understanding of value to risk and level of effort for each Work Package Dependencies between the Gaps and Work Packages |
| Phase F: Implementation and Migration | An approved Architecture Roadmap An approved Implementation and Migration Plan containing a set of projects containing respective objectives, constraints, required resources, and start and finish dates | Key Stakeholder Concerns, Preferences, Priorities, and Requirements Available Resources for each Projects |
| Phase G: Implementation Governance | Ensure conformant Implementation Projects Perform appropriate Architecture Governance functions for the projects, including registering any implementation-driven architecture Change Requests Successful projects that realize their targeted business value | Key Stakeholder Concerns, Preferences, Priorities, and Requirements Purpose of and constraints on the implementation team: Scope, Gaps, Architecture Requirement Specification document, Implementation Governance Model and associated Architecture Contracts |
| Phase H: Architecture Change Management | Ensure that the architecture development cycle is maintained. Ensure that the Architecture Governance framework is executed. Ensure that the Enterprise Architecture Capability meets current requirements. Identification of alternative Courses of Action to start developing needed Target Architectures | Gaps in Value Realization across the Architecture Landscape Changes to Key Stakeholder Concerns, Preferences, Priorities, and Requirements |
| Requirements Phase | Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases. Manage Architecture Requirements identified during any execution of the ADM cycle or a phase. Deliver Requirements Impact Assessments Ensure that relevant Architecture Requirements are available for use by each phase as the phase is executed | Key Stakeholder Concerns, Preferences, Priorities, and Requirements Gaps in Value Realization across the Architecture Landscape |
Menu