Key takeaways
- Remember each phase’s objective rather than a mechanical sequence.
- Requirements are managed throughout the cycle.
- Iteration and governance need to work together.
- PreliminaryPrepare the capability
- AScope and approve the vision
- B · C · DDescribe the four domains and their gaps
- E · FPrepare and finalize the transformation
- G · HGovern implementation and manage change
Requirements Management supports every phase. This thread explains their roles: iteration allows the work to be revisited.
A coherent cycle
The Preliminary Phase prepares architecture capability and the context of the practice. Phase A defines the vision, scope, and authorization for the work. Phases B, C, and D develop Business, Information Systems, and Technology Architectures respectively. Phase E identifies realization opportunities and an initial roadmap; Phase F refines migration planning. Phase G governs implementation, and Phase H manages architecture change.
Requirements Management operates at the center of the method throughout every phase. Phase outputs inform other activities, but the ADM diagram should not be treated as a rigid timetable in which each activity happens only once.
Iterate with clear status
The ADM allows revisiting work, parallel activities, and multiple cycles at different levels of detail. A description may be provisional, revised, and then approved. Approval authorizes its use in a particular context; it does not make it unchangeable. Governance establishes decision points and the conditions for subsequent changes.
- Tailor scope, depth, and pace to the need.
- Reuse suitable repository assets.
- Keep track of requirements, decisions, and versions.
TERMS TO KNOW
The terms, in context.
- ADM
- Architecture Development Method for developing and evolving architecture.
- Iteration
- Revisiting or elaborating work using newly available information.