Objectives
- Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases
- Manage architecture requirements identified during any execution of the ADM cycle or a phase
- Ensure that relevant architecture requirements are available for use by each phase as the phase is executed
Steps
- 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 requirements 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
Inputs
- 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).
Outputs
- Changed requirements
- Requirements Impact Assessment, 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).