Introduction

Phase H of the TOGAF Architecture Development Method (ADM) focuses on establishing procedures for managing change to the new architecture. This phase ensures that the architecture development lifecycle is maintained, the Architecture Governance Framework is executed, and the Enterprise Architecture Capability meets current requirements. It also involves deploying monitoring tools, managing risks, and providing analysis for architecture change management.

Objectives and Steps

1. Ensure Maintenance of the Architecture Development Lifecycle

Objective: Ensure that the architecture development lifecycle is maintained and that the Architecture Governance Framework is executed.

Steps:

  • Establish Value Realization Process: Develop a process to realize the value of the architecture changes.
  • Deploy Monitoring Tools: Implement tools to monitor the architecture and its changes.
  • Manage Risks: Identify and manage risks associated with architecture changes.
  • Provide Analysis for Architecture Change Management: Conduct analysis to support architecture change management.
  • Develop Change Requirements: Create change requirements to meet performance targets.
  • Manage Governance Process: Oversee the governance process to ensure compliance and effectiveness.
  • Activate Change Implementation Process: Initiate the process to implement changes to the architecture.

Inputs and Outputs

Inputs

  1. Architecture Reference Materials:
    • Use architecture reference materials to guide the change management process.
  2. Request for Architecture Work:
    • The initial request that triggers the architecture development process.
  3. Organizational Model for Enterprise Architecture:
    • The organizational structure and roles involved in the Enterprise Architecture.
  4. Tailored Architecture Framework:
    • The customized architecture framework used for the project.
  5. Statement of Architecture Work:
    • The approved document that outlines the scope, objectives, and deliverables of the architecture project.
  6. Architecture Vision:
    • The comprehensive vision for the future state of the enterprise architecture.
  7. Architecture Repository:
    • Existing architecture documentation, including framework descriptions, architecture descriptions, and baseline descriptions.
  8. Architecture Definition Document:
    • A detailed document that includes baseline and/or target architectures of any architectural domain.
  9. Architecture Requirements Specification:
    • Includes gap analysis results and relevant technical requirements.
  10. Architecture Roadmap:
    • The roadmap outlining the transition from the Baseline to the Target Architecture.
  11. Change Requests Due to Technology Changes:
    • Requests for changes to the architecture due to technology advancements.
  12. Change Requests Due to Business Changes:
    • Requests for changes to the architecture due to business needs.
  13. Change Requests from Lessons Learned:
    • Requests for changes based on lessons learned during the architecture development process.
  14. Implementation Governance Model:
    • A model for governing the implementation of the architecture.
  15. Architecture Contract (Signed):
    • The signed contract agreeing to the terms and conditions for the architecture implementation.
  16. Compliance Assessments:
    • Assessments to ensure compliance with the Target Architecture.
  17. Implementation and Migration Plan:
    • A detailed plan for implementing and migrating to the Target Architecture.

Outputs

  1. Architecture Updates (for Maintenance Changes):
    • Updates to the architecture to address maintenance changes.
  2. Changes to Architecture Framework and Principles (for Maintenance Changes):
    • Adjustments to the architecture framework and principles to accommodate maintenance changes.
  3. New Request for Architecture Work:
    • Requests for new architecture work to initiate another cycle of the ADM for major changes.
  4. Statement of Architecture Work, Updated if Necessary:
    • An updated Statement of Architecture Work reflecting any changes or new insights gained during Phase H.
  5. Architecture Contract, Updated if Necessary:
    • An updated Architecture Contract reflecting any changes or new agreements.
  6. Compliance Assessments, Updated if Necessary:
    • Updated compliance assessments to ensure ongoing adherence to the Target Architecture.

Key Concepts

  • Architecture Change Management: The process of managing changes to the enterprise architecture to ensure it remains aligned with business goals and strategic drivers.
  • Value Realization Process: A process to realize the value of architecture changes.
  • Monitoring Tools: Tools deployed to monitor the architecture and its changes.
  • Risk Management: The identification and management of risks associated with architecture changes.
  • Governance Process: The process of overseeing the governance of the architecture to ensure compliance and effectiveness.
  • Change Requirements: Requirements developed to meet performance targets and address changes to the architecture.

Conclusion

Phase H of the TOGAF ADM is crucial for establishing procedures for managing change to the new architecture. By following the outlined steps and utilizing the necessary inputs, organizations can ensure that the architecture development lifecycle is maintained, the Architecture Governance Framework is executed, and the Enterprise Architecture Capability meets current requirements. This phase ensures that the architecture remains aligned with business goals and strategic drivers, addressing stakeholder concerns and adapting to changes effectively.

References

Leave a Reply

Your email address will not be published. Required fields are marked *