TOGAF 9.2 is an evolutionary update to 9.1 — the core ADM, four domains, and governance model are all retained. The changes focus on structure, Business Architecture expansion, tooling, and alignment to digital trends. 40% of 9.1 content changed or enhanced.

40%

Retained unchanged from 9.1

36%

Changed or enhanced content

24%

Brand new content

KEY CHANGES — 12 dimensions

🆕 NEW

Document structure — modular

9.1: Single monolithic document — 650 pages, 7 parts

9.2: Core standard slimmed down + separate Series Guides. First step toward a modular architecture ecosystem. Makes future updates far easier.

🆕 NEW

TOGAF Library introduced

9.1: No TOGAF Library concept

9.2: TOGAF Library becomes the overarching structure — containing the TOGAF Standard, Series Guides, and white papers. Enterprise Continuum is one of its two key dimensions.

🔄 CHANGED

Business Architecture — significantly expanded

9.1: Basic business architecture coverage

9.2: Value Chains, Value Streams, and Business Capabilities explicitly required in Phase A (Architecture Vision). Business Architecture phase B expanded with new entities and artefacts.

🔄 CHANGED

ADM — anti-waterfall language

9.1: ADM described iteratively but susceptible to waterfall misinterpretation

9.2: ADM description explicitly precludes a waterfall interpretation. Language updated throughout to support Agile thinking — always iterative, now unambiguous.

🔄 CHANGED

Preliminary phase — tools strategy

9.1: Tools mentioned briefly in context of architecture tools

9.2: Preliminary now includes a broad tools strategy — business modelling tools, management tools, repository management, and governance tools — beyond just architecture tools.

🔄 CHANGED

Content Metamodel updated

9.1: Original content metamodel entities

9.2: Content Metamodel enhanced with new Business Architecture entities — Value Streams and Business Capabilities added as first-class metamodel entities with formal definitions.

🔄 ALIGNED

ISO/IEC/IEEE 42010:2011 alignment

9.1: Referenced an earlier version of ISO 42010

9.2: Consequent changes throughout the standard to align terminology — Concern, View, Viewpoint, and Architecture Description updated to match the 2011 standard precisely.

🆕 NEW

Digital transformation focus

9.1: IT-focused framework — business transformation implied but not explicit

9.2: Explicit focus on digital trends and business transformation beyond IT. TOGAF positioned as a business-wide framework, not an IT framework.

🔄 CHANGED

Terminology & definitions

9.1: Large glossary with some ambiguity — explanatory material embedded in definitions

9.2: Terms worked over for clarity. Extraneous material shown as notes, not embedded in definitions. Alignment with ISO 42010 also updated several core terms.

🆕 NEW

Security Architecture Series Guide

9.1: Security referenced but not deeply covered

9.2: Security architecture guide extended into a dedicated Series Guide. Also updated security considerations in the ADM application of each phase.

🔄 CHANGED

Phase A — early modelling requirement

9.1: Architecture Vision — general vision and concerns

9.2: Phase A now explicitly requires creating Value Chains, Value Streams, and Business Capabilities early — supporting business thinking primacy over IT focus from the very first phase.

🆕 NEW

TOGAF Essentials 2018 bridge credential

9.1: No bridge path — certification levels Foundation + Certified

9.2: 3-hour TOGAF Essentials 2018 refresher for 9.1 holders covering all 9.2 changes. Certification levels remain unchanged — same Foundation and Certified exams, updated syllabus from Nov 2018.

✓ WHAT STAYED THE SAME — core foundations retained from 9.1

ADM — all 10 phases unchanged 4 architecture domains (BDAT) Architecture Repository — 6 classes Building Blocks (ABB / SBB) Enterprise Continuum — 4 levels Architecture governance model Architecture Board structure 4 compliance levels Certification levels — Foundation + Certified Core ADM deliverables and artefacts Requirements Management — central continuous

The ADM 10 phases are fully retained from TOGAF 9.1. The key 9.2 change is explicit anti-waterfall language and the expansion of Phase A and Phase B with Business Architecture modelling. Click any phase for 9.2-specific details.

Select a phase

Click any phase on the left to explore its 9.2-specific purpose, steps, outputs, and what changed from 9.1.

The four domains BDAT remain unchanged in structure. The significant 9.2 change is in Business Architecture — Value Chains, Value Streams, and Business Capabilities are now explicitly required from Phase A onwards.

🏢

Business Architecture — Phase B Expanded in 9.2

The WHY and HOW of the enterprise — significantly strengthened

Business strategy, goals, and key business drivers

Organisational structures, functions, and roles

Business Capabilities — what the enterprise can do9.2

Value Chains — end-to-end value delivery modelling9.2

Value Streams — the flow of value to stakeholders9.2

Output: Business Architecture Definition Document

💾

Data Architecture — Phase C Retained

The information assets of the enterprise

Types and sources of data required by the enterprise

Logical and physical data models

Data management and lifecycle governance policies

Data governance and master data management

Output: Data Architecture Definition Document

📱

Application Architecture — Phase C Retained

The applications that process and manage data

Application portfolio — what systems exist and are needed

Application interactions and integration dependencies

Application-to-business-function and capability mapping

Legacy systems and rationalisation candidates

Output: Application Architecture Definition Document

⚙️

Technology Architecture — Phase D Retained

The infrastructure enabling all other architectures

Software and hardware infrastructure components

Network and communications infrastructure

Technology standards, platforms, and products

Cloud, virtualisation, and security infrastructure

Output: Technology Architecture Definition Document

9.2 BUSINESS ARCHITECTURE FOCUS — the three new required modelling techniques

Business Capability

What the enterprise can do — independent of who does it or how. The most stable element of the business. Used to assess gaps and investment priorities.

Value Chain

A set of activities the enterprise undertakes to deliver value. Shows how each activity contributes to the overall value delivered to the customer or stakeholder.

Value Stream

The end-to-end flow of activities that deliver a specific value outcome to a specific stakeholder. More detailed than a Value Chain — shows the sequence and interactions.

In 9.2, these three techniques are required from Phase A (Architecture Vision) — not just Phase B

The biggest structural change in 9.2: the monolithic 7-part document is broken into a smaller Core Standard plus separate Series Guides. This makes the standard easier to use, maintain, and extend without rewriting the whole document.

TOGAF 9.1 Structure — Monolithic

Single document — ~650 pages

7 parts — all embedded in one publication

Problems with the monolithic approach:

→Hard to update — 100s of change requests pending

→One change requires reviewing the whole document

→Cannot extend specific areas without full revision

TOGAF 9.2 Structure — Modular

TOGAF Library (overarching)

Contains: Core Standard + Series Guides + White Papers

Benefits of the modular approach:

✓Core standard is lean and stable

✓Series Guides can be updated independently

✓New guides added without touching the core

CORE STANDARD — 7 parts retained (content refined)

Part I — Introduction

Retained — key concepts and EA fundamentals

Part II — ADM Updated

Anti-waterfall language, Phase A and B expansions

Part III — Guidelines Updated

Additional agile and security guidance added

Part IV — Content Updated

Metamodel updated — Value Streams, Capabilities added

Part V — Continuum

Retained — TOGAF Library now sits above this

Part VI — Reference Models

TRM and III-RM retained

Part VII — Capability Updated

Architecture Capability Framework refined

TOGAF SERIES GUIDES — new in 9.2, published alongside the Core Standard

Business Capabilities Guide

How to identify, define, and use Business Capabilities in architecture — directly supporting the Business Architecture expansion in 9.2

Value Streams Guide

How to model Value Streams to describe end-to-end flows of value delivery to specific stakeholders

Security Architecture Guide Extended

Extended from 9.1 — comprehensive guidance on incorporating security across all four domains and ADM phases

Industry Models Guide

Guidance on mapping TOGAF to industry-specific reference models — financial services, healthcare, government

Practitioners Approach Guide

A practitioner-oriented guide to developing EA following the TOGAF ADM — real-world application guidance

Migration Planning Guide

Detailed guidance on Phases E and F — opportunities, solutions, and migration planning in practice

TOGAF LIBRARY — the new overarching ecosystem (new in 9.2)

TOGAF Standard

The Core — 7 parts · stable · foundation

Series Guides

Specialist guidance · evolving · topic-specific

White Papers

World Class EA series · best practices · emerging trends

The two dimensions of the TOGAF Library: the Enterprise Continuum (from generic to specific) and the Architecture Capability (breadth of usage)

Building Blocks are unchanged in 9.2 — ABBs and SBBs retain the same definitions and qualities from 9.1. The Content Metamodel that organises them has been updated to include new Business Architecture entities.

Architecture Building Block (ABB)

What is needed — the specification Unchanged

•Captures architecture requirements — what must be done

•Technology-agnostic — independent of any product or vendor

•Drives the selection of Solutions Building Blocks

•Developed in ADM Phases A through D

Example: "An identity management service providing single sign-on"

Solutions Building Block (SBB)

How it is implemented — the product Unchanged

•Represents a specific product, service, or component

•Technology-specific — bound to a vendor or product

•Fully defined — ready to purchase, build, or reuse

•Developed in ADM Phases E and F

Example: "Microsoft Entra ID implementing the SSO service ABB"

🔄 CONTENT METAMODEL — what changed in 9.2

NEW entities added

+Business Capability — formal metamodel entity

+Value Stream — formal metamodel entity

+Capability Increment — phased delivery support

UPDATED entity relationships

~Business Service → linked to Value Streams

~Organisation Unit → mapped to Capabilities

~Process → related to Value Stream stages

3 WORK PRODUCT TYPES — unchanged from 9.1

Deliverable

Contractually specified work product formally reviewed and signed off — the end product of an architecture phase.

Artefact

Architectural work product describing architecture from a specific viewpoint — diagrams, catalogues, matrices.

Building Block

Reusable component — combined with others to deliver architectures and solutions. ABB or SBB.

The Enterprise Continuum is retained unchanged from 9.1. The 9.2 addition is the TOGAF Library sitting above the Continuum as the overarching ecosystem — the Enterprise Continuum becomes one of its two key dimensions.

🆕 9.2 — TOGAF LIBRARY (new overarching structure)

TOGAF Standard (Core) · Series Guides · White Papers · Open Badges

↓ contains ↓

ENTERPRISE CONTINUUM (retained from 9.1)

ARCHITECTURE CONTINUUM — what is needed

FoundationCommon SystemsIndustryOrg-Specific →

SOLUTIONS CONTINUUM — how it is implemented

FoundationCommon SystemsIndustryOrg-Specific →

Foundation

TOGAF TRM · generic

Common Systems

Cross-industry shared

Industry

Sector-specific models

Organisation

Enterprise-specific

ARCHITECTURE REPOSITORY — 6 classes retained from 9.1

Architecture Metamodel

Organisation-specific metamodel — the rules for content

Architecture Capability

Parameters, processes, roles of the EA function

Architecture Landscape

Strategic, segment, and capability architectures

Standards Information Base

Industry, legal, and organisational technology standards

Reference Library

Reference architectures, models, and patterns

Governance Log

Architecture decisions, assessments, and waivers

Architecture Governance is retained unchanged from 9.1 in its core structure. The 9.2 change is expanded guidance on governance in the Preliminary phase — broader definition of what tools and approaches support governance.

GOVERNANCE HIERARCHY — retained from 9.1

Corporate Governance — overall enterprise direction and accountability

↓

Technology Governance — IT strategies, policies, and enterprise technology standards

↓

IT Governance — IT resources and performance management

↓

Architecture Governance — architectural decisions, compliance, and standards

ARCHITECTURE BOARD — responsibilities (unchanged)

Provide architectural oversight

Ensuring all architecture is consistent with the enterprise architecture

Identify reuse opportunities

Finding where architecture components can be shared across projects

Manage dispensations

Granting time-limited waivers from architecture compliance

Approve architecture changes

Reviewing and approving architecture change requests

Monitor compliance

Conducting compliance reviews of implementation projects

Manage standards evolution

Updating and retiring architecture standards and patterns

4 COMPLIANCE LEVELS — unchanged from 9.1

✓ Fully Conformant

All mandatory architecture requirements met — no deviations

~ Conformant

Mandatory met — some recommended items not fully addressed

⚠ Partially Conformant

Significant gaps — dispensation required to proceed

✗ Non-Conformant

Significant departure — escalation and remediation required

36 flash cards — includes all 9.1 core concepts plus 9.2-specific content: TOGAF Library, Series Guides, Business Capabilities, Value Streams, Value Chains, and anti-waterfall ADM. Filter by category to focus on what is new.

Card 1 of 36

QUESTION

Loading...

Tap to reveal the answer

ANSWER

Key definitions for TOGAF 9.2 — new 9.2 concepts are marked. Concepts retained from 9.1 appear with their updated or clarified 9.2 definitions.

TOGAF 9.2 interactive infographic study manual — what changed from 9.1, ADM phases, Series Guides, Business Architecture expansion, and flash cards