Study guide

11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict

TOGAF Enterprise Architecture Practitioner OGEA-103

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Mechanics & Foundation Overview

1.1 OGEA-103 Exam Structure, Gradient Scoring & Open-Book Strategy 1.2 The TOGAF Standard 10th Edition Structure & Core Concepts 1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains 1.4 The Context for Enterprise Architecture: Purpose, Capability, Security, and the Digital Enterprise

2 Chapter 2: Preliminary Phase & Establishing the EA Capability

2.1 Preliminary Phase Objectives, Inputs, and Activities 2.2 Scope of the Enterprise and Defining the Architecture Footprint 2.3 Establishing Architecture Governance, Frameworks, and Tools

3 Chapter 3: Architecture Vision & Stakeholder Management (Phase A)

3.1 Phase A Objectives, Request for Architecture Work, and Scope Definition 3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map 3.3 Business Scenarios Technique for Problem Definition and Requirements Elicitation 3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval

4 Chapter 4: Business Architecture (Phase B)

4.1 Phase B Objectives, Steps, and Business Modeling Approaches 4.2 Business Capabilities, Capability Mapping, and Assessment 4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping 4.4 Business Architecture Artifacts, Gap Analysis, and Architecture Definition Document Updates

5 Chapter 5: Information Systems Architectures — Data Architecture (Phase C)

5.1 Phase C Data Architecture Objectives, Approach, and Data Principles 5.2 Conceptual, Logical, and Physical Data Models and Data Management 5.3 Data Entity/Business Function Matrix, Data Architecture Gap Analysis, and Interoperability Requirements

6 Chapter 6: Information Systems Architectures — Application Architecture (Phase C)

6.1 Phase C Application Architecture Objectives, Approach, and Baseline vs. Target First 6.2 Application Portfolio Rationalization, Component Modeling, and Application Integration 6.3 Application/Organization Matrix, Application Gap Analysis, and Boundary Definitions

7 Chapter 7: Technology Architecture (Phase D)

7.1 Phase D Objectives, Cloud & Modern Platforms, and Technology Principles 7.2 Technology Standards, the Standards Library, Platform Services, and Infrastructure Modeling 7.3 Technology Gap Analysis, Non-Functional Requirements, and Reference Models

8 Chapter 8: Opportunities and Solutions (Phase E)

8.1 Phase E Objectives, Consolidated Gap Analysis, and Work Package Formulation 8.2 Architecture Building Blocks (ABBs) to Solution Building Blocks (SBBs) Transition 8.3 Transition Architectures, Incremental Delivery, and Dependency Analysis 8.4 Architecture Roadmap Development and Trade-Off Analysis 8.5 Business Transformation Readiness Assessment and Risk Management

9 Chapter 9: Migration Planning (Phase F)

9.1 Phase F Objectives, Stakeholder Collaboration, and Governance Alignment 9.2 Business Value Assessment, Cost-Benefit Analysis, and Risk/Feasibility Scoring 9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps

10 Chapter 10: Implementation Governance (Phase G)

10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off 10.2 Architecture Contracts: Purpose, Types, Timing, and Stakeholder Commitments 10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists

11 Chapter 11: Architecture Change Management (Phase H) & Requirements Management

11.1 Phase H Objectives, Drivers of Architecture Change, and Value Monitoring 11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes 11.3 Ongoing Governance, Retirement of Solutions, and Maintenance vs. New ADM Cycle 11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict

12 Chapter 12: Architecture Governance, Boards, and Dispensations

12.1 Architecture Governance Framework, Organizational Roles, and RACI Matrix 12.2 Architecture Board Structure, Federation, Responsibilities, and Meeting Operations 12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking 12.4 Architecture Principles, the Decision Log, and Resolving Principle Conflicts

13 Chapter 13: Architecture Content Framework & Architecture Repository

13.1 The TOGAF Content Framework and Enterprise Metamodel 13.2 Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs vs SBBs) 13.3 Architectural Views, Viewpoints, Stakeholder Concerns, and ISO/IEC/IEEE 42010 13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository

14 Chapter 14: EA Capability, Tailoring, and Iteration

14.1 Tailoring the ADM: Enterprise Context, Process Weight, and Agile Integration 14.2 ADM Iteration Cycles, Levels, and Classes of Architecture Engagement 14.3 Architecture Maturity Models, Capability Assessment, and EA Performance Measures 14.4 Supporting the ADM Work: The TOGAF Library, Series Guides, Patterns, and Security

11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict

Key Takeaways Explain This Topic AI

Requirements Management sits at the exact center of the TOGAF ADM circular diagram, operating continuously and dynamically across all phases from Preliminary through Phase H.

Requirements Management is a process for managing requirements throughout the ADM; TOGAF states that the process itself does not dispose of, address, or prioritize requirements, which is done within the relevant phase.

The Architecture Requirements Specification captures functional requirements, non-functional qualities of service (QoS), architectural constraints, assumptions, and acceptance criteria.

Bidirectional vertical and horizontal traceability establishes an unbroken chain linking strategic business goals to physical Solution Building Blocks (SBBs), enabling precise impact analysis.

Mid-phase requirement discoveries require a formal Requirements Impact Assessment against the Architecture Vision and Statement of Architecture Work, escalating scope conflicts to the Architecture Board for binding arbitration.

Last updated: October 2026

11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict

In the iconic graphical representation of the TOGAF Architecture Development Method (ADM), Requirements Management is positioned neither as an opening phase nor as a closing phase. Instead, it occupies the exact center of the circular ADM diagram, directly connected to every phase from Preliminary through Phase H. This central positioning is deliberate and conceptually vital: Requirements Management is not a static, one-time activity executed at the beginning of a transformation. It is a continuous, dynamic process that operates throughout the entire architecture lifecycle, acting as the authoritative custodian of stakeholder intent, business drivers, and technical constraints.

The Central Position and Role of Requirements Management

A common misconception on the OGEA-103 exam is confusing Requirements Management with requirements elicitation or business analysis. In the TOGAF Standard:

Requirements Management does not create requirements : Architects elicit requirements collaboratively with stakeholders during specific ADM phases (such as business requirements in Phase B, data requirements in Phase C, and migration requirements in Phase F).

Requirements Management manages requirements; phases decide on them : TOGAF states that the Requirements Management process "does not dispose of, address, or prioritize any requirements; this is done within the relevant phase of the ADM". The process identifies and records requirements and changes, records the priorities that architects and stakeholders set, assesses impacts, and keeps the Architecture Requirements Repository current.

Dynamic Interaction Across All ADM Phases

Requirements Management operates as an active hub, exchanging information continuously with every phase:

Preliminary Phase : Establishes the requirements management framework, selecting repository tooling, defining requirement classification taxonomies, and agreeing on traceability criteria.

Phase A (Architecture Vision) : Ingests high-level business goals, strategic drivers, and stakeholder concerns; shapes the initial scope and establishes the baseline Architecture Requirements Specification .

Phases B, C, and D (Domain Architectures) : Decomposes high-level business scenarios into granular functional and non-functional requirements across Business, Data, Application, and Technology domains, identifying domain-specific constraints.

Phases E and F (Opportunities, Solutions & Migration) : Evaluates candidate work packages, transition architectures, and migration roadmaps against approved requirements, ensuring that delivery schedules prioritize high-value requirements.

Phase G (Implementation Governance) : Uses requirements as the definitive compliance benchmark during Architecture Compliance reviews, verifying through Architecture Contracts that deployed solutions fulfill specifications.

Phase H (Architecture Change Management) : Captures emerging operational requirements, technical debt remediation needs, and new regulatory mandates, evaluating whether they can be resolved within existing baselines or demand a new ADM cycle.

Objectives and Steps of Requirements Management

TOGAF states three objectives: ensure 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; and ensure relevant requirements are available for use by each phase as it executes.

The ten steps alternate between Requirements Management and the ADM phase in progress:

  • Step Who Activity
  • 1 Phase Identify requirements and document them in the Architecture Requirements Specification and repository

2 Requirements Management Establish baseline requirements: determine priorities, confirm stakeholder agreement, and document them

  • 3 Requirements Management Monitor baseline requirements
  • 4 Phase Identify new and changed requirements (remove, add, or modify, and reassess priorities)

5 Requirements Management Identify changed requirements and record priorities; manage conflicts; generate a Requirements Impact Statement

6 Phase Assess the impact on the current and previous phases; decide whether to implement now or defer to a later cycle; issue the Requirements Impact Statement version n+1

  • 7 Phase Implement requirements arising from Phase H
  • 8 Requirements Management Update the Architecture Requirements Repository
  • 9 Phase Implement change in the current phase
  • 10 Phase Assess and revise gap analysis for past phases

In step 10, TOGAF defines a gap requirement as anything eliminated by accident, which therefore requires a change to the Target Architecture. The Requirements Impact Statement identifies the ADM phases that must be revisited and goes through iterations until it includes the full implications (costs, timescales, and business metrics). The outputs of Requirements Management are the Requirements Impact Assessment and an updated Architecture Requirements Specification where necessary.

The Architecture Requirements Specification Deliverable

The primary deliverable managed by this process is the Architecture Requirements Specification . This comprehensive document articulates what the architecture must achieve and encompasses five core components:

Functional Requirements : Specific capabilities, business services, and functional workflows the architecture must deliver (e.g., real-time multi-currency settlement, automated customer identity verification).

Non-Functional Requirements (Qualities of Service / QoS) : Quantifiable, measurable operational attributes that define system performance and reliability, including:

Availability & Resilience : e.g., 99.999% uptime with automated multi-region failover.

Performance & Latency : e.g., sub-50ms API response time at 10,000 requests per second.

Scalability : e.g., horizontal scaling to support 500% organic transaction surges.

Disaster Recovery : Recovery Point Objective (RPO) < 1 minute; Recovery Time Objective (RTO) < 15 minutes.

Security & Compliance : End-to-end encryption in transit and at rest adhering to FIPS 140-3 standards.

Architectural Constraints : Inviolable boundaries that restrict design options, including statutory laws (GDPR data residency), corporate policies, mandatory technology standards (approved cloud platforms in the Standards Library), and budgetary caps.

Assumptions & Dependencies : Operational preconditions, external partner delivery timelines, and foundational platforms required for successful execution.

Acceptance Criteria : Verifiable test conditions and metrics agreed with business sponsors to confirm requirement fulfillment prior to deployment sign-off.

Bidirectional Traceability: Vertical and Horizontal

One of the most powerful capabilities enabled by the Requirements Management process is Bidirectional Traceability .

1. Vertical Traceability (Strategic to Physical)

Vertical traceability establishes an unbroken chain of custody linking strategic enterprise goals down to physical software and infrastructure components: Strategic Business Goal (e.g., Expand into European Digital Banking)

  • |
  • v
  • Business Capability (e.g., Cross-Border Real-Time Payment Settlement)
  • |
  • v
  • Architecture Requirement (e.g., ISO 20022 Compliance, Sub-Second Latency)
  • |
  • v
  • Architecture Building Block [ABB] (e.g., Event-Driven Payment Clearing Engine)
  • |
  • v
  • Solution Building Block [SBB] (e.g., Apache Kafka Cluster deployed on AWS EKS)
  • |
  • v
  • Verification & Compliance Test (e.g., End-to-End Stress Test Suite #402)

Downward Traceability : Verifies that every technical component, cloud service, and software license directly supports an approved business requirement, eliminating expensive 'gold-plating.'

Upward Traceability : Confirms that every high-level business objective is actively realized by underlying architectural assets.

Impact Analysis : When a strategic goal or statutory regulation changes, vertical traceability allows architects to instantly trace downward and identify the exact ABBs, SBBs, and projects affected.

2. Horizontal Traceability (Cross-Domain Dependencies)

Horizontal traceability maps interdependencies across architectural domains. For example, a customer self-service business requirement in Phase B links horizontally to a customer account data entity in Phase C (Data), an API gateway service in Phase C (Application), and a high-availability container cluster in Phase D (Technology). Horizontal traceability ensures that modifying a data schema or network protocol does not trigger unpredicted failures across dependent domains.

Managing Mid-Phase Requirement Discoveries

In real-world enterprise architecture, requirements cannot be frozen permanently in Phase A. As architects conduct deep domain modeling in Phases B through D, or as implementation teams build solutions in Phase G, previously unknown technical limitations, operational bottlenecks, or vendor constraints inevitably surface. Under TOGAF guidelines, newly discovered requirements must never be silently absorbed or implemented out-of-band.

The Requirements Impact Assessment Process

When a new requirement is uncovered mid-ADM, the architecture team executes a structured impact assessment:

Record in Requirements Repository : Formally log the emergent requirement, capturing its source, business rationale, and proposed technical realization.

Conduct Requirements Impact Assessment : Evaluate the requirement's impact against five dimensions:

Impact on Architecture Vision : Does this requirement alter the strategic scope or intent agreed in Phase A?

Impact on Statement of Architecture Work : Does it require additional deliverables or alter contractual commitments?

Impact on Architecture Roadmap : Does it introduce new technical dependencies that disrupt project sequencing?

Impact on Budget & Schedule : Will accommodating this requirement breach CapEx/OpEx limits or miss regulatory deadlines?

Impact on Architectural Principles : Does it violate established enterprise standards or security policies?

Determine Resolution Pathway :

Accommodate : If the requirement is minor and fits within existing scope, budget, and principles, absorb it into the current phase and update the Architecture Requirements Specification.

Defer : If the requirement is valid but non-critical, log it in the repository and defer it to a future Transition Architecture or subsequent ADM cycle.

Escalate for Scope Change : If the requirement is critical but breaches approved scope, budget, or timelines, submit a formal change request to the Architecture Board and business sponsors to amend the Statement of Architecture Work.

Resolving Scope Conflicts and Stakeholder Disagreements

In complex multi-stakeholder transformations, conflicting requirements are standard. The chief marketing officer may demand instant customer onboarding via social media logins, while the chief information security officer mandates multi-factor biometric authentication that introduces onboarding friction. When requirements conflict, enterprise architects do not make arbitrary unilateral decisions.

Structured Conflict Resolution Techniques

Trade-Off Analysis : Systematically evaluating alternative architectural options against strategic enterprise criteria (e.g., security vs. usability, build vs. buy, speed-to-market vs. long-term maintenance cost).

Prioritization Frameworks : Applying proven prioritization models such as MoSCoW (Must have, Should have, Could have, Won't have this time) or weighted multi-criteria scoring to categorize requirements based on business value and technical feasibility.

Architecture Board Arbitration : When stakeholders reach an impasse, the conflict is formally escalated to the Architecture Board . The Architecture Board evaluates the competing requirements against corporate strategy, enterprise architecture principles, and risk appetite, issuing a binding governance determination that balances enterprise-wide interests.

The Architecture Requirements Repository

All requirements artifacts are managed within the Architecture Requirements Repository , which TOGAF organizes into strategic, segment, and capability architecture requirements. TOGAF does not define requirement status values; many tools use a lifecycle such as:

Identified / Elicited : Captured from stakeholder interactions or domain modeling; pending validation.

Under Review : Subject to technical feasibility analysis and initial impact assessment.

Approved : Formally accepted into the Architecture Requirements Specification with allocated budget and phase mapping.

In-Progress : Actively being addressed by architecture domain design or implementation projects.

Implemented / Verified : Certified as fully satisfied through Phase G compliance reviews and testing.

Deferred : Postponed to subsequent transition architectures or future ADM iterations.

Rejected : Formally dismissed by the Architecture Board, accompanied by an audit record explaining the strategic rationale.

Common Exam Traps & Practitioner Pitfalls

The 'Requirements Creation' Fallacy : Believing that Requirements Management invents or dictates business requirements. Requirements Management does not create requirements; it manages, validates, stores, and prioritizes requirements elicited by architects across ADM phases.

The 'Static Waterfall' Myth : Assuming requirements are finalized and locked in Phase A and never change. In modern enterprise architecture, requirements evolve dynamically; Requirements Management governs this evolution through formal impact analysis.

The 'Unrecorded Change' Anti-Pattern : Permitting project teams to implement emergent requirements discovered during development without recording them in the Requirements Repository or performing an impact assessment.

Loading diagram... Central Role of Requirements Management & Bidirectional Traceability Hub