The TOGAF® Architecture Development Method (ADM) is one of the most structured and widely adopted approaches to enterprise architecture. Whether you’re preparing for certification or looking to implement a practical architecture framework in your organization, understanding the flow of inputs and outputs between ADM phases is critical to success.
In this article, we break down the ADM cycle (Phases A to H) with a clear focus on the key documents, contracts, and transitions involved.
Table of Contents
Why Focus on ADM Inputs and Outputs?
Every ADM phase doesn’t operate in isolation—it is tightly interlinked through formal deliverables, like architecture statements, gap analyses, contracts, and feedback loops. These inputs and outputs ensure traceability, governance, and alignment with business goals.
At the core of the entire cycle lies Requirements Management, which continuously collects, validates, and distributes requirements across all phases.
Vision Central Element: Requirements Management
Purpose:
Acts as the foundation and feedback system across the entire ADM cycle.
- Manages and validates requirements across Phases A to H
- Continuously updated as architecture evolves
- Feeds every phase with refined business and technical needs
Preliminary Phase (Before Phase A)
Output:
- Request for Architecture Work – Initiates the engagement with defined scope and purpose.
Phase A: Architecture Vision
Input:
- Request for Architecture Work (from Preliminary Phase)
Output:
- Statement of Architecture Work – This document sets expectations, deliverables, stakeholders, and scope of the architectural effort
Phase B: Business Architecture
Input:
- Statement of Architecture Work
Output:
- Business Architecture Definition
- Refined business requirements (fed back into Requirements Management)
Phase C: Information Systems Architecture
Input:
- Statement of Architecture Work
- Business Architecture Output
Output:
- Data Architecture
- Application Architecture
- Updated requirements
Phase D: Technology Architecture
Input:
- Information Systems Architecture artifacts
Output:
- Defined Technology Architecture
- Identified technology services and standards
Phase E: Opportunities and Solutions
Input:
- Outputs from Phases B–D
- Gap Analysis findings
Output:
- Work Packages
- Project Dependencies
- Transition Architectures
Phase F: Migration Planning
Input:
- Work Packages
- Transition Architectures
Output:
- Contract for Implementation
- Implementation and Migration Plan
Phase G: Implementation Governance
Input:
- Contract from Phase F
Output:
- Compliance Assessments
- Updated Architecture Deliverables
- Contract for Change Management
Phase H: Architecture Change Management
Input:
- Operational Feedback
- Change Requests
- Contract from Phase G
Output:
- Contract for New Architecture Work
- Updated Requirements
- New Change Requests
Summary of Key Document Flows
|
Document / Contract |
Source Phase |
Target Phase |
|
Request for Architecture Work |
Preliminary |
Phase A |
|
Statement of Architecture Work |
Phase A |
Phases B, C, D |
|
Contract (Implementation Planning) |
Phase F |
Phase G |
|
Contract (Change Management) |
Phase G |
Phase H |
|
Contract (New Architecture Cycle) |
Phase H |
Preliminary / Phase A |
Conclusion: The Value of Mapping Inputs & Outputs in ADM
Understanding how documents, decisions, and deliverables flow between TOGAF ADM phases helps you:
- Maintain traceability and stakeholder alignment
- Ensure the architecture evolves logically and predictably
- Apply governance to real-world enterprise initiatives
- Pass TOGAF certification exams with greater confidence
If you’re looking to master TOGAF® Standard Version 10 with expert guidance, templates, and coaching—PM Training School is here to support you.
👉 TOGAF Study Group (WhatsApp)
📞 Ready to Master TOGAF® with Confidence?
Whether you’re preparing for the TOGAF® 10 certification or need help applying ADM in your organization, our team is here to support you.
📧 Email us at support@pmtrainingschool.com
📱 Call now: +64 21103635
Recent Comments