Study guide
6.2 Phase H: Architecture Change Management & Driver Monitoring
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.2 Phase H: Architecture Change Management & Driver Monitoring
Key Takeaways Explain This Topic AI
Phase H establishes a continuous architecture change management framework to maintain alignment with evolving business strategy and technology innovations.
TOGAF categorizes architecture changes into 3 distinct types: Simplification change, Incremental change, and Re-architecting change.
A Re-architecting change involves high impact and risk, requiring a new full ADM cycle starting from Phase A or the Preliminary Phase.
Continuous driver monitoring tracks business shifts, emerging technology trends, and governance findings to trigger Architecture Change Requests.
Phase H ensures the enterprise architecture remains dynamic, valuable, and sustainable throughout its operational lifecycle.
Last updated: August 2026
6.2 Phase H: Architecture Change Management & Driver Monitoring
Phase H: Architecture Change Management is the final phase of the TOGAF Architecture Development Method (ADM) cycle. However, rather than signifying an end point, Phase H represents the continuous, operational state of Enterprise Architecture governance. Once a target architecture is implemented (via Phase G), the business environment, market dynamics, regulatory landscape, and technology capabilities continue to evolve rapidly. Phase H ensures that the Enterprise Architecture baseline remains aligned with enterprise goals, continuously delivers business value, and adapts flexibly to strategic changes.
Without a structured change management phase, enterprise architectures quickly become obsolete static artifacts. Architecture drift occurs, solutions deviate from strategic goals, and technology debt accumulates. Phase H establishes an ongoing monitoring capability, processes incoming change requests, conducts impact assessments, and determines whether localized adjustments are sufficient or if a new ADM cycle must be triggered.
Core Objectives of Phase H
The strategic objectives of ADM Phase H include:
Ensure Continuous Business-IT Alignment: Continuously monitor internal business strategy changes and external market drivers to keep the architecture baseline current.
Monitor Technology Innovations: Track technological advancements, emerging vendor capabilities, and industry trends to identify proactive improvement opportunities.
Operate Architecture Change Governance: Provide a systematic intake, review, evaluation, and approval process for all incoming Architecture Change Requests.
Classify Architecture Changes: Evaluate change proposals and categorize them as Simplification, Incremental, or Re-architecting changes.
Drive Architectural Evolution: Determine when architectural changes can be handled operationally versus when they necessitate initiating a new ADM iteration.
Maintain Architecture Assets: Ensure the Architecture Repository, building blocks, and baseline documentation remain updated across operational lifecycles.
Monitoring Drivers for Architecture Change
Phase H relies on continuous monitoring across three primary categories of change drivers: +-------------------------------------------------------------------------+
- | DRIVERS FOR ARCHITECTURE CHANGE |
- +------------------------------------+------------------------------------+
- | BUSINESS DRIVERS | TECHNOLOGY DRIVERS |
- | - Corporate M&A / Restructuring | - Emerging Tech (AI, Cloud, IoT) |
- | - Business Model Innovations | - Vendor End-of-Life / Obsolescence |
- | - Regulatory & Compliance Changes | - Cyber Threats & Security Risks |
- +------------------------------------+------------------------------------+
- |
- v
- +-------------------------------------------------------------------------+
- | GOVERNANCE & COST DRIVERS |
- | - Unplanned IT Maintenance Costs - Architecture Board Audit Findings |
- +-------------------------------------------------------------------------+
- 1. Business Drivers
Strategic Mergers & Acquisitions: Integration of diverse business units, customer databases, and enterprise systems.
Market Disruptions: Emergence of novel digital business models requiring rapid capability pivoting.
Regulatory Mandates: New data privacy laws (e.g., GDPR, CCPA) or financial reporting regulations requiring architectural compliance.
2. Technology Drivers
Emerging Technologies: Opportunities presented by generative AI, cloud-native serverless models, or edge computing.
Vendor Lifecycle Expiration: Core legacy software or hardware reaching end-of-life (EOL), introducing vulnerability and support risks.
Security Baseline Evolution: Heightened cyber threat landscapes mandating zero-trust network architectures.
3. Governance & Cost Drivers
Operational Efficiency Mandates: Corporate directives to reduce redundant application licensing or infrastructure footprints.
Compliance Review Audit Findings: Accumulated dispensations requiring systematic resolution.
Classification of Architecture Changes
When a change driver triggers an Architecture Change Request, TOGAF Phase H provides a definitive classification model to assess impact, cost, risk, and governing authority. TOGAF establishes 3 core types of architecture change :
Change Type Characteristics & Drivers Architectural Impact & Required Action
Simplification Change Driven by goals to reduce operational complexity, eliminate redundant software licenses, or retire legacy assets. Low cost, low risk. Handled through normal operational maintenance or minor project updates. Does not require a new ADM cycle. Managed by solution governance.
Incremental Change Driven by desires to enhance existing capabilities, integrate minor software upgrades, or expand system capacity. Medium cost, moderate impact. Managed within the existing architecture framework and current roadmap. May require minor ADM iterations (e.g., updating Phase C/D models) without resetting Vision.
Re-architecting Change Driven by major strategic business shifts, disruptive market changes, enterprise-wide digital transformations, or total technology overhauls. High impact, high risk. Requires initiating a brand-new full ADM cycle , starting from Phase A (Architecture Vision) or the Preliminary Phase. Requires Architecture Board executive sign-off.
The Change Request Management Workflow
Processing incoming changes in Phase H follows a disciplined 5-step lifecycle:
Intake & Logging: Capture incoming Change Requests from business leaders, project teams, compliance audits, or technology monitoring.
Architectural Impact Analysis: Evaluate the proposed change against the baseline architecture, target architecture, roadmap, and ongoing projects. Determine affected Architecture Building Blocks (ABBs).
Classification & Strategy Selection: Categorize the change as Simplification, Incremental, or Re-architecting.
Governance Board Evaluation: Present findings to the Architecture Board for formal review, funding allocation, or rejection.
Execution & Repository Update: Execute approved operational changes or launch a new ADM cycle. Update baseline documentation in the Architecture Repository.
Capacity & Value Management in Phase H
Phase H also incorporates ongoing Capacity and Performance Management . As business transaction volumes scale, the technology architecture must accommodate increased load without degrading service level agreements (SLAs). If monitoring reveals capacity bottlenecks that cannot be remediated through routine infrastructure scaling, an Architecture Change Request is submitted to adjust the underlying technology architecture pattern.
Furthermore, Phase H validates Value Realization . It assesses whether deployed solutions achieved the Return on Investment (ROI) and capability benefits outlined in the original Statement of Architecture Work from Phase A.
- Phase H Inputs, Steps, and Outputs
- Key Inputs
- Ongoing Implementation Governance Reports & Compliance Assessments (Phase G)
- Updated Architecture Repository & Baseline Artifacts
- Change Requests from business and technology stakeholders
- Vendor Technology Strategy & Market Research Intelligence
- Key Steps
Establish and operate continuous business and technology monitoring capabilities.
Receive, record, and prioritize incoming Architecture Change Requests.
Conduct impact assessments across business, data, application, and technology domains.
Classify changes into Simplification, Incremental, or Re-architecting categories.
Present recommendations to the Architecture Board for formal decisioning.
Update Architecture Repository baselines or initiate a new ADM cycle.
Key Outputs
Architecture Change Requests: Approved, modified, or deferred change proposals.
Updated Architecture Contracts & Repository Assets: Refreshed architectural baselines.
New Statement of Architecture Work: Triggered when a Re-architecting change initiates a new ADM cycle.