The Architecture Development Method (ADM)
The ADM at a glance
The ADM is the core of TOGAF: an iterative process of ten phases with Requirements Management at the centre, touching every phase. The Preliminary Phase establishes the Architecture Capability - principles, governance, tools, tailoring. Then:
- A Architecture Vision - scope, stakeholders, vision, capability assessment, Statement of Architecture Work.
- B Business, C Information Systems (Data and Application), D Technology - each produces baseline and target descriptions plus a gap analysis.
- E Opportunities and Solutions - work packages, transition architectures, outline roadmap.
- F Migration Planning - finalised roadmap and Implementation and Migration Plan with costs, schedule, resources.
- G Implementation Governance - architecture contracts and compliance reviews.
- H Architecture Change Management - monitor change, decide whether to re-enter at A or return to a lower phase.
Traps: Requirements Management is drawn as a central box but is not a phase - no letter, no gate. Phase E is not detailed project planning; it identifies work packages and transition architectures. Phase F is where the roadmap and plan are finalised. Phase G governs conformance during implementation, not the decision to implement. Phase H does not implement change; it manages the request and routes it. Iteration is legitimate and expected: after D a team may loop back to B, and the whole cycle repeats per architecture level.
Rule of thumb: A answers why and who, B what, C what information, D on what technology, E how could we, F when and at what cost, G are we doing it right, H what has changed.