What is the ADM?
Architecture Development Method
A method for developing your enterprise architecture
The Architecture Development Method – often referred to by its abbreviation as the ADM – is a detailed step-by-step process for developing or changing an enterprise architecture
The ADM is right at the heart of TOGAF®, in part II of the documentation. Much of the TOGAF documentation covers the ADM, and everything else in TOGAF can be mapped back to the ADM.
The ADM describes covers 10 phases which describe the Architecture Development Cycle.
These steps are:
- Preliminary Phase
- Phase A: Architecture Vision
- Phase B: Business Architecture
- Phase C: Information Systems Architecture
- Phase D: Technology Architecture
- Phase E: Opportunities and Solutions
- Phase F: Migration Planning
- Phase G: Implementation Governance
- Phase H: Architecture Change Management
- ADM Architecture Requirements Management
The Preliminary Phase
The main objectives of the Preliminary Phase are to determine and establish the Architecture Capability desired by the organization.
The Preliminary Phase makes sure there is a well-defined Request for Architecture Work, and that the organization – and Enterprise Architecture team in particular – have everything in place to be able to fulfil that request.Read more
The Requirements Management Phase is central to the ADM – which is why it is shown at the center of the ADM crop circle diagram. This Phase describes a process for Requirements Management, and how that process links to the other phases of the ADM.Read more
The rest of the Phases are arranged in the development cycle to show the ongoing nature of enterprise architectural change.
The TOGAF ADM sets out a recommended sequence for the various phases and steps involved in developing an architecture. Even when an EA team isn’t using the ADM it is likely to follow a similar process to that outlined in the ADM.
As with other TOGAF documentation, you should always adapt the ADM to meet your exact needs.Phase A