Per the TOGAF Standard, the Requirements Management phase is a CONTINUOUS phase: it sits at the centre of the ADM cycle diagram and operates throughout ALL the other phases, not as a step in the Preliminary → H sequence. Every phase feeds requirements into it and draws requirements from it, so requirements stay consistent and governed across the whole architecture lifecycle.
Requirements Management is TOGAF's answer to how requirements are maintained consistently across a potentially long and iterative architecture process.
- ▸🔄 Continuous process — runs throughout ALL ADM phases simultaneously
- ▸🎯 Central position — appears at the CENTER of the ADM wheel (not as one of the outer phases)
- ▸📦 Repository — stores, manages, and makes requirements available to all phases
- ▸🔁 Bidirectional — phases both STORE requirements into it AND RETRIEVE requirements from it
- ▸⚖️ Consistency — resolves requirement conflicts across phases
- ▸📊 Prioritization — maintains relative priority of requirements as they evolve
- ▸🔍 Traceability — traces each requirement to its source and to the architecture components that address it
Every ADM phase has a specific store/retrieve interaction with Requirements Management. Understanding these interactions is key for scenario questions:
Requirements Management is NOT a phase — it runs continuously throughout ALL ADM phases. It acts as a central repository: phases STORE requirements into it, and phases RETRIEVE requirements from it. It ensures requirements remain consistent as the architecture evolves through each phase.
Architecture Vision requirements — stakeholder concerns become high-level requirements
Requirements Management is NOT a phase — it is a continuous process. It appears in the center of the ADM wheel. Every ADM phase interacts with it. It does not produce an Architecture Definition Document or an Architecture Vision — it manages the requirement repository. When asked "how many ADM phases are there?" = 9 (Preliminary + A–H). Requirements Management is NOT counted as a phase.
A common source of confusion — TOGAF Requirements Management is NOT the same as requirements engineering (eliciting, analyzing, specifying requirements).
- ▸📝 Requirements Engineering: eliciting requirements from stakeholders, analyzing them, writing specifications — done by each phase as part of its own work
- ▸🗄️ Requirements Management (TOGAF): storing, versioning, prioritizing, and making available requirements that have been identified by any phase
- ▸📌 Each phase does its OWN requirements work (Phase B identifies business requirements) — then STORES those requirements in the Requirements Management repository
- ▸🔍 The repository does NOT generate requirements — it manages them
- ▸⚠️ Exam: "Requirements Management elicits requirements from stakeholders" = FALSE
Requirements Management performs specific activities throughout the ADM. These activities are what makes it a "management" function, not just a storage system.
- ▸📥 Identify and document requirements (received from each phase)
- ▸🔢 Prioritize requirements against business goals and constraints
- ▸⚖️ Resolve conflicts between requirements from different phases
- ▸🔄 Manage requirement changes — update requirements as architecture evolves
- ▸🔗 Maintain traceability — from stakeholder concern → requirement → architecture component
- ▸📤 Make requirements available to phases that need them
- ▸📊 Archive superseded requirements for audit trail