An Introduction To The Togaf Standard, Version 9.2: A White Paper by
An Introduction To The Togaf Standard, Version 9.2: A White Paper by
April 2018
An Introduction to the TOGAF® Standard, Version 9.2
This White Paper is an informational document and does not form part of the TOGAF documentation set. Readers should note
that this document has not been approved through the formal Open Group Standards Process and does not represent the formal
consensus of The Open Group Architecture Forum.
ArchiMate®, DirecNet®, Making Standards Work®, OpenPegasus®, Platform 3.0®, The Open Group®, TOGAF®, UNIX®,
UNIXWARE®, X/Open®, and the Open Brand X® logo are registered trademarks and Boundaryless Information Flow™,
Build with Integrity Buy with Confidence™, Dependability Through Assuredness™, EMMM™, FACE™, the FACE™ logo,
IT4IT™, the IT4IT™ logo, O-DEF™, O-PAS™, Open FAIR™, Open Platform 3.0™, Open Process Automation™, Open
Trusted Technology Provider™, SOSA™, the Open O™ logo, and The Open Group Certification logo (Open O and check™)
are trademarks of The Open Group. All other brands, company, and product names are used for identification purposes only
and may be trademarks that are the sole property of their respective owners.
Table of Contents
Executive Summary................................................................... 4
References............................................................................... 20
Executive Summary
This White Paper provides an introduction to the TOGAF Standard, Version 9.2.
Topics addressed include:
Changes between Version 9.1 and Version 9.2 of the TOGAF standard
The TOGAF standard is developed and maintained by members of The Open Group, working within the
Architecture Forum. The original development of TOGAF Version 1 in 1995 was based on the US
Department of Defense Technical Architecture Framework for Information Management (TAFIM). Starting
from this sound foundation, The Open Group Architecture Forum has developed successive versions of the
TOGAF standard and published each one on The Open Group public website.
Accompanying the standard is the TOGAF Library. The TOGAF Library is a reference library containing
guidelines, templates, patterns, and other forms of reference material to accelerate the creation of new
architectures for the enterprise.
This White Paper covers the TOGAF Standard, Version 9.2, published in April 2018. It is an update
providing additional guidance, introducing structural changes to support the TOGAF Library (an extensive
collection of reference material), correcting errors, and removing obsolete content. A description of the
changes is provided in Changes Between Version 9.1 and Version 9.2 of the TOGAF Standard (on page 13).
The TOGAF standard can be used for developing a broad range of different Enterprise Architectures. It
complements, and can be used in conjunction with, other frameworks that are more focused on specific
deliverables for particular vertical sectors such as Government, Telecommunications, Manufacturing,
Defense, and Finance. A key part of the TOGAF standard is the method – the TOGAF Architecture
Development Method (ADM) – for developing an Enterprise Architecture that addresses business needs.
Part II: This part is the core of the TOGAF framework. It describes the TOGAF
Architecture Development Method Architecture Development Method (ADM) – a step-by-step approach to
developing an Enterprise Architecture.
Part III: This part contains a collection of guidelines and techniques available
ADM Guidelines and Techniques for use in applying the TOGAF approach and the TOGAF ADM.
Additional guidelines and techniques are also in the TOGAF Library.
Part IV: This part describes the TOGAF content framework, including a
Architecture Content Framework structured metamodel for architectural artifacts, the use of re-usable
Architecture Building Blocks (ABBs), and an overview of typical
architecture deliverables.
Part VI: This part discusses the organization, processes, skills, roles, and
Architecture Capability Framework responsibilities required to establish and operate an architecture
practice within an enterprise.
Included in the TOGAF Library to support the TOGAF Standard, Version 9.2 is a set of supporting guidance
documents known as the TOGAF Series Guides. The TOGAF Series Guides contain detailed guidance on
how to use the TOGAF framework, and are expected to be the most rapidly developing part of the TOGAF
documentation set. While the TOGAF framework documented in the standard is expected to be long-lived
and stable, guidance on the use of the TOGAF framework can be industry, architectural style, purpose, and
problem-specific.
• TOGAF® Series Guide: The TOGAF® Leader’s Guide to Establishing and Evolving an EA Capability
• TOGAF® Series Guide: A Practitioners’ Approach to Developing Enterprise Architecture Following the
TOGAF® ADM
• TOGAF® Series Guide: Using the TOGAF® Framework to Define and Govern Service-Oriented
Architectures
• TOGAF® Series Guide: The TOGAF® Integrated Information Infrastructure Reference Model (III-RM):
An Architected Approach to Boundaryless Information Flow™
“The fundamental concepts or properties of a system in its environment embodied in its elements,
relationships, and in the principles of its design and evolution.”
The TOGAF standard embraces ISO/IEC/IEEE 42010:2011 terminology, extending it to also define a second
meaning depending upon the context:
“The structure of components, their inter-relationships, and the principles and guidelines governing their
design and evolution over time.”
Business Architecture The business strategy, governance, organization, and key business
processes.
Data Architecture The structure of an organization’s logical and physical data assets and data
management resources.
Application Architecture A blueprint for the individual applications to be deployed, their interactions,
and their relationships to the core business processes of the organization.
*
To be published in 2018.
1
ISO/IEC/IEEE 42010:2011, Systems and Software Engineering – Architecture Description.
Technology Architecture The logical software and hardware capabilities that are required to support the
deployment of business, data, and application services. This includes IT
infrastructure, middleware, networks, communications, processing, and
standards.
Central to the TOGAF framework is the Architecture Development Method (ADM), documented in Part II of
the standard. The Architecture Capability (documented in Part VI of the standard) operates the method. The
method is supported by a number of guidelines and techniques (documented in Part III of the standard, and
the TOGAF Library). This produces content to be stored in the repository (documented in Part IV of the
standard), which is classified according to the Enterprise Continuum (documented in Part V of the standard).
The repository can be initially populated with the TOGAF Reference Models and other reference materials
(documented in the TOGAF Library).
The ADM describes how to derive an organization-specific Enterprise Architecture that addresses business
requirements. The ADM is the major component of the TOGAF framework and provides guidance for
architects on a number of levels:
• It provides a narrative of each architecture phase, describing the phase in terms of objectives, approach,
inputs, steps, and outputs; the inputs and outputs sections provide a definition of the architecture content
structure and deliverables (a detailed description of the phase inputs and phase outputs is given in the
Architecture Content Framework)
ADM Guidelines and Techniques provides a number of guidelines and techniques to support the
application of the ADM. The guidelines include adapting the ADM to deal with a number of usage scenarios,
including different process styles – the use of iteration, and applying the ADM across the Architecture
Landscape. There is also a high-level description of how to use the TOGAF framework with different
architectural styles using SOA as an example. The techniques support specific tasks within the ADM (such as
capability-based planning, defining principles, gap analysis, migration planning, risk management,
stakeholder management, etc.). Additional guidelines and techniques are also available in the TOGAF
Library (for example, guidance on the business scenarios technique).
The Architecture Content Framework provides a detailed model of architectural work products, including
deliverables, artifacts within deliverables, and the Architecture Building Blocks (ABBs) that artifacts
represent.
The Enterprise Continuum provides a model for structuring a virtual repository and provides methods for
classifying architecture and solution artifacts, showing how the different types of artifacts evolve, and how
they can be leveraged and re-used. This is based on architectures and solutions (models, patterns, architecture
descriptions, etc.) that exist within the enterprise and in the industry at large, and which the enterprise has
collected for use in the development of its architectures.
The Architecture Capability Framework is a set of resources, guidelines, templates, background information,
etc. provided to help the architect establish an architecture practice within an organization.
Modular Structure
• Greater usability – a defined purpose for each part, and can be used in isolation as a standalone set of
guidelines
• Accompanying the standard is a portfolio of guidance material, known as the TOGAF Library, to support
the practical application of the TOGAF approach
Content Framework
The TOGAF standard includes a content framework to drive greater consistency in the outputs that are
created when following the Architecture Development Method (ADM). The TOGAF content framework
provides a detailed model of architectural work products.
Extended Guidance
The TOGAF standard features an extended set of concepts and guidelines to support the establishment of an
integrated hierarchy of architectures being developed by teams within larger organizations that operate within
an overarching architectural governance model. In particular, the following concepts are included:
• Partitioning – a number of techniques and considerations on how to partition the various architectures
within an enterprise
• Architecture Repository – a logical information model for an Architecture Repository which can be used
as an integrated store for all outputs created by executing the ADM
• Capability Framework – a structured definition of the organization, skills, roles, and responsibilities
required to operate an effective Enterprise Architecture Capability; the TOGAF standard also provides
guidance on a process that can be followed to identify and establish an appropriate Architecture
Capability
Architectural Styles
The TOGAF standard is designed to be flexible and it can be used with various architectural styles. Examples
are provided both in the TOGAF standard, in Part III (ADM Guidelines and Techniques), and in the TOGAF
Library.
Together these comprise a set of supporting materials that show in detail how the ADM can be applied to
specific situations; for example:
• The varying uses of iteration that are possible within the ADM and when each technique should be
applied
• The various types of architecture development required within an enterprise and how these relate to one
another
• The use of the TOGAF ADM with Service-Oriented Architectures (SOAs), risk and security, etc. (these
specific examples are documented in the TOGAF Library)
The TOGAF Standard, Version 9.2 includes additional detailed information over earlier versions of the
TOGAF standard for supporting the execution of the ADM. Particular areas of enhancement are:
• The Architecture Vision and Business Architecture phases feature extended guidance on development of
the Business Architecture; this includes focus on Business Capabilities, Value Streams, and Organization
Maps
• The Technology Architecture phase recognizes that emerging technologies are increasingly leading to
technology-driven change
Supporting Guides
A significant change introduced with the TOGAF Standard, Version 9.2 is the addition of TOGAF Series
Guides and related Guides from The Open Group. These allow for additional guidance to be provided and
also maintained separately from the standard. At the time of writing, the following had been published (with
more planned to appear in 2018):
• TOGAF® Series Guide: The TOGAF® Leader’s Guide to Establishing and Evolving an EA Capability
• TOGAF® Series Guide: A Practitioners’ Approach to Developing Enterprise Architecture Following the
TOGAF® ADM
• TOGAF® Series Guide: The TOGAF® Integrated Information Infrastructure Reference Model (III-RM):
An Architected Approach to Boundaryless Information Flow™
• TOGAF® Series Guide: Using the TOGAF® Framework to Define and Govern Service-Oriented
Architectures
2 Core Concepts 2 Core Concepts References to ISO/IEC/IEEE 42010 are updated here and
throughout the document to the 2011 edition.
The structure of the Architecture Repository is updated to include
the Solutions Landscape and Architecture Requirements
Repository.
A reference to the IT4IT™ Reference Architecture is added as an
example of adopting other elements to integrate with when
tailoring the TOGAF framework.
Minor editorial cleanup is applied to this (and all chapters).
6 Preliminary Phase 5 Preliminary Phase The Approach section is moved to the end of the chapter.
The TOGAF Library is named as an input.
The step “Implement architecture tools” is now renamed to
“Develop strategy and implementation plans for tools and
techniques”, and additional guidance provided.
Terminology tailoring now recommends creation of an Enterprise
Glossary.
7 Phase A: 6 Phase A: The Approach section is moved to the end of the chapter and
Architecture Vision Architecture Vision revised extensively.
One of the steps is renamed from “Evaluate business capabilities”
to “Evaluate capabilities”.
Explicit mention of a Stakeholder Map is added into the Develop
the Architecture Vision step.
Guidance is added on evaluation of business models and
identification of required business capabilities.
New artifacts added: Business Model diagram, Business
Capability map, Value Stream map
8 Phase B: Business 7 Phase B: Business The Approach section is moved to the end of the chapter and
Architecture Architecture revised extensively to include further advice on Business
Architecture.
The first objective is revised to address the Statement of
Architecture Work (rather than the Request for Architecture Work
as it stated previously).
Artifacts added: Value Stream catalog, Business Capabilities
catalog, Value Stream Stages catalog, Value Stream/Capability
matrix, Strategy/Capability matrix, Capability/Organization matrix,
Business model diagram, Business Capability map, Value Stream
map, Organization map
9 Phase C: 8 Phase C: Information The phase text is simplified to just Objectives and Approach, with
Information Systems Systems Architectures pointers to the following two chapters for details.
Architectures
10 Phase C: 9 Phase C: Information The first objective is revised to address the Statement of
Information Systems Systems Architectures Architecture Work (rather than the Request for Architecture Work
Architectures – Data – Data Architecture as it stated previously).
Architecture The Approach section is moved to the end of the chapter with a
minor revision to example standards.
14 Phase F: Migration 13 Phase F: Migration The Approach section is moved to the end of the chapter with
Planning Planning minor revisions.
15 Phase G: 14 Phase G: The Approach section is moved to the end of the chapter with
Implementation Implementation minor revisions.
Governance Governance
16 Phase H: 15 Phase H: The Approach section is moved to the end of the chapter.
Architecture Change Architecture Change
Management Management
17 ADM Architecture 16 ADM Architecture The Approach section is moved to the end of the chapter.
Requirements Requirements References to the “Requirements Repository” are changed to the
Management Management “Architecture Requirements Repository”.
19 Applying Iteration 18 Applying Iteration to Minor editorial changes only. No substantive changes.
to the ADM the ADM
20 Applying the ADM 19 Applying the ADM Minor editorial changes only. No substantive changes.
across the Across the
Architecture Architecture
Landscape Landscape
21 Security Removed This chapter is removed and advice on risk and security is
Architecture and the published separately as:
ADM Integrating Risk and Security within a TOGAF Enterprise
Architecture, available at: www.opengroup.org/library/g152
22 Using TOGAF to Removed This chapter is removed. Content now published as:
®
Define & Govern TOGAF Series Guide: Using the TOGAF® Framework to Define
SOAs and Govern Service-Oriented Architectures, available at:
www.opengroup.org/library/g174
24 Stakeholder 21 Stakeholder The example stakeholder map has been updated to include the
Management Management new Business Architecture artifacts.
27 Gap Analysis 23 Gap Analysis Text is updated to refer to the TOGAF TRM rather than the
Technical Reference Model. Minor editorials. No substantive
changes otherwise.
28 Migration Planning 24 Migration Planning Rather than referring directly to the TOGAF TRM, the text is
Techniques Techniques updated to now refer to services from the defined taxonomy in the
enterprise.
29 Interoperability 25 Interoperability The end Summary section has been deleted. No substantive
Requirements Requirements changes otherwise.
31 Risk Management 27 Risk Management Minor editorial changes only. No substantive changes.
34 Content 30 Content Metamodel The descriptions of the concepts of Catalog, Matrix, and Diagram
Metamodel are moved to Chapter 31.
Platform Services are renamed Technology Services.
The following entities are added to the core metamodel: Business
Capability, Course of Action, Value Stream
The list of artifacts by phase is removed from this chapter.
The changes to the metamodel for extensions are now referred to
as Extensions.
The metamodel diagrams and the metamodel relationships tables
are revised. New relationships are added, and others have been
changed. Changes have been made for consistency across the
diagrams and relationships table.
The Location entity is now a global entity, so text about it being
added as part of the Infrastructure Consolidation extension is
removed. Figures now show it as a white core element.
The Communications and Engineering diagram is renamed to the
Network and Communications diagram.
36 Architecture 32 Architecture The description of tailoring changes has been changed from
Deliverables Deliverables project and process management frameworks to simply
management frameworks.
Minor editorial changes. No substantive changes.
Part V: Part V:
Enterprise Enterprise
Continuum & Tools Continuum & Tools
42 Tools for 38 Tools for Minor editorial changes only. No substantive changes.
Architecture Architecture
Development Development
50 Architecture 44 Architecture Reference to the White Paper: Mapping between TOGAF 8.1 and
Governance Governance COBIT 4.0 is removed.
Minor editorial changes also applied.
52 Architecture Skills 46 Architecture Skills Minor editorial changes only. No substantive changes.
Framework Framework
Appendices Appendices
References
(Please note that the links below are good at the time of writing but cannot be guaranteed for the future.)
• Business Capabilities, an Open Group Guide (G161), published by The Open Group, March 2016; refer
to: www.opengroup.org/library/g161
• Integrating Risk and Security within a TOGAF ® Enterprise Architecture, an Open Group Guide (G152),
published by The Open Group, January 2016; refer to: www.opengroup.org/library/g152
• The TOGAF® Standard, Version 9.2, a standard of The Open Group (C182), published by The Open
Group, April 2018; refer to: www.opengroup.org/library/c182
• TOGAF® Series Guide: A Practitioners’ Approach to Developing Enterprise Architecture Following the
TOGAF® ADM (G186), published by The Open Group, March 2018; refer to: www.opengroup.org/g186
• TOGAF® Series Guide: Business Scenarios (G176), published by The Open Group, September 2017;
refer to: www.opengroup.org/library/g176
• TOGAF® Series Guide: The TOGAF® Integrated Information Infrastructure Reference Model (III-RM):
An Architected Approach to Boundaryless Information Flow™ (G179), published by The Open Group,
November 2017; refer to: www.opengroup.org/g179
• TOGAF® Series Guide: The TOGAF® Leader’s Guide to Establishing and Evolving an EA Capability
(G184), published by The Open Group, February 2018; refer to: www.opengroup.org/library/g184
• TOGAF® Series Guide: The TOGAF® Technical Reference Model (TRM) (G175), published by The
Open Group, September 2017; refer to: www.opengroup.org/library/g175
• TOGAF® Series Guide: Using the TOGAF® Framework to Define and Govern Service-Oriented
Architectures (G174), published by The Open Group, September 2017; refer to:
www.opengroup.org/library/g174
• TOGAF® Series Guide: Value Streams (G178), published by The Open Group, October 2017; refer to:
www.opengroup.org/library/g178
Andrew Josey is VP Standards & Certification overseeing all certification and testing programs of The Open
Group. He also manages the standards process for The Open Group. At The Open Group, he has led many
standards development projects including specification and certification development for the ArchiMate ®,
IT4IT™, TOGAF®, Open FAIR™, POSIX®, and UNIX® programs. He is a member of the IEEE, USENIX,
and the Association of Enterprise Architects (AEA). He holds an MSc in Computer Science from University
College London.
• Capture, understand, and address current and emerging requirements, establish policies, and share best
practices
• Facilitate interoperability, develop consensus, and evolve and integrate specifications and open source
technologies