Architecture Requirements Management

The process of architecture requirements management is relevant to all phases of the ADM cycle. Requirements Management is a dynamic process. It addresses the identification of requirements for the enterprise, storing them, and then feeding them in and out of the relevant ADM phases. Hence, the ADM chart shows it as central to driving the ADM process.


The objective of this phase is to ensure that Requirements Management process is sustained and operates for all relevant ADM phases - to manage architecture requirements identified, and made available during any execution of the ADM cycle or a phase.


For achieving this goal, TOGAF recommends the following steps

  • Identify/document requirements
  • Baseline requirements
  • Monitor baseline requirements
  • Identify changed requirements; remove, add, modify, and re-assess priorities
  • Identify changed requirements and record priorities; identify and resolve conflicts; generate requirements impact statements
  • Assess impact of changed requirements on current and previous ADM phases
  • Implement requirements arising from Phase H
  • Update the Architecture Requirements Repository
  • Implement change in the current phase
  • Assess and revise gap analysis for past phases


The inputs to the Requirements Management process are the requirements-related outputs from each ADM phase. The first high-level requirements are produced as part of the Architecture Vision. Each architecture domain then generates detailed requirements. Deliverables in later ADM phases contain mappings to new types of requirements (for example, conformance requirements).


The output of the requirements management phase include the Changed requirements; and the Requirements Impact Assessment. The impact assessment identifies the phases of the ADM need to be revisited to address a given changes. The final version of this assessment must include the full implications of the requirements (e.g. costs, timescales, and business metrics).