TOGAF ADM Phases Explained: Inputs, Steps and Outputs (TOGAF 9.2)

The TOGAF Architecture Development Method (ADM) is the core of The Open Group Architecture Framework: an iterative cycle of phases that takes an enterprise from an initial architecture vision through to implemented, governed change. This guide brings together my TOGAF 9.2 study notes in one place, with the inputs, steps and outputs of every ADM phase, the difference between architecture and solution building blocks, and a reference table of ADM deliverables.

I put these notes together while studying TOGAF 9.2. They are useful if you are preparing for the TOGAF exam, or if you simply need a quick reminder of what each phase should produce.

TOGAF ADM phases at a glance

Requirements Management sits at the centre of the cycle, so requirements are captured, stored and fed into every phase.

Contents

1. What is enterprise architecture and solution architecture?
2. Preliminary Phase: preparing the organisation
3. Phase A: Architecture Vision
4. Phase B: Business Architecture
5. Phase C: Information Systems Architecture (data and applications)
6. Phase D: Technology Architecture
7. Phase E: Opportunities and Solutions
8. Phase F: Migration Planning
9. Phase G: Implementation Governance
10. Phase H: Architecture Change Management
11. Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs)
12. TOGAF 9.2 ADM deliverables: which phase produces and consumes them

What is enterprise architecture and solution architecture?

There are couple of definitions for architecture.

The most common and used ones are :

1- The fundamental concepts or properties of a system in its environment embodies in its elements, relationships, and in the principles of its design and evolution.

Source : ISO 42010:2011

2- An architecture is the set of significant decisions about the orgranization of a software system, the selection of the structural elements and their interfaces by which the system is composed, together with their behaviour as specified in the collaborations among those elements, the composition of these structural and behavioural elements into progressively larger subsystems, and the architectural style that guides this orgranization – these elements and their interfaces , their collaborations, and their composition.

Source : Grady Booch / UML Definitions 1999.

Preliminary Phase: preparing the organisation

As the first phase of the ADM which consists of 10 steps, the preliminary phase aims at preparing the road for the other steps, it has a set of inputs, steps and generates a number of outputs and artifacts.

Inputs

This section defines the inputs to the Preliminary Phase.

1. The TOGAF Library.
2. Other architecture frameworks.
3. Board strategies and board business pans, business strategy, IT strategy, business principles, business goals, and business drivers.
4. Major frameworks operating in the business (e.g. SCRUM).
5. Governance and legal frameworks including Architecture Governance strategy.
6. Architecture capabilities.
7. Partnership and contract agreements.
8. Existing documents related to architecture capability.
9. The organizational model for Enterprise Architecture.
10. Existing architecture framework (if any).

Steps

The steps included in this phase are:

1. Scope of the enterprise organizations impacted.
2. Confirm the governance and support frameworks.
3. Define and establish the architecture team.
4. Identify and establish architectural principles
5. Tailor TOGAF and other frameworks.
6. Implement architecture tools.

Outputs

At the end of this phase, the following outputs are generated:

1. Organizational Model for Enterprise Architecture.
2. Tailored Architecture Framework.
3. Initial Architecture Repository.
4. Business principles, business goals, and business drivers.
5. Request for Architecture Work (optional).
6. Architecture Governance Framework.

Phase A: Architecture Vision

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

Inputs

The inputs of this phase are:

1. Architecture reference materials.
2. Request for Architecture Work.
3. Business principles, business goals, and business drivers.
4. Organizational Model for Enterprise Architecture.
5. Tailored Architecture Framework.
6. Populated Architecture Repository.

Steps

The steps included in this phase are:

1. Establish Architecture Project.
2. Identify stakeholders, concerns, and business requirements.
3. Confirm business goals, drivers, and constraints.
4. Evaluate capabilities (this has been updated in TOGAF 9.2)
5. Assess readiness for transformation.
6. Define the scope.

Outputs

At the end of this phase, the following outputs are generated:

1. Approved statement of Architecture Work.
2. Refined statements of business principles, goals, and drivers.
3. Architecture principles.
4. Capability assessment.
5. Tailored architecture framework.
6. Architecture vision.
7. Draft architecture definition document (v 0.1 of all baseline and target BDAT documents).
8. Communication plan.
9. Additional content in the Architecture Repository.

Phase B: Business Architecture

This step of ADM looks at the business architecture and is the first pillar of the BDAT architectures (Business, Data, Application & Technology).

Inputs

The inputs of this phase are:

1. External reference materials.
2. Request for Architecture Work (optional) (Prelim Phase).
3. Business principles, business goals, and business drivers. (Phase A).
4. Capability assessment (Phase A).
5. Communication plan (Phase A).
6. Organization Model for Enterprise Architecture (Prelim Phase).
7. Tailored Architecture Framework (Prelim Phase).
8. Approved Statement of Architecture Work (Phase A).
9. Architecture principles (Phase A).
10. Enterprise continuum.
11. Architecture Repository.
12. Architecture vision (Phase A).
13. Draft architecture definition document (Version 0.1 of all baseline and target BDAT documents) (Phase A).

Steps

The steps included in this phase are:

1. Select reference models, viewpoints, and tools.
2. Develop a baseline business architecture description.
3. Develop target business description.
4. Perform a gap analysis.
5. Define candidate roadmap components.
6. Resolve impacts across the architecture landscape.

Outputs

At the end of this phase, the following outputs are generated:

1. Refined Phase A Deliverables.
2. Draft architecture definition document
   1. Baseline business v1.0 (detailed)
   2. Target business  v1.0 (detailed)
3. Draft architecture requirements specification – Gap Analysis.
4. Business components of an architecture roadmap.

Phase C: Information Systems Architecture (data and applications)

This step of ADM looks at the information system architecture and is the second pillar of the BDAT architectures (Business, Data, Application & Technology). It covers both Data and application architecture. There is no particular order in which you should tackle them.

Inputs (Application)

The inputs of this phase are:

1. External reference materials.
2. Request for Architecture Work (optional) (Prelim Phase).
3. Capability assessment (Phase A).
4. Communication plan (Phase A).
5. Organization Model for Enterprise Architecture (Prelim Phase).
6. Tailored Architecture Framework (Prelim Phase).
7. Application principles (TOGAF Specification Chapter 20)
8. Approved Statement of Architecture Work (Phase A).
9. Architecture vision (Phase A).
10. Architecture Repository.
11. Draft architecture documents and draft requirements (Phase B).
12. Business and data related architecture roadmap (Phase B).

Steps (Application)

The steps included in this phase are:

1. Select reference models, viewpoints, and tools.
2. Develop a baseline application architecture description.
3. Develop target application architecture description.
4. Perform a gap analysis.
5. Define candidate roadmap components.
6. Resolve impacts across the architecture landscape.

Outputs (Application)

At the end of this phase, the following outputs are generated:

1. Refined Phase A Deliverables.
2. Draft architecture definition document
   1. Baseline application architecture v1.0 (detailed)
   2. Target application architecture v1.0 (detailed)
3. Draft architecture requirements specification – Gap Analysis.
4. Application architecture components of an architecture roadmap.

Inputs (Data)

The inputs of this phase are:

1. External reference materials.
2. Request for Architecture Work (optional) (Prelim Phase).
3. Capability assessment (Phase A).
4. Communication plan (Phase A).
5. Organization Model for Enterprise Architecture (Prelim Phase).
6. Tailored Architecture Framework (Prelim Phase).

Steps (Data)

The steps included in this phase are:

1. Select reference models, viewpoints, and tools.
2. Develop a baseline data architecture description.
3. Develop target data architecture description.
4. Perform a gap analysis.
5. Define candidate roadmap components.
6. Resolve impacts across the architecture landscape.

Outputs (Data)

At the end of this phase, the following outputs are generated:

1. Refined Phase A Deliverables.
2. Draft architecture definition document
   1. Baseline data architecture v1.0 (detailed)
   2. Target data architecture v1.0 (detailed)
3. Draft architecture requirements specification – Gap Analysis.
4. Data architecture components of an architecture roadmap.

Phase D: Technology Architecture

This step of ADM looks at the technology architecture and is the last pillar of the BDAT architectures (Business, Data, Application & Technology).

The technology architecture looks at the underlying and enabler of the architecture if comprises of data centers, servers, networks, cloud architecture …etc.

Inputs

The inputs of this phase are:

1. External reference materials.
2. Product information and candidate products.
3. Request for Architecture Work (optional) (Prelim Phase).
4. Capability assessment (Phase A).
5. Communication plan (Phase A).
6. Organization Model for Enterprise Architecture (Prelim Phase).
7. Tailored Architecture Framework (Prelim Phase).
8. Technology principles (TOGAF specification Chapter 20).
9. Approved Statement of Architecture Work (Phase A).
10. Architecture vision (Phase A).
11. Architecture Repository
12. Draft architecture documents and draft requirements (Phase B & C).
13. Business, data, and application components of an architecture roadmap (Phase B & C).

Steps

The steps included in this phase are:

1. Select reference models, viewpoints, and tools.
2. Develop a baseline technology architecture description.
3. Develop target technology architecture description.
4. Perform a gap analysis.
5. Define candidate roadmap components.
6. Resolve impacts across the architecture landscape.

Outputs

At the end of this phase, the following outputs are generated:

1. Refined Phase A Deliverables.
2. Draft architecture definition document
   1. Baseline technology architecture v1.0 (detailed)
   2. Target technology architecture v1.0 (detailed)
3. Draft architecture requirements specification – Gap Analysis.
4. Technology architecture components of an architecture roadmap.

Phase E: Opportunities and Solutions

In order to deliver the architecture identified in the previous steps, this step aims at identifying the enablers or delivery vehicles to achieve the desired results (Projects, programs, and portfolios).

Inputs

The inputs of this phase are:

1. External reference materials.
2. Product information.
3. Request for Architecture Work (optional) (Prelim Phase).
4. Capability assessment (Phase A).
5. Communication plan (Phase A).
6. Planning methodologies.
7. Organization Model for Enterprise Architecture (Prelim Phase).
8. Tailored Architecture Framework (Prelim Phase).
9. Approved Statement of Architecture Work (Phase A).
10. Architecture vision (Phase A).
11. Architecture Repository
12. Draft architecture documents and draft requirements (BDAT).
13. Change request for existing business programs and projects.
14. Candidate architecture roadmap components.

Steps

The steps included in this phase are:

1. Determine key corporate change attributes.
2. Determine business constraints.
3. Review and consolidate gap analysis from phases B to D.
4. Review consolidated requirements across business functions.
5. Consolidate and reconcile interoperability requirements.
6. Refind and validate dependencies.

Outputs

At the end of this phase, the following outputs are generated:

1. Refined Phase A Deliverables.
2. Draft architecture definition document – incl. baseline and target, v1.0.
3. Draft architecture requirements specification – incl. gap analysis.
4. Capability assessments.
5. Architecture road, v0.1
6. Implementation and migration plan, vision 0.1.

Phase F: Migration Planning

In this phase, we start looking at how to migrate from the current baseline architecture to the desired target architecture.

Inputs

The inputs of this phase are:

1. External reference materials.
2. Request for Architecture Work (optional) (Prelim Phase).
3. Capability assessment (Phase A).
4. Communication plan (Phase A).
5. Organization Model for Enterprise Architecture (Prelim Phase).
6. Governance Models and Frameworks.
7. Tailored Architecture Framework (Prelim Phase).
8. Approved Statement of Architecture Work (Phase A).
9. Architecture vision (Phase A).
10. Architecture Repository.
11. Draft architecture documents and draft requirements (BDAT).
12. Change requests for existing business programs and projects.
13. Architecture roadmap, version 0.1 (Phase E).
14. Capability assessment.
15. Implementation and migration plan, version 0.1 (Phase E).

Steps

The steps included in this phase are:

1. Confirm management framework interactions.
2. Assign a business value to each work package.
3. Estimate resource requirements, project timings, etc.
4. Prioritize the migration projects.
5. Confirm the architecture roadmap Migration planning and update the architecture definition document.
6. Generate implementation and migration plan.
7. Complete the architecture development cycle, lessons learned.

Outputs

At the end of this phase, the following outputs are generated:

1. Implementation and Migration Plan, version 1.0.
2. Finalized architecture definition document.
3. Finalized architecture requirements.
4. Finalized architecture roadmap.
5. Reusable Architecture Building Blocks (ABBs).
6. Request for Architecture Work for the next ADM cycle (if any).
7. Implementation of the governance model.
8. Change requests for architecture capability from lessons learned.

Phase G: Implementation Governance

This phase of the TOGAF framework ensures that the implementation and deliverables are in line with the desired target architecture. Even if it does not involve hands-on code, this step ensures that the implementation team delivers what was designed in the previous steps.

Inputs

The inputs of this phase are:

1. External reference materials.
2. Request for Architecture Work (optional) (Prelim Phase).
3. Capability assessment (Phase A).
4. Organization Model for Enterprise Architecture (Prelim Phase).
5. Tailored Architecture Framework (Prelim Phase).
6. Approved Statement of Architecture Work (Phase A).
7. Architecture vision (Phase A).
8. Architecture Repository.
9. Architecture definition documents and requirements (BDAT).
10. Architecture roadmap, version 1.0 (Phase F).
11. Implementation governance model.
12. Architecture Contracts.
13. Request for architecture work for the next ADM cycle (Phase F).
14. Implementation and migration plan, version 1.0 (Phase F).

Steps

The steps included in this phase are:

1. Confirm Scope and Priorities for deployment.
2. Identify Deployment Resources and Skills.
3. Guide Development of Solutions Deployment.
4. Perform Enterprise Architecture Compliance Reviews.
5. Implement Business and IT Operations.
6. Perform Post-Implementation Review and Close the Implementation.

Outputs

At the end of this phase, the following outputs are generated:

1. Architecture contract.
2. Compliance assessments.
3. Change requests.
4. Architecture-compliant solutions deployed.

Phase H: Architecture Change Management

This final phase of the TOGAF ADM looks at establishing procedures for managing change to the new architecture.

Inputs

The inputs of this phase are:

1. External reference materials.
2. Request for Architecture Work (optional) (Prelim Phase).
3. Organization Model for Enterprise Architecture (Prelim Phase).
4. Tailored Architecture Framework (Prelim Phase).
5. Statement of Architecture Work (Phase A).
6. Architecture vision (Phase A).
7. Architecture Repository.
8. Architecture definition documents and requirements (BDAT).
9. Architecture roadmap, version 1.0 (Phase F).
10. Change requests – technology changes, business changes, lessons learned.
11. Implementation governance model.
12. Architecture Contract (Phase G).
13. Compliance assessments (Phase G).
14. Implementation and migration plan, version 1.0 (Phase F).

Steps

The steps included in this phase are:

1. Establish the Value Realization Process.
2. Deploy Monitoring Tools.
3. Manage Risks.
4. Provide Analysis for Architecture Change Management.
5. Develop Change Requirements to TOGAF Meet Performance Targets.
6. Manage Governance Process.
7. Activate the Process to Implement Change.

Outputs

At the end of this phase, the following outputs are generated:

1. Architecture updates (maintenance).
2. Change to architecture framework and principles (maintenance).
3. New Request for Architecture Work (for major changes).
4. Statement of architecture work (Update if necessary).
5. Architecture contract (updated if necessary).
6. Compliance assessments (update if necessary).

Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs)

Architecture building blocks

Architecture Building Blocks (ABBs) relate to the Architecture Continuum (The Architecture Continuum), and are defined or selected as a result of the application of the ADM.

Characteristics

ABBs:

• Define what functionality will be implemented
• Capture business and technical requirements
• Are technology aware
• Direct and guide the development of SBBs

Specification Content

ABB specifications include the following as a minimum:

• Fundamental functionality and attributes: semantic, unambiguous, including security capability and manageability
• Interfaces: chosen set, supplied (APIs, data formats, protocols, hardware interfaces, standards)
• Dependent building blocks with required functionality and named user interfaces
• Map to business/organizational entities and policies

Solution building blocks

Solution Building Blocks (SBBs) relate to the Solutions Continuum (The Solutions Continuum), and may be either procured or developed.

Characteristics

SBBs:

• Define what products and components will implement the functionality
• Define the implementation
• Fulfil business requirements
• Are product or vendor-aware

Specification Content

SBB specifications include the following as a minimum:

• Specific functionality and attributes
• Interfaces; the implemented set
• Required SBBs used with required functionality and names of the interfaces used
• Mapping from the SBBs to the IT topology and operational policies
• Specifications of attributes shared across the environment (not to be confused with functionality) such as security, manageability, localizability, scalability
• Performance, configurability
• Design drivers and constraints, including the physical architecture
• Relationships between SBBs and ABBs.

TOGAF 9.2 ADM deliverables: which phase produces and consumes them

Here is a list of the deliverables generated by the TOGAF 9.2 ADM and TOGAF Framework in general, and in which phase they are produced or consumed

Source: http://sarathc.com/experience-with-togaf-certification.html

Source: Togaf 9.2 Standard.

TOGAF ADM FAQ

How many phases are there in the TOGAF ADM?

The ADM has a Preliminary Phase plus eight lettered phases (A to H), with Requirements Management at the centre of the cycle.

What are the BDAT architecture domains?

BDAT stands for Business, Data, Application and Technology. Business is covered in Phase B, data and applications in Phase C, and technology in Phase D.

Which TOGAF phase produces the Architecture Contract?

Architecture Contracts are produced and enforced during Phase G (Implementation Governance). They are agreements between the architecture function and the teams delivering the solution.

Is the ADM always followed in order?

No. The ADM is iterative and is meant to be tailored. Phases can be revisited and iterated, for example cycling through B, C and D, or running several ADM cycles at different levels of the enterprise.

Explore more architecture content in the Enterprise Architecture category, or read about microservices architecture patterns.