Ücretsiz Kullanmaya Başla

Phase H: Architecture Change Management Knowledge-Based Study

TOGAF · Enterprise Architecture Capability and Governance · Foundation · Establishing an Architecture Capability

Foundation topic explanations on Phase H: Architecture Change Management.

Study notes

  1. Overview of Phase H: Architecture Change Management

    In the TOGAF ADM cycle, the deployment of a target architecture does not mark the conclusion of the Enterprise Architecture journey. The goal of Phase H: Architecture Change Management is to ensure that the architecture achieves its original target business value and is maintained in a cohesive, architected way.

    The primary objectives of Phase H include:

    • Ensuring that the architecture lifecycle is maintained continuously.
    • Executing the enterprise's architecture governance processes to assess, monitor, and direct changes.
    • Evaluating the business and technical drivers for change to maintain alignment between strategy and operational realization.
    • Determining whether a change warrants a simple update or requires initiating a new iteration of the Architecture Development Method (ADM).

    Without an effective change management process, enterprise solutions undergo unmanaged drift, resulting in architecture erosion and misaligned business outcomes.

    Drivers of Architecture Change

    Change drivers originate from both the business context and technical environment:

    • Business Drivers: Mergers and acquisitions, strategic shifts, market disruption, changes in partner relationships, and new regulations.
    • Technology Drivers: Emerging technologies, asset obsolescence, vendor product deprecation, and security vulnerability patterns.

    Classifications of Architecture Change

    The TOGAF Standard categorizes architectural changes into three primary classifications:

    1. Simplification Change: Driven by an objective to reduce complexity, reduce costs, or eliminate redundancies. These changes typically do not modify the core business capability and are handled within existing change management procedures.
    2. Incremental Change: Driven by an ongoing requirement to derive additional value or extend features within an established architecture boundary. Incremental changes can frequently be handled through standard operational governance mechanisms.
    3. Re-architecting Change: A fundamental alteration that changes the underlying rules, paradigms, or core architecture foundation. A re-architecting change is significant enough to require a new cycle of the ADM, formally initiated via a new Request for Architecture Work.

    The Architecture Change Management Process

    Phase H operates in close collaboration with the Architecture Board and enterprise governance bodies. The operational workflow centers on monitoring, assessment, and formal decision-making:

    • Value Monitoring: Continually assessing whether implemented architectures generate expected business outcomes and return on investment.
    • Risk Management: Evaluating the impact of internal system adaptations and external industry changes on enterprise integrity.
    • Architecture Governance Execution: Using the Architecture Contract to verify compliance and establishing whether dispensations are warranted.

    When changes are evaluated, the architecture team produces an Architecture Impact Analysis. If the decision mandates a fundamental restructuring, the outcome of Phase H is a new Request for Architecture Work, directing the organization back to Phase A: Architecture Vision.

    Knowledge Check: Conceptual Distinctions in Phase H

    Practice Question 1: An enterprise determines that emerging regulatory compliance standards require a fundamental redesign of its core transactional capabilities, invalidating key principles in the Architecture Vision. According to the TOGAF Standard, what is the appropriate classification of this change, and what action should be taken in Phase H?

    • A) Simplification change; handle via standard maintenance procedures.
    • B) Incremental change; issue an Architecture Contract addendum without cycling the ADM.
    • C) Re-architecting change; issue a new Request for Architecture Work to initiate a new ADM cycle.
    • D) Operational dispensation; bypass Architecture Board review and update the baseline repository directly.

    Correct Answer: C
    Explanation: A fundamental redesign that impacts the core operating model and invalidates architectural principles is classified as a Re-architecting change. In Phase H, this triggers a formal new Request for Architecture Work to start a new ADM cycle starting at Phase A.

    Practice Question 2: What is the core distinction between the primary responsibility of Phase G and Phase H in the TOGAF ADM?

    • A) Phase G creates the Architecture Vision, whereas Phase H delivers the Target Architecture definitions.
    • B) Phase G oversees implementation compliance, whereas Phase H manages ongoing architecture governance and adaptation after deployment.
    • C) Phase G handles technology-driven changes, whereas Phase H strictly handles business-driven changes.
    • D) Phase G executes vendor procurement, whereas Phase H selects technical product standards.

    Correct Answer: B
    Explanation: Phase G (Implementation Governance) provides architectural oversight and conformance verification during project delivery, whereas Phase H (Architecture Change Management) monitors and directs long-term changes, value delivery, and baseline evolution over the architecture lifecycle.