18. Introduction

Chapter Contents
18.1 Guidelines for Adapting the ADM Process | 18.2 Techniques for Architecture Development | 18.3 Using TOGAF with Different Architectural Styles

This chapter provides an overview of the contents of Part III.

18.1 Guidelines for Adapting the ADM Process

The Architecture Development Method (ADM) process can be adapted to deal with a number of different usage scenarios, including different process styles (e.g., the use of iteration) and also specific specialist architectures (such as security). Guidelines included within this part of TOGAF are as follows:

18.2 Techniques for Architecture Development

The following techniques are described within Part III: ADM Guidelines and Techniques to support specific tasks within the ADM:

18.3 Using TOGAF with Different Architectural Styles

TOGAF is designed to be flexible and it can be used with various architectural styles. This part of TOGAF includes two chapters that are intended as useful examples.

Architectural styles differ in terms of focus, form, techniques, materials, subject, and time period. Some styles can be considered as fashionable, others focused on particular aspects of enterprise architecture. TOGAF is a generic framework and intended to be used in a wide variety of environments. It is a flexible and extensible framework that can be readily adapted to a number of architectural styles.

An organization's Architecture Landscape can be expected to contain architecture work that is developed in many architectural styles. TOGAF ensures that the needs of each stakeholder are appropriately addressed in the context of other stakeholders and the Baseline Architecture.

When using TOGAF to support a specific architectural style the practitioner must take into account the combination of distinctive features in which architecture is performed or expressed. As a first step, the distinctive features of a style must be identified.

For example, The Open Group definition for SOA identifies the following distinctive features:

The second step is determining how these distinctive features will be addressed. Addressing a distinctive style should not call for significant changes to TOGAF; instead it should adjust the models, viewpoints, and tools used by the practitioner.

In Phase B, Phase C, and Phase D the practitioner is expected to select the relevant architecture resources, including models, viewpoints, and tools, to properly describe the architecture domain and demonstrate that stakeholder concerns are addressed (see Part II, 8.4.1 Select Reference Models, Viewpoints, and Tools, 10.4.1 Select Reference Models, Viewpoints, and Tools, 11.4.1 Select Reference Models, Viewpoints, and Tools, and 12.4.1 Select Reference Models, Viewpoints, and Tools). Depending upon the distinctive features, different architectural styles will add new elements that must be described, highlight existing elements, adjust the notation used to describe the architecture, and focus the architect on some stakeholders or stakeholder concerns.

Addressing the distinctive features will usually include extensions to the Architecture Content Metamodel and the use of specific notation or modeling techniques and the identification of viewpoints. Whether the style is dominant will determine whether it is necessary to revisit the Preliminary Phase and make changes to the Architecture Capability or whether support for the distinctive feature is possible within the scope of selection expected within a single ADM cycle.

Style-specific reference models and maturity models are commonly used tools that support a practitioner.

Over time new architectural styles are expected to arise to address the key problems facing practitioners. Some styles will be transitory, some will endure in a niche, and some will merge into the mainstream. The Open Group Forums and Work Groups exist to address the challenges facing the industry. These bodies produce a wide range of material that is useful to a practitioner interested in adapting TOGAF, or a particular ADM cycle, to a particular architectural style for current materials, including White Papers and Standards that are applicable (see www.opengroup.org/togaf_docs).
return to top of page


The TOGAF document set is designed for use with frames. To navigate around the document:

return to top of page


Downloads of TOGAF®, an Open Group Standard, are available under license from the TOGAF information web site. The license is free to any organization wishing to use the TOGAF standard entirely for internal purposes (for example, to develop an information system architecture for use within that organization). A book is also available (in hardcopy and pdf) from The Open Group Bookstore as document G116.