The TOGAF Architecture Development Method

This chapter describes the TOGAF Architecture Development Method (ADM), including summary tables for each of the ADM phases.

What is the ADM?

The ADM provides a tested and repeatable process for developing architectures. It is a method for deriving organization-specific Enterprise Architectures and is specifically designed to address business requirements. It includes establishing an architecture framework, developing architecture content, transitioning, and governing the realization of architectures. All of these activities are carried out within an iterative cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled manner in response to business goals and opportunities. This is illustrated in Figure 1.

What are the Phases of the ADM?

The phases within the ADM and their purpose are summarized in Table 1.

The description of the phases of the ADM in the TOGAF Standard focuses on recommendations for defining and deploying an Enterprise Architecture. Additional guidance for how to apply the recommendations can be found in the TOGAF Series Guides.

It is recommended that the ADM be adapted to meet the needs of the enterprise and to support different architecture styles. In particular, after commencing an architecture development cycle, the ADM does not mandate that the phases be performed in any specific order, and does not mandate a “waterfall” method.

Figure 1. The Architecture Development Cycle

Table 1. Phases within the ADM
ADM Phase	Purpose
Preliminary Phase	Describes the preparation and initiation activities required to create an Architecture Capability, including customization of the TOGAF framework and definition of Architecture Principles.
Requirements Management	Operates the process of managing architecture requirements throughout the ADM.
Phase A: Architecture Vision	Describes the initial phase of an architecture development cycle. It includes information about defining the scope of the architecture development initiative, identifying the stakeholders, creating the Architecture Vision, and obtaining approval to proceed with the architecture development.
Phase B: Business Architecture Phase C: Information Systems Architectures (Data & Application) Phase D: Technology Architecture	Describes the development of four architectures, that are commonly accepted as subsets of an overall Enterprise Architecture, to support the agreed Architecture Vision: — Business — Information Systems – Data — Information Systems – Application — Technology
Phase E: Opportunities and Solutions	Conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases.
Phase F: Migration Planning	Addresses how to move from the Baseline to the Target Architectures by finalizing a detailed Implementation and Migration Plan.
Phase G: Implementation Governance	Provides architectural oversight for the implementation.
Phase H: Architecture Change Management	Establishes procedures for managing change to the new architecture.

The ADM in Detail

The following tables summarize the objectives, steps, and the inputs and outputs of each ADM phase.

Preliminary Phase

The Preliminary Phase describes the preparation and initiation activities required to meet the business directive for a new Enterprise Architecture Capability, including the definition of an Organization-Specific Architecture framework and the definition of principles.

An overview of the phase is given in Table 2.

Table 2. Preliminary Phase Objectives and Steps
Objectives	Steps
Determine the Architecture Capability desired by the organization: - Review the organizational context for conducting Enterprise Architecture - Identify and scope the elements of the enterprise organizations affected by the Architecture Capability - Identify the established frameworks, methods, and processes that intersect with the Architecture Capability - Establish the Capability Maturity target Establish the Architecture Capability: - Define and establish the Organizational Model for Enterprise Architecture - Define and establish the detailed process and resources for Architecture Governance - Select and implement tools that support the Architecture Capability - Define the Architecture Principles	Scope the enterprise organizations impacted Confirm governance and support frameworks Define and establish the Enterprise Architecture team and organization Identify and establish Architecture Principles Tailor the TOGAF framework and, if any, other selected architecture frameworks Develop strategy and implementation plans for tools and techniques

Table 3. Preliminary Phase Inputs and Outputs
Inputs	Outputs
The TOGAF Library Other architecture framework(s) Board strategies, business plans, business strategy, IT strategy, business principles, business goals, and business drivers Major frameworks operating in the business Governance and legal frameworks Architecture Capability Partnership and contract agreements Existing organizational model for Enterprise Architecture Existing architecture framework, if any, including: - Architecture method - Architecture content - Configured and deployed tools - Architecture Principles - Architecture Repository	Organizational Model for Enterprise Architecture Tailored Architecture Framework, including Architecture Principles, configured and deployed tools Initial Architecture Repository Restatement of, or reference to, business principles, business goals, and business drivers Request for Architecture Work Architecture Governance Framework The Architecture of the Enterprise Architecture Capability

Phase A: Architecture Vision

Phase A is the initial phase of the ADM. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.

Table 4. Phase A Objectives and Steps
Objectives	Steps
Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision	Establish the Architecture Project Identify stakeholders, concerns, and business requirements Confirm and elaborate business goals, business drivers, and constraints Evaluate capabilities Assess readiness for business transformation Define the scope Confirm and elaborate Architecture Principles, including business principles Develop the Architecture Vision Define the Target Architecture value propositions and Key Performance Indicators (KPIs) Identify the business transformation risks and mitigation activities Develop Statement of Architecture Work; secure approval

Table 5. Phase A Inputs and Outputs
Inputs	Outputs
Request for Architecture Work Business principles, business goals, and business drivers Organizational Model for Enterprise Architecture Tailored Architecture Framework, including tailored architecture method, architecture content, Architecture Principles, configured and deployed tools Populated Architecture Repository; that is, existing architecture documentation (framework description, architecture descriptions, existing baseline descriptions, etc.)	Approved Statement of Architecture Work Refined statements of business principles, business goals, and business drivers Architecture Principles Capability assessment Tailored Architecture Framework Architecture Vision, including: - Refined key high-level stakeholder requirements Draft Architecture Definition Document, which may include Baseline and/or Target Architectures of any architectural domain Communications Plan Additional content populating the Architecture Repository

Phase B: Business Architecture

Phase B describes the development of a Business Architecture to support an agreed Architecture Vision.

Table 6. Phase B Objectives and Steps
Objectives	Steps
Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision in a way that addresses the Statement of Architecture Work and stakeholder concerns Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures	Select reference models, viewpoints, and tools Develop the Baseline Business Architecture Description Develop the Target Business Architecture Description Perform a gap analysis Define candidate roadmap components Resolve impacts across the Architecture Landscape Conduct a formal stakeholder review Finalize the Business Architecture Create/update Architecture Definition Document

Note that the same steps are common to Phases B, C, and D.

Table 7. Phase B Inputs and Outputs
Inputs	Outputs
Architecture reference materials Request for Architecture Work Business principles, business goals, and business drivers Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Tailored Architecture Framework Approved Statement of Architecture Work Architecture Principles, including business principles, when pre-existing Enterprise Continuum Architecture Repository Architecture Vision, including: - Refined key high-level stakeholder requirements Draft Architecture Definition Document, which may include Baseline and/or Target Architectures of any architectural domain	Refined and updated versions of the Architecture Vision phase deliverables, where applicable, including: - Statement of Architecture Work - Validated business principles, business goals, and business drivers - Architecture Principles Draft Architecture Definition Document containing content updates: - Baseline Business Architecture, approved, if appropriate - Target Business Architecture (approved with business capabilities, business data model, business processes, etc.) - Views corresponding to selected viewpoints addressing key stakeholder concerns Draft Architecture Requirements Specification including content updates: - Gap analysis results - Technical requirements - Updated business requirements Business Architecture components of an Architecture Roadmap

Phase C: Information Systems Architectures

Phase C describes the Information Systems Architectures for an Architecture Project, including the development of Data and Application Architectures. It involves some combination of Data and Application Architecture, which may be developed either sequentially or concurrently.

Data Architecture

Table 8. Phase C – Data Architecture Objectives and Steps
Objectives	Steps
Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Data Architectures	As per Phase B Steps, see Table 6.

Table 9. Phase C – Data Architecture Inputs and Outputs
Inputs	Outputs
Architecture reference materials Request for Architecture Work Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Tailored Architecture Framework Data principles Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document, which may include Baseline and/or Target Architectures of any architectural domain Draft Architecture Requirements Specification, including: - Gap analysis results - Relevant technical requirements Business Architecture components of an Architecture Roadmap	Refined and updated versions of the Architecture Vision phase deliverables, where applicable, including: - Statement of Architecture Work - Validated data principles, or new data principles Draft Architecture Definition Document, including: - Baseline Data Architecture - Target Data Architecture - Views corresponding to the selected viewpoints, addressing key stakeholder concerns Draft Architecture Requirements Specification, including: - Gap analysis results - Data interoperability requirements - Relevant technical requirements that will apply to this evolution of the architecture development cycle - Constraints on the Technology Architecture - Updated business requirements - Updated application requirements Data Architecture components of an Architecture Roadmap

Application Architecture

Table 10. Phase C – Application Architecture Objectives and Steps
Objectives	Steps
Develop the Target Application Architecture that enables the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Application Architectures	As per Phase B Steps, see Table 6.

Table 11. Phase C – Application Architecture Inputs and Outputs
Inputs	Outputs
Architecture reference materials Request for Architecture Work Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Tailored Architecture Framework Application principles Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document, which may include Baseline and/or Target Architectures of any architectural domain Draft Architecture Requirements Specification, including: - Gap analysis results - Relevant technical requirements Business and Data Architecture components of an Architecture Roadmap	Refined and updated versions of the Architecture Vision phase deliverables, where applicable, including: - Statement of Architecture Work - Validated application principles, or new application principles Draft Architecture Definition Document, including: - Baseline Application Architecture - Target Application Architecture - Views corresponding to the selected viewpoints, addressing key stakeholder concerns Draft Architecture Requirements Specification, including content updates: - Gap analysis results - Application interoperability requirements - Relevant technical requirements that will apply to this evolution of the architecture development cycle - Constraints on the Technology Architecture - Updated business requirements - Updated data requirements Application Architecture components of an Architecture Roadmap

Phase D: Technology Architecture

Phase D is about the development of a Technology Architecture for an Architecture Project.

Table 12. Phase D Objectives and Steps
Objectives	Steps
Develop the Target Technology Architecture that enables the Architecture Vision, target business, data, and application building blocks to be delivered through technology components and technology services, in a way that addresses the Statement of Architecture Work and stakeholder concerns Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures	As per Phase B Steps, see Table 6.

Table 13. Phase D Inputs and Outputs
Inputs	Outputs
Architecture reference materials Product information on candidate products Request for Architecture Work Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Tailored Architecture Framework Technology principles Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document, which may include Baseline and/or Target Architectures of any architectural domain Draft Architecture Requirements Specification, including: - Gap analysis results - Relevant technical requirements Business, Data, and Application Architecture components of an Architecture Roadmap	Refined and updated versions of the Architecture Vision phase deliverables, where applicable, including: - Statement of Architecture Work - Validated technology principles or new technology principles (if generated here) Draft Architecture Definition Document, including: - Baseline Technology Architecture, if appropriate - Target Technology Architecture - Technology Architecture views corresponding to the selected viewpoints, addressing key stakeholder concerns Draft Architecture Requirements Specification, including content updates: - Gap analysis report - Requirements output from Phases B and C - Updated technology requirements Technology Architecture components of an Architecture Roadmap

Phase E: Opportunities and Solutions

Phase E describes the process of identifying delivery vehicles (projects, programs, or portfolios) that effectively deliver the Target Architecture identified in previous phases. It is the first phase which is directly concerned with implementation.

Table 14. Phase E Objectives and Steps
Objectives	Steps
Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value Define the overall Solution Building Blocks (SBBs) to finalize the Target Architecture based on the ABBs	Determine/confirm key corporate change attributes Determine business constraints for implementation Review and consolidate gap analysis results from Phases B to D Review consolidated requirements across related business functions Consolidate and reconcile interoperability requirements Refine and validate dependencies Confirm readiness and risk for business transformation Formulate Implementation and Migration Strategy Identify and group major work packages Identify Transition Architectures Create Architecture Roadmap & Implementation and Migration Plan

Table 15. Phase E Inputs and Outputs
Inputs	Outputs
Architecture reference materials Product Information Request for Architecture Work Capability Assessment Communications Plan Planning methodologies Organizational Model for Enterprise Architecture Governance models and frameworks Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document, which may include Baseline and/or Target Architectures of any architectural domain Draft Architecture Requirements Specification Change Requests for existing business programs and projects Candidate Architecture Roadmap components from Phases B, C, and D	Refined and updated versions of the Architecture Vision phase deliverables, where applicable, including: - Architecture Vision - Statement of Architecture Work Architecture Vision, updated if necessary Draft Architecture Definition Document, including: - Baseline and/or Target Architectures of any architectural domain - Transition Architectures, number and scope, if any Draft Architecture Requirements Specification, including Consolidated Gaps, Solutions, and Dependencies Assessment Capability Assessments, including: - Business Capability - IT Capability Architecture Roadmap, including: - Work package portfolio - Identification of Transition Architectures, if any - Implementation recommendations Implementation and Migration Plan Draft, including: - Implementation and Migration Strategy

Phase F: Migration Planning

Phase F addresses migration planning, which is how to move from the Baseline to the Target Architectures by finalizing a detailed Implementation and Migration Plan.

Table 16. Phase F Objectives and Steps
Objectives	Steps
Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan Ensure that the Implementation and Migration Plan is coordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders	Confirm management framework interactions for the Implementation and Migration Plan Assign a business value to each work package Estimate resource requirements, project timings, and availability/delivery vehicle Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation Confirm Architecture Roadmap and update Architecture Definition Document Complete the Implementation and Migration Plan Complete the architecture development cycle and document lessons learned

Table 17. Phase F Inputs and Outputs
Inputs	Outputs
Architecture reference materials Request for Architecture Work Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Governance models and frameworks Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document, which may include Baseline and/or Target Architectures of any architectural domain Draft Architecture Requirements Specification Change Requests for existing business programs and projects Architecture Roadmap Capability Assessment, including: - Business Capability - IT Capability Implementation and Migration Plan Draft, including: - High-level Implementation and Migration Strategy	Implementation and Migration Plan (detailed), including: - Implementation and Migration Strategy - Project and portfolio breakdown of the implementation - Project charters (optional) Finalized Architecture Definition Document, including: - Finalized Transition Architectures, if any Finalized Architecture Requirements Specification Finalized Architecture Roadmap Re-usable ABBs Requests for Architecture Work for a new iteration of the ADM cycle (if any) Implementation Governance Model Change Requests for the Architecture Capability arising from lessons learned

Phase G: Implementation Governance

Phase G provides architectural oversight of the implementation.

Table 18. Phase G Objectives and Steps
Objectives	Steps
Ensure conformance with the Target Architecture by implementation projects Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests	Confirm scope and priorities for deployment with development management Identify deployment resources and skills Guide development of solutions deployment Perform Enterprise Architecture compliance reviews Implement business and IT operations Perform post-implementation review and close the implementation

Table 19. Phase G Inputs and Outputs
Inputs	Outputs
Architecture reference materials Request for Architecture Work Capability Assessment Organizational Model for Enterprise Architecture Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository Architecture Definition Document Architecture Requirements Specification Architecture Roadmap Implementation Governance Model Architecture Contract (standard) Request for Architecture Work identified in Phases E and F Implementation and Migration Plan	Architecture Contract (signed) Compliance Assessments Change Requests Architecture-compliant solutions deployed, including: - The architecture-compliant implemented system - Populated Architecture Repository - Architecture compliance recommendations and dispensations - Recommendations on service delivery requirements - Recommendations on performance metrics - SLAs - Architecture Vision, updated post-implementation - Architecture Definition Document, updated post-implementation - Business and IT operating models for the implemented solution - ABBs

Phase H: Architecture Change Management

Phase H establishes procedures for managing change to the new architecture.

Table 20. Phase H Objectives and Steps
Objectives	Steps
Ensure that the architecture development lifecycle is maintained Ensure that the Architecture Governance Framework is executed Ensure that the Enterprise Architecture Capability meets current requirements	Establish value realization process Deploy monitoring tools Manage risks Provide analysis for architecture change management Develop change requirements to meet performance targets Manage governance process Activate the process to implement change

Table 21. Phase H Inputs and Outputs
Inputs	Outputs
Architecture reference materials Request for Architecture Work Organizational Model for Enterprise Architecture Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository Architecture Definition Document Architecture Requirements Specification Architecture Roadmap Change Requests due to technology changes Change Requests due to business changes Change Requests from lessons learned Implementation Governance Model Architecture Contract (signed) Compliance Assessments Implementation and Migration Plan	Architecture updates (for maintenance changes) Changes to architecture framework and principles (for maintenance changes) New Request for Architecture Work, to initiate another cycle of the ADM (for major changes) Statement of Architecture Work, updated if necessary Architecture Contract, updated if necessary Compliance Assessments, updated if necessary

Requirements Management

This phase is the process of managing architecture requirements throughout the ADM, and applies to all phases of the ADM cycle. The Requirements Management process is a dynamic process, which addresses the identification of requirements for the enterprise, storing them, and then feeding them in and out of the relevant ADM phases. As shown in Figure 1, this process is central to driving the ADM process.

Table 22. Requirements Management Objectives and Steps
Objectives	Steps
Ensure that 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 Ensure that relevant architecture requirements are available for use by each phase as the phase is executed	Identify/document requirements Baseline requirements Monitor baseline requirements Identify new and changed requirements; remove, add, modify, and re-assess priorities Identify changed requirements and record priorities; identify and resolve conflicts; generate Requirements Impact Statement Assess impact of changed requirements on current and previous ADM phases Implement requirements arising from Phase H Update the Architecture Requirements Repository Implement change in the current phase Assess and revise gap analysis for past phases

Table 23. Requirements Management Inputs and Outputs
Inputs	Outputs
A populated Architecture Repository Organizational model for Enterprise Architecture Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture requirements populating an Architecture Requirements Specification Requirements Impact Statement	Changed requirements Updated Requirements Specification