Source · TOGAF Standard, 10th Edition — ADM: Requirements Management
Why this matters
ADM — Requirements ManagementRequirements are the fuel of the ADM. Requirements Management is drawn at the centre of the ADM diagram because it interacts with every phase — it's the discipline that keeps requirements consistent and traceable as the architecture develops.
The concept
Req Mgmt §ObjectivesRequirements Management is a continuous process, not an ADM phase. Its purpose is to define a process whereby architecture requirements are identified, stored, and fed into and out of the relevant ADM phases. It is the dynamic management of the requirements pool.
What it does — and doesn't
Req Mgmt §ApproachRequirements Management handles the flow and storage of requirements between phases; but it does not dispose of, address, or prioritise requirements — the individual ADM phases do that. Each phase both draws requirements from, and returns updated requirements to, the requirements repository.
How it connects
ADM centreBecause it sits at the centre, every phase (Preliminary, A–H) exchanges requirements with it. Approved requirements are stored in the Architecture Requirements Repository (TGF‑C3). Changes to requirements are a key trigger considered in Phase H.
- Requirements Management is a continuous process at the centre, NOT a numbered phase.
- It manages the flow/storage of requirements but does not address or prioritise them — the phases do.
- Every phase interacts with it — it's not 'done' at one point in the cycle.
- Requirements Management is the continuous central process of the ADM.
- It identifies, stores, and feeds requirements into/out of every phase.
- It manages requirements; the phases address and prioritise them.