The TOGAF ADM: Phases, Objectives, Inputs, Outputs, and Application
The ADM at a glance
The ADM runs from the Preliminary Phase through Phases A to H, with Requirements Management at the center. Preliminary establishes architecture principles, the Architecture Board, the tailored method, and tools. Phase A (Architecture Vision) defines scope, stakeholders, concerns, and a high-level vision, and produces the Architecture Vision and Statement of Architecture Work. Phase B develops Business Architecture; Phase C develops Information Systems Architectures (data and application); Phase D develops Technology Architecture. Phase E (Opportunities and Solutions) groups work into projects; Phase F (Migration Planning) produces the implementation and migration plan; Phase G (Implementation Governance) provides architecture contracts and compliance oversight; Phase H (Architecture Change Management) manages change requests and can trigger another cycle.
Objectives, inputs, and outputs
Each phase has a purpose, inputs drawn from earlier phases and the repository, and outputs that feed later phases. Remember the logic: B, C, and D describe architectures; E and F convert architecture into programmes and plans; G governs delivery; H watches for change. Requirements Management is continuous and does not sit in the cycle.
Traps
Candidates confuse Phase E and Phase F: E selects and groups work, F schedules and resources it. Phase G is often mistaken for project management; it is architecture governance of implementation. Phase H is not closing the project but managing change. The Statement of Architecture Work is confirmed in Phase A, not Phase G; the architecture contract belongs in Phase G.
Worked example
If a scenario asks where an architecture contract is agreed, answer Phase G, using outputs from Phases E and F. Rule of thumb: A defines, B–D describe, E–F plan, G governs, and H changes.