Startreading the introduction part of the TOGAF Fundamental Content below, read the White Paper: An Introduction to the TOGAF Standard, 10th Edition, read the Pocket Guide, select a specific document on the left navigation panel, or search the standard.
A portfolio of learning paths based on bodies of knowledge derived from the TOGAF Standard, 10th Edition are now available. Read about the TOGAF Learning Paths and certifications. 1. IntroductionThe TOGAF Standard is a framework for Enterprise Architecture. It may be used freely by any organization wishing to develop anEnterprise Architecture for use within that organization (see 1.3.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 TOGAFVersion 1 in 1995 was based on the Technical Architecture Framework for Information Management (TAFIM), developed by the USDepartment of Defense (DoD). The DoD gave The Open Group explicit permission and encouragement to create Version 1 of the TOGAFStandard by building on the TAFIM, which itself was the result of many years of development effort and many millions of dollars ofUS Government investment.
This version builds on previous versions of the TOGAF Standard and updates the material available to architecture practitionersto assist them in building a sustainable Enterprise Architecture. Work on White Papers and Guides describing how to integrate anduse this standard with other frameworks and architectural styles has highlighted the universal framework parts of the standard, aswell as industry, architecture style, and purpose-specific tools, techniques, and guidance. This work is embodied in the TOGAFLibrary.1
Although all of the TOGAF documentation works together as a whole, it is expected that organizations will customize it duringadoption, and deliberately choose some elements, customize some, exclude some, and create others. For example, an organization maywish to adopt the TOGAF metamodel, but elect not to use any of the guidance on how to develop an in-house Technology Architecturebecause they are heavy consumers of cloud services.
You are recommended to first read the Executive Overview (see 1.1 Executive Overview), which includesan outline of The Open Group understanding of Enterprise Architecture and answers to fundamental questions, such as:
This section provides an executive overview of Enterprise Architecture, the basic concepts of what it is (not just another namefor IT Architecture), and why it is needed. It provides a summary of the benefits of establishing an Enterprise Architecture andadopting the TOGAF approach to achieve that.
The term "Enterprise" in the context of "Enterprise Architecture" can be applied to either an entire enterprise, encompassingall of its business activities and capabilities, information, and technology that make up the entire infrastructure and governanceof the enterprise, or to one or more specific areas of interest within the enterprise. An enterprise may include partners,suppliers, and customers as well as internal business units. In all cases, the architecture crosses multiple systems, and multiplefunctional groups within the enterprise.
The enterprise operating model concept is useful to determine the nature and scope of the Enterprise Architecture within anorganization. Many organizations may comprise multiple enterprises, and may develop and maintain a number of independent EnterpriseArchitectures to address each one. These enterprises often have much in common with each other including processes, functions, andtheir information systems, and there is often great potential for wider gain in the use of a common architecture framework. Forexample, a common framework can provide a basis for the development of common building blocks and solutions, and a shareableArchitecture Repository for the integration and re-use of business models, designs, information, and data.
The purpose of Enterprise Architecture is to optimize across the enterprise the often fragmented legacy of processes (bothmanual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the businessstrategy.
The effective management and exploitation of information and Digital Transformation are key factors to business success, andindispensable means to achieving competitive advantage. An Enterprise Architecture addresses this need, by providing a strategiccontext for the evolution and reach of digital capability in response to the constantly changing needs of the businessenvironment.
Furthermore, a good Enterprise Architecture enables you to achieve the right balance between business transformation andcontinuous operational efficiency. It allows individual business units to innovate safely in their pursuit of evolving businessgoals and competitive advantage. At the same time, the Enterprise Architecture enables the needs of the organization to be met withan integrated strategy which permits the closest possible synergies across the enterprise and beyond.
Often key people identify areas of change required in order for new business goals to be met. Such people are commonly referredto as the "stakeholders" in the change. The role of the architect is to address their concerns by:
An architecture framework is a foundational structure, or set of structures, which can be used for developing a broad range ofdifferent architectures. It should include a method for describing both a baseline and target state of the enterprise, in terms ofa set of building blocks for showing how the building blocks fit together and planning the evolution from baseline to targetstates.
The TOGAF Standard has been developed through the collaborative efforts of the whole community. Using the TOGAF Standard resultsin Enterprise Architecture that is consistent, reflects the needs of stakeholders, employs best practice, and gives dueconsideration 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 anddecision processes in the organization. The TOGAF Standard plays an important role in standardizing and de-risks the architecturedevelopment process. The TOGAF Standard provides a best practice framework for adding value, and enables the organization to buildworkable and economic solutions which address their business issues and needs.
The TOGAF Standard value proposition is to enable organizations to operate in an efficient and effective way using a proven andrecognized set of best practices, across the enterprise and in different sectors to address specific business and technologytrends.
A key consideration is that guidance provided by the standard is intended to be adapted to address different needs andparticular use-cases. That means it can be used to create a sustainable Enterprise Architecture for a broad range of use-cases,including agile enterprises and Digital Transformation.
Any organization undertaking, or planning to undertake, the development and implementation of an Enterprise Architecture for thesupport of business transformation will benefit from use of the TOGAF Standard.
Organizations seeking Boundaryless Information FlowTM can use the TOGAF Standard to define and implement thestructures 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 aprocurement specification that can facilitate an open systems implementation, thus enabling the benefits of open systems withreduced risk.
To get the greatest benefit from Enterprise Architecture it should be done early and throughout the change process to helpdecision-makers understand the implications of their decisions. Without this understanding, costly mistakes can be made andEnterprise Architecture is not serving it fullest potential. Enterprise Architecture done after decisions are made is merelydocumentation of those decisions or at best enforcement of those decisions. No insight is gained as to the effect of thosedecisions which could be far-reaching and perhaps detrimental.
In either case, the TOGAF Standard can be used freely by any organization wishing to do so to develop an architecture for usewithin that organization. No part of it may be reproduced, stored in a retrieval system, or transmitted, in any form or by anymeans, electronic, mechanical, photocopying, recording, or otherwise, for any other purpose including, but not by way oflimitation, any use for commercial gain, without the prior permission of the copyright owners.
The Open Group is committed to delivering greater business efficiency by bringing together buyers and suppliers of informationsystems to lower the barriers of integrating new technology across the enterprise. Its goal is to realize the vision ofBoundaryless 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 inpractical 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 usefree-of-charge by any organization wishing to use it internally to develop an Enterprise Architecture. (There are restrictions onits commercial use, however; see 1.3.1 Conditions of Use .)
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 isfree to any organization wishing to use the standard entirely for internal purposes (for example, to develop an EnterpriseArchitecture for use within that organization).
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. TheTOGAF Standard is a key enabler in this task.
3a8082e126