the TOGAF framework. It describes the TOGAF Architecture Development Method (ADM) – a multi-phase, iterative approach to developing an Enterprise Architecture.Accompanying the standard is the TOGAF Library4. The TOGAF Library is a library of resources to support usage of the TOGAF standard. It contains guidelines, templates, patterns, and other forms of reference material to accelerate the creation of new architectures for an enterprise.
Recently added are the TOGAF Series Guides, a series of documents containing detailed guidance on how to use the TOGAF framework.
The current titles in the TOGAF Series Guides5 are summarized in Table 2.
Table 2: TOGAF Series Guides
| Title | Description |
| TOGAF Series Guide:A Practitioners’ Approach to Developing Enterprise Architecture Following the TOGAF ADM | This document puts forward an approach to develop, maintain, and use an Enterprise Architecture that aligns to a set of requirements and expectations of the stakeholders and enables predictable value creation. |
| TOGAF Series Guide:Architecture Project Management | This document provides architecture project teams with an overall view and detailed guidance on what processes, tools, and techniques of PRINCE2® or PMBOK® can be applied alongside the TOGAF ADM for project planning, monitoring, and control. |
| TOGAF Series Guide:Business Capabilities | This document describes what a business capability is, and how business capabilities can be used to enhance business analysis and planning. |
| TOGAF Series Guide:Business Models | This document provides a basis for Enterprise Architects to understand and utilize business models, which describe the rationale of how an organization creates, delivers, and captures value. |
| TOGAF Series Guide:Business Scenarios | This document describes the business scenarios method, which is a technique to validate, elaborate, and/or change the premise behind an architecture effort by understanding and documenting the key elements of a business scenario in successive iterations. |
| TOGAF Series Guide:Information Mapping | This document addresses how to provide the architect with a means to articulate, characterize, and visually represent the information that is critical to the business. |
| TOGAF Series Guide:The TOGAF Integrated Information Infrastructure Reference Model (III-RM):An Architected Approach to Boundaryless Information Flow™ | This document addresses the TOGAF Integrated Information Infrastructure Reference Model (III-RM) in terms of its concepts, an overview, and its detailed taxonomy. |
| TOGAF Series Guide:The TOGAF Leader’s Guide to Establishing and Evolving an EA Capability | This document puts forward advice on establishing an Enterprise Architecture Capability that aligns to a set of requirements and expectations specific to each enterprise. |
| TOGAF Series Guide:The TOGAF Technical Reference Model (TRM) | This document describes the TOGAF Technical Reference Model (TRM), including the core taxonomy, graphical representation, and the detailed platform taxonomy. |
| TOGAF Series Guide:Using the TOGAF Framework to Define and Govern Service-Oriented Architectures | This document provides guidance on how the architect can use the TOGAF standard to develop, manage, and govern Service-Oriented Architectures (SOA). |
| TOGAF Series Guide:Value Streams | This document addresses how to identify, define, model, and map a value stream to other key components of an enterprise’s Business Architecture. |
2.5 An Introduction to the TOGAF ADM
The TOGAF Architecture Development Method (ADM) forms the core of the TOGAF standard and is a method for deriving organization-specific Enterprise Architecture. It is the result of contributions from many architecture practitioners.
The ADM provides a tested and repeatable process for developing architectures. The ADM includes establishing an architecture framework, developing architecture content, transitioning, and governing the realization of architectures. All of these activities are carried out within an iterative cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled manner in response to business goals and opportunities.
The ADM is described as a number of phases within a process of change illustrated by an ADM cycle graphic (see Figure 2).
Figure 2: The TOGAF ADM
The Preliminary Phase describes the preparation and initiation activities required to create an Architecture Capability, including the customization of the TOGAF framework, and the definition of Architecture Principles.
Phase A: Architecture Vision describes the initial phase of an Architecture Development Cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.
Phase B: Business Architecture describes the development of a Business Architecture to support an agreed Architecture Vision.
Phase C: Information Systems Architectures describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures.
Phase D: Technology Architecture describes the development of the Technology Architecture for an architecture project.
Phase E: Opportunities and Solutions describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture defined in the previous phases.
Phase F: Migration Planning describes the development of a detailed Implementation and Migration Plan that addresses how to move from the Baseline to the Target Architecture.
Phase G: Implementation Governance describes architectural oversight of the implementation.
Phase H: Architecture Change Management describes procedures for managing change to the new architecture.
Requirements Management describes the process of managing architecture requirements throughout the ADM.
2.6 Using the TOGAF Framework with Other Frameworks
Two of the key elements of any Enterprise Architecture framework are a definition of the deliverables that the architecting activity should produce, together with a description of the method for production.
Many Enterprise
