To provide a process to manage architecture requirements throughout the phases of the ADM cycle

Identify requirements for the enterprise, store them and feed them in and out of the relevant ADM phases, which dispose of, address and prioritize requirements

Identify/document requirements

Baseline Requirements

Monitor baseline requirements

Identify changed requirement; remove, add, modify and re-assess priorities

Identify changed requirement and record priorities; identify and resolve conflicts; generate requirements impact statements

Assess impact of changed requirement on current and previous ADM phases

Implement requirements arising from Phase H

Update the 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).

Changed requirements

Requirements Impact Statement, which identifies the phases of the ADM that need to be revisited to address any changes. The final version must include the full implications of the requirements (e.g., costs, timescales, and business metrics).