Comprehensive Guide to TOGAF ADM Architecture Requirements Management Deliverables

Introduction

The Architecture Requirements Management phase is a dynamic process that addresses the identification, documentation, and management of architecture requirements throughout the ADM cycle. This phase ensures that relevant architecture requirements are available for use by each phase as it is executed. The following guide explains the key deliverables required to be completed within this phase and provides steps to complete them.

Deliverables

1. Architecture Requirements Specification

Objective: Specify the requirements for the architecture, including functional and non-functional requirements.

Description: The Architecture Requirements Specification document outlines the detailed requirements for the architecture. It includes functional requirements (what the architecture should do) and non-functional requirements (how the architecture should perform).

Steps to Complete:

Identify Requirements:
- Engage Stakeholders: Work with stakeholders to understand their needs and expectations.
- Document Functional Requirements: Specify what the architecture should do to support business goals.
- Document Non-Functional Requirements: Specify how the architecture should perform, including performance, security, and scalability requirements.
Consolidate Requirements:
- Combine Requirements: Combine all identified requirements into a single document.
- Review Requirements: Ensure that the requirements are complete, accurate, and aligned with business goals.
- Prioritize Requirements: Assign priorities to the requirements based on their importance and impact.
Document Specification:
- Include All Requirements: Ensure that the document includes all functional and non-functional requirements.
- Get Approval: Present the Architecture Requirements Specification to stakeholders and obtain approval.
Communicate Specification: Share the Architecture Requirements Specification with the Enterprise Architecture team and other relevant stakeholders.

2. Requirements Impact Assessment

Objective: Assess the impact of changes on the architecture requirements.

Description: A Requirements Impact Assessment is an evaluation that determines the impact of changes on the architecture requirements.

Steps to Complete:

Identify Changes:
- Gather Input: Collect information on the proposed changes to the architecture.
- Document Changes: Create detailed descriptions of the proposed changes.
Conduct Impact Assessment:
- Evaluate Impact: Determine the impact of the proposed changes on the architecture requirements.
- Document Findings: Create a detailed report of the Requirements Impact Assessment findings.
Communicate Assessment:
- Review Assessment: Ensure that the Requirements Impact Assessment is complete, accurate, and aligned with business goals.
- Get Approval: Present the Requirements Impact Assessment to stakeholders and obtain approval.
- Communicate Assessment: Share the Requirements Impact Assessment with the Enterprise Architecture team and other relevant stakeholders.

Key Concepts

Architecture Requirements Specification: A document outlining the detailed requirements for the architecture, including functional and non-functional requirements.
Requirements Impact Assessment: An evaluation that determines the impact of changes on the architecture requirements.

Conclusion

The Architecture Requirements Management phase is essential for ensuring that relevant architecture requirements are available for use by each phase as it is executed. By completing the key deliverables—Architecture Requirements Specification and Requirements Impact Assessment—organizations can ensure that their architecture development process is aligned with business goals and strategic drivers. This phase sets the foundation for successful architecture development and deployment, driving business value and transformation.