The Architecture Development Method is a proven, iterative and repeatable way to develop and manage architectures. It runs through a Preliminary Phase and Phases A to H, with Requirements Management sitting in the middle.
Also called Architecture Development Method.
Read more: TOGAF Standard
In the Ultra Transcenders books
Each book explains ADM in context, with comparison tables and the common traps.
Terms in this definition
- MANAGE
A Unity Catalog privilege allowing a principal to grant and revoke access on an object, hand over its ownership and drop it, all without being the owner. It gives no data access by itself and is not part of
ALL PRIVILEGES. - Agents (classic) API
First-generation Foundry Agent Service API, based on threads, messages and runs. It is deprecated, replaced by conversations and responses, and retires on 31 March 2027.
- Preliminary Phase
The opening phase of the ADM readies the organisation: here the Architecture Capability is set up, the framework is adapted to fit and the Architecture Principles are agreed.
- Requirements Management
Sitting at the core of the ADM and never stopping, this process looks after architecture requirements and keeps them on hand for all phases.
Related terms
- Fundamental Content
The heart of the Standard: a set of six documents running from introductory core concepts through the ADM, its techniques and how to apply it, to architecture content and building and governing an EA capability.
- Request for Architecture Work
Issued to the architecture organisation by the sponsoring organisation, this document kicks off an ADM cycle and feeds into Phase A.