Welcome to the TOGAF® Standard, Version 9.2, a standard of The Open Group

1. Introduction

Chapter Contents
1.1 Structure of this Document | 1.2 Structure of the TOGAF Library | 1.3 Executive Overview | 1.4 Information on Using the TOGAF Standard | 1.5 Why Join The Open Group?

The TOGAF standard is a framework for Enterprise Architecture. It may be used freely by any organization wishing to develop an Enterprise Architecture for use within that organization (see 1.4.1 Conditions of Use).

The TOGAF standard is developed and maintained by members of The Open Group, working within the Architecture Forum (refer to www.opengroup.org/architecture). The original development of TOGAF Version 1 in 1995 was based on the Technical Architecture Framework for Information Management (TAFIM), developed by the US Department of Defense (DoD). The DoD gave The Open Group explicit permission and encouragement to create Version 1 of the TOGAF standard by building on the TAFIM, which itself was the result of many years of development effort and many millions of dollars of US Government investment.

Starting from this sound foundation, the members of The Open Group Architecture Forum have developed successive versions of the TOGAF standard and published each one on The Open Group public website.

This version builds on previous versions of the TOGAF standard and updates the material available to architecture practitioners to assist them in building a sustainable Enterprise Architecture. Work on White Papers and Guides describing how to to integrate and use this standard with other frameworks and architectural styles has highlighted the universal framework parts of the standard, as well as industry, architecture style, and purpose-specific tools, techniques, and guidance. This work is embodied in the TOGAF Library.1

Although all of the TOGAF documentation works together as a whole, it is expected that organizations will customize it during adoption, and deliberately choose some elements, customize some, exclude some, and create others. For example, an organization may wish to adopt the TOGAF metamodel, but elect not to use any of the guidance on how to develop an in-house Technology Architecture because they are heavy consumers of cloud and Open Platform 3.0.

Regardless of your prior experience, you are recommended to read the Executive Overview (see 1.3 Executive Overview), where you will find an outline of The Open Group understanding of Enterprise Architecture and answers to fundamental questions, such as:

1.1 Structure of this Document

The structure of this document reflects the structure and content of an Architecture Capability within an enterprise, as shown in Figure 1-1 .


Figure 1-1: Structure of the TOGAF Standard

There are six parts to this document:

PART I
(Introduction) This part provides a high-level introduction to the key concepts of Enterprise Architecture and in particular the TOGAF approach. It contains the definitions of terms used throughout this standard.
PART II
(Architecture Development Method) This part is the core of the TOGAF framework. It describes the TOGAF Architecture Development Method (ADM) - a step-by-step approach to developing an Enterprise Architecture.
PART III
(ADM Guidelines & Techniques) This part contains a collection of guidelines and techniques available for use in applying the TOGAF approach and the TOGAF ADM. Additional guidelines and techniques are available in the TOGAF Library.
PART IV
(Architecture Content Framework) This part describes the TOGAF content framework, including a structured metamodel for architectural artifacts, the use of re-usable Architecture Building Blocks (ABBs), and an overview of typical architecture deliverables.
PART V
(Enterprise Continuum & Tools) This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise.
PART VI
(Architecture Capability Framework) This part discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture function within an enterprise.

The intention of dividing the TOGAF standard into these independent parts is to allow for different areas of specialization to be considered in detail and potentially addressed in isolation. Although all parts work together as a whole, it is also feasible to select particular parts for adoption while excluding others. For example, an organization may wish to adopt the ADM process, but elect not to use any of the materials relating to Architecture Capability.

As an open framework, such use is encouraged, particularly in the following situations:

1.2 Structure of the TOGAF Library

Accompanying this standard is a portfolio of guidance material, known as the TOGAF Library, to support the practical application of the TOGAF approach. 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.

The TOGAF Library is maintained under the governance of The Open Group Architecture Forum.

Library resources are organized into four sections:

Where resources within the Library apply to the deployment of the TOGAF ADM and make explicit reference to "anchor points" within the TOGAF standard they are classified within the Library as Dependent documents. Resources that provide guidance on how to utilize features described in the standard are classified as Supporting documents. Resources that relate to Enterprise Architecture in general, and that do not make any specific references to the TOGAF standard, are classified as EA General documents.

1.3 Executive Overview

This section provides an executive overview of Enterprise Architecture, the basic concepts of what it is (not just another name for IT Architecture), and why it is needed. It provides a summary of the benefits of establishing an Enterprise Architecture and adopting the TOGAF approach to achieve that.

What is an enterprise?

The TOGAF standard considers an "enterprise" to be any collection of organizations that have common goals.

For example, an enterprise could be:

The term "Enterprise" in the context of "Enterprise Architecture" can be applied to either an entire enterprise, encompassing all of its business activities and capabilities, information, and technology that make up the entire infrastructure and governance of the enterprise, or to one or more specific areas of interest within the enterprise. In both cases, the architecture crosses multiple systems, and multiple functional groups within the enterprise.

Confusion often arises from the evolving nature of the term "enterprise". An extended enterprise nowadays frequently includes partners, suppliers, and customers. If the goal is to integrate an extended enterprise, then the enterprise comprises the partners, suppliers, and customers, as well as internal business units.

The enterprise operating model concept is useful to determine the nature and scope of the Enterprise Architecture within an organization. Many organizations may comprise multiple enterprises, and may develop and maintain a number of independent Enterprise Architectures to address each one. These enterprises often have much in common with each other including processes, functions, and their information systems, and there is often great potential for wider gain in the use of a common architecture framework. For example, a common framework can provide a basis for the development of common building blocks and solutions, and a shareable Architecture Repository for the integration and re-use of business models, designs, information, and data.

Why is an Enterprise Architecture needed?

The purpose of Enterprise Architecture is to optimize across the enterprise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy.

Today's CEOs know that the effective management and exploitation of information and Digital Transformation are key factors to business success, and indispensable means to achieving competitive advantage. An Enterprise Architecture addresses this need, by providing a strategic context for the evolution and reach of digital capability in response to the constantly changing needs of the business environment.

For example, the rapid development of social media, Internet of Things, and cloud computing has radically extended the capacity of the enterprise to create new market opportunities.

Furthermore, a good Enterprise Architecture enables you to achieve the right balance between business transformation and continuous operational efficiency. It allows individual business units to innovate safely in their pursuit of evolving business goals and competitive advantage. At the same time, the Enterprise Architecture enables the needs of the organization to be met with an integrated strategy which permits the closest possible synergies across the enterprise and beyond.

What are the benefits of an Enterprise Architecture?

An effective Enterprise Architecture can bring important benefits to the organization. Specific benefits of an Enterprise Architecture include:

What specifically would prompt the development of an Enterprise Architecture?

Typically, preparation for business transformation needs or for radical infrastructure changes initiates an Enterprise Architecture review or development. Often key people identify areas of change required in order for new business goals to be met. Such people are commonly referred to as the "stakeholders" in the change. The role of the architect is to address their concerns by:

Without the Enterprise Architecture, it is highly unlikely that all the concerns and requirements will be considered and met.

What is an architecture framework?

An architecture framework is a foundational structure, or set of structures, which can be used for developing a broad range of different architectures. It should describe a method for designing a target state of the enterprise in terms of a set of building blocks, and for showing how the building blocks fit together. It should contain a set of tools and provide a common vocabulary. It should also include a list of recommended standards and compliant products that can be used to implement the building blocks.

Why use the TOGAF standard as a framework for Enterprise Architecture?

The TOGAF standard has been developed through the collaborative efforts of the whole community. Using the TOGAF standard results in Enterprise Architecture that is consistent, reflects the needs of stakeholders, employs best practice, and gives due consideration both to current requirements and the perceived future needs of the business.

Developing and sustaining an Enterprise Architecture is a technically complex process which involves many stakeholders and decision processes in the organization. The TOGAF standard plays an important role in standardizing and de-risks the architecture development process. The TOGAF standard provides a best practice framework for adding value, and enables the organization to build workable and economic solutions which address their business issues and needs.

Who would benefit from using the TOGAF standard?

Any organization undertaking, or planning to undertake, the development and implementation of an Enterprise Architecture for the support of business transformation will benefit from use of the TOGAF standard.

Organizations seeking Boundaryless Information Flow can use the TOGAF standard to define and implement the structures and processes to enable access to integrated information within and between enterprises.

Organizations that design and implement Enterprise Architectures using the TOGAF standard are assured of a design and a procurement specification that can facilitate an open systems implementation, thus enabling the benefits of open systems with reduced risk.

1.4 Information on Using the TOGAF Standard

1.4.1 Conditions of Use

The TOGAF standard is freely available for viewing online without a license. Alternatively, it can be downloaded and stored under license, as explained on the TOGAF information website.

In either case, the TOGAF standard can be used freely by any organization wishing to do so to develop an architecture for use within that organization. No part of it may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, for any other purpose including, but not by way of limitation, any use for commercial gain, without the prior permission of the copyright owners.

1.4.2 How Much Does the TOGAF Standard Cost?

The Open Group is committed to delivering greater business efficiency by bringing together buyers and suppliers of information systems to lower the barriers of integrating new technology across the enterprise. Its goal is to realize the vision of Boundaryless Information Flow.

The TOGAF standard is a key part of its strategy for achieving this goal, and The Open Group wants it to be taken up and used in practical architecture projects, and the experience from its use fed back to help improve it.

The Open Group therefore publishes it on its public web server, and allows and encourages its reproduction and use free-of-charge by any organization wishing to use it internally to develop an Enterprise Architecture. (There are restrictions on its commercial use, however; see 1.4.1 Conditions of Use .)

1.4.3 Downloads

Downloads of the TOGAF standard, including printable PDF files, are available under license from the TOGAF information website (refer to www.opengroup.org/togaf/downloads). The license is free to any organization wishing to use the standard entirely for internal purposes (for example, to develop an Enterprise Architecture for use within that organization).

1.5 Why Join The Open Group?

Organizations wishing to reduce the time, cost, and risk of implementing multi-vendor solutions that integrate within and between enterprises need The Open Group as their key partner.

The Open Group brings together the buyers and suppliers of information systems worldwide, and enables them to work together, both to ensure that IT solutions meet the needs of customers, and to make it easier to integrate IT across the enterprise. The TOGAF standard is a key enabler in this task.

Yes, the TOGAF standard itself is freely available. But how much will you spend on developing or updating your Enterprise Architecture? And how much will you spend on procurements based on that architecture? The price of membership of The Open Group is insignificant in comparison with these amounts.

In addition to the general benefits of membership, as a member of The Open Group you will be eligible to participate in The Open Group Architecture Forum, which is the development program within which the TOGAF standard is evolved, and in which TOGAF users come together to exchange information and feedback.

Members of the Architecture Forum gain:


Footnotes

1.
The TOGAF Library provides an online publicly available structured list of Guides, White Papers, and other resources. Refer to The Open Group Library at https://publications.opengroup.org/togaf-library.


return to top of page