Comprehensive Guide to Requirements Management in TOGAF ADM

Introduction

Requirements Management is a critical phase in the TOGAF Architecture Development Method (ADM) that ensures the identification, documentation, and management of architecture requirements throughout the ADM cycle. This dynamic process is central to driving the ADM process and applies to all phases of the ADM cycle. The following guide outlines the objectives, steps, inputs, and outputs for effective Requirements Management.

Objectives and Steps

1. Ensure Sustained Requirements Management Process

Objective: Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases.

Steps:

Identify/Document Requirements: Capture and document all architecture requirements.
Baseline Requirements: Establish a baseline of the identified requirements.
Monitor Baseline Requirements: Continuously monitor the baseline requirements to ensure they remain relevant and up-to-date.
Identify New and Changed Requirements: Regularly identify new requirements and changes to existing requirements. Remove, add, modify, and re-assess priorities as needed.
Record Priorities and Resolve Conflicts: Document the priorities of changed requirements and resolve any conflicts that arise. Generate a Requirements Impact Statement to assess the impact of changes.
Assess Impact of Changed Requirements: Evaluate the impact of changed requirements on current and previous ADM phases.
Implement Requirements from Phase H: Ensure that requirements arising from Phase H are implemented.
Update the Architecture Requirements Repository: Keep the Architecture Requirements Repository up-to-date with the latest requirements.
Implement Change in the Current Phase: Ensure that changes are implemented in the current phase of the ADM cycle.
Assess and Revise Gap Analysis: Review and update the gap analysis for past phases based on the latest requirements.

Inputs and Outputs

Inputs

Populated Architecture Repository:
- Existing architecture documentation and requirements stored in the Architecture Repository.
Organizational Model for Enterprise Architecture:
- The organizational structure and roles involved in the Enterprise Architecture.
Tailored Architecture Framework:
- The customized architecture framework used for the project.
Statement of Architecture Work:
- The approved document that outlines the scope, objectives, and deliverables of the architecture project.
Architecture Vision:
- The comprehensive vision for the future state of the enterprise architecture.
Architecture Requirements Populating an Architecture Requirements Specification:
- Detailed architecture requirements that populate the Architecture Requirements Specification.
Requirements Impact Statement:
- A statement that assesses the impact of changed requirements on the architecture.
Changed Requirements:
- New or modified requirements that need to be managed and implemented.

Outputs

Updated Requirements Specification:
- A revised Architecture Requirements Specification that includes all updated and new requirements.

Key Concepts

Requirements Management: The process of identifying, documenting, and managing architecture requirements throughout the ADM cycle.
Baseline Requirements: The initial set of requirements that serve as a baseline for the architecture.
Requirements Impact Statement: A document that assesses the impact of changed requirements on the architecture.
Architecture Requirements Repository: A centralized repository that stores all architecture requirements and related documentation.
Gap Analysis: The process of identifying and analyzing the gaps between the current and desired states of the architecture.

Conclusion

Requirements Management is a dynamic and continuous process that ensures architecture requirements are effectively managed throughout the ADM cycle. By following the outlined steps and utilizing the necessary inputs, organizations can ensure that relevant architecture requirements are available for use by each phase as it is executed. This process is central to driving the ADM process and ensuring that the architecture remains aligned with business goals and strategic drivers.