Study guide

6.3 Requirements Management: Central Flow, Impact Analysis & Traceability

TOGAF Enterprise Architecture Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction to TOGAF & Enterprise Architecture Concepts

1.1 Overview of TOGAF Standard 10th Edition & Enterprise Architecture Concepts 1.2 The Structure of the TOGAF Standard (Easily Navigated Body of Knowledge) 1.3 Core Concepts: Enterprise, Architecture, Deliverables, Artifacts, and Building Blocks 1.4 TOGAF Certification Paths & the OGEA-101 Exam Plan

2 Chapter 2: ADM Foundation & Preliminary Phase

2.1 The Architecture Development Method (ADM) Cycle & Requirements Management 2.2 Preliminary Phase: Scope, Principles, and Architecture Capability Setup 2.3 Tailoring the ADM & Applying Iteration / Architecture Levels 2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

3 Chapter 3: ADM Architecture Vision & Business Architecture

3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition 3.2 Business Architecture Scope, Strategy & Capability Mapping 3.3 Phase B: Business Architecture Inputs, Steps, Outputs & Artifacts 3.4 Business Scenarios & Value Stream Modeling

4 Chapter 4: ADM Information Systems Architectures (Phase C)

4.1 Information Systems Architectures Overview & Phase C Strategy 4.2 Phase C Data Architecture: Principles, Data Models & Governance 4.3 Phase C Application Architecture: Logical Components, Services & Interfaces 4.4 Data and Application Integration, Migration & Interoperability

5 Chapter 5: ADM Technology Architecture & Solution Realization (Phases D, E, F)

5.1 Phase D: Technology Architecture, Platform Services & Infrastructure 5.2 Phase E: Opportunities and Solutions & Initial Implementation Strategy 5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization 5.4 Transition Architectures & Implementation Dependencies

6 Chapter 6: ADM Governance, Change & Requirements Management (Phases G, H)

6.1 Phase G: Implementation Governance & Architecture Compliance 6.2 Phase H: Architecture Change Management & Driver Monitoring 6.3 Requirements Management: Central Flow, Impact Analysis & Traceability 6.4 Architecture Contracts, Dispensations & Compliance Reviews

7 Chapter 7: BDAT Architecture Domains Deep-Dive

7.1 Business Architecture Domain: Functions, Processes & Value Streams 7.2 Data Architecture Domain: Data Entities, Storage & Data Management 7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns 7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

8 Chapter 8: Architecture Content — Content Framework, Enterprise Metamodel & Artifacts

8.1 Architecture Content Framework Overview & Deliverables vs Artifacts vs Building Blocks 8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs) 8.3 The Enterprise Metamodel: Core Concepts, Entities & Attributes 8.4 Architecture Catalogs, Matrices & Diagrams (Visual Representation) 8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

9 Chapter 9: Architecture Governance, Capability & Maturity

9.1 Architecture Governance Framework & The Role of the Architecture Board 9.2 Establishing an Architecture Capability & Organizational Structure 9.3 Architecture Skills Framework, Roles & Competency Levels 9.4 Architecture Maturity Models & Capability Assessments

10 Chapter 10: Enterprise Continuum, Reference Models & Key Techniques

10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning 10.2 Technical Reference Model (TRM) & Integrated Information Infrastructure Reference Model (III-RM) 10.3 Core EA Techniques: Gap Analysis, Interoperability, Risk, Capability-Based Planning & Architecture Patterns

6.3 Requirements Management: Central Flow, Impact Analysis & Traceability

Key Takeaways Explain This Topic AI

Requirements Management operates at the center of the TOGAF ADM, dynamically interfacing with every phase from Preliminary through Phase H.

The process consists of 5 core steps: Identify, Store, Implement, Monitor, and Identify Changed Requirements.

The Requirements Repository acts as the authoritative central store for business, architectural, and technical requirements with comprehensive metadata.

Requirements Impact Analysis evaluates how changes in business requirements ripple across baseline architectures, target designs, and active projects.

Requirements Traceability Matrices map bidirectional line-of-sight from high-level business drivers down to ABBs and SBBs.

Last updated: August 2026

6.3 Requirements Management: Central Flow, Impact Analysis & Traceability

In the visual representation of the TOGAF Architecture Development Method (ADM) cycle, Requirements Management occupies the central hub around which all phases (Preliminary through Phase H) revolve. This visual positioning is intentional: Requirements Management is not a static phase that occurs at a single point in time. Rather, it is a dynamic, continuous process that operates in parallel with every phase of the ADM.

Every phase of the ADM both consumes existing requirements and generates new or refined architectural requirements. Business needs evolve, technical constraints emerge during Phase G implementation, and market shifts occur during Phase H operations. The Requirements Management process provides the disciplined framework required to capture, analyze, store, validate, prioritize, and track these requirements across the entire architecture lifecycle.

Distinction Between Requirement Categories

To manage requirements effectively, TOGAF distinguishes between different levels of abstraction:

Business Requirements: High-level goals, business drivers, strategies, and operational needs defined by enterprise stakeholders (e.g., "Reduce customer onboarding time to under 5 minutes").

Architecture Requirements: Technical and structural specifications derived by enterprise architects to satisfy business goals (e.g., "Identity service must support OAuth 2.0 / OIDC with automated sub-second token validation").

Solution / System Requirements: Detailed functional and non-functional specifications consumed by software engineering and infrastructure teams during solution delivery (e.g., "Redis cluster configured with multi-region replication").

Requirements Management specifically focuses on maintaining line-of-sight between Business Requirements and Architecture Requirements .

The 5 Core Steps of the Requirements Management Process

TOGAF defines a structured 5-step process for managing requirements throughout the ADM: +-------------------------------------------------------+

  • | 1. IDENTIFY REQUIREMENTS |
  • | - Elicit from stakeholders & ADM phase outputs |
  • +-------------------------------------------------------+
  • |
  • v
  • +-------------------------------------------------------+
  • | 2. STORE REQUIREMENTS |
  • | - Catalog in central Requirements Repository |
  • +-------------------------------------------------------+
  • |
  • v
  • +-------------------------------------------------------+
  • | 3. IMPLEMENT REQUIREMENTS |
  • | - Feed into current ADM phase architecture design |
  • +-------------------------------------------------------+
  • |
  • v
  • +-------------------------------------------------------+
  • | 4. MONITOR REQUIREMENTS |
  • | - Track fulfillment during Phase G & Operations |
  • +-------------------------------------------------------+
  • |
  • v
  • +-------------------------------------------------------+
  • | 5. IDENTIFY CHANGED REQUIREMENTS |
  • | - Assess impact & trigger phase/ADM updates |
  • +-------------------------------------------------------+
  • Detailed Step Walkthrough

Identify Requirements: Capture requirements during Phase A (Vision), Phase B (Business), Phase C (Data/App), Phase D (Tech), and ongoing Phase G/H activities.

Store Requirements: Record validated requirements in the central Requirements Repository with mandatory metadata attributes (source, priority, rationale, owner, architectural domain).

Implement Requirements: Supply stored requirements to active ADM phases for incorporation into baseline and target architecture models, candidate solutions, and Architecture Contracts.

Monitor Requirements: Continuously track requirement status during solution implementation (Phase G) and operational governance (Phase H) to verify proper delivery.

Identify Changed Requirements: Detect changes in business environment, regulatory rules, or technical constraints. Perform impact analysis and determine whether to update the current phase or submit a Change Request in Phase H.

The Requirements Repository

The Requirements Repository is the authoritative store within the TOGAF Architecture Repository dedicated to cataloging all enterprise architectural requirements. A well-structured repository maintains key metadata attributes for every requirement:

Metadata Attribute Description & Purpose

Requirement ID Unique alphanumeric identifier for tracking (e.g., REQ-SEC-004 ).

Statement Clear, unambiguous description of the required capability or constraint.

Source / Stakeholder Business unit, executive sponsor, or regulation originating the requirement.

Architectural Domain Categorization across Business, Data, Application, Technology, or Security.

Priority MoSCoW scale (Must have, Should have, Could have, Won't have) or numeric weight.

Status / State Identified, Approved, In Architecture Design, Implemented, Verified, Retired.

Mapped ABBs / SBBs Links to specific Architecture and Solution Building Blocks fulfilling the requirement.

Requirements Impact Analysis

When new requirements emerge or existing requirements change mid-ADM cycle, architects must execute a Requirements Impact Analysis . The purpose of impact analysis is to evaluate how a requirement change ripples across earlier ADM decisions, target blueprints, and active projects.

Key questions answered during Impact Analysis:

Does this requirement change alter the agreed Architecture Vision (Phase A)?

Which target domain models (Phases B, C, D) are invalidated or modified?

Does the change disrupt the current Architecture Roadmap or Transition Architectures (Phases E, F)?

Does the change break active Architecture Contracts in Phase G?

Is a new ADM cycle required, or can the change be absorbed into the active phase?

Requirements Traceability & The Traceability Matrix

Traceability is the capability to trace a requirement bidirectionally—forward from business goal to technical implementation, and backward from technical asset to business justification. Traceability ensures that no technical component is built without a business rationale, and no business requirement is left unfulfilled.

The Requirements Traceability Matrix

A Requirements Traceability Matrix maps line-of-sight linkages across architectural abstractions: Business Goal ---> Business Capability ---> Arch Requirement ---> Architecture Building Block (ABB) ---> Solution Building Block (SBB)

Business Goal Capability Architecture Requirement Mapped ABB Mapped SBB

Accelerate Digital Checkout Omni-channel Payment Processing Must support tokenized single-click credit card authorization Payment Gateway ABB Stripe API Integration Module

Ensure Data Privacy Compliance Customer Data Protection PII must be encrypted at rest with AES-256 and keys rotated annually Data Encryption Service ABB AWS KMS & HashiCorp Vault

Through rigorous traceability, Enterprise Architecture guarantees transparency, simplifies audit reviews, and streamlines impact assessment when change occurs.

Loading diagram... Central Requirements Flow Across ADM Phases