Contents of TOGAF Framework

The TOGAF Standard helps us define the structure and content of an architecture capability in an enterprise. The different components of the standard define the different aspects of an enterprise architecture. The TOGAF standard is defined in five important parts. These five parts and the interaction between them defines a good enterprise architecture.

These parts are not independent static entities. There is a dynamic collaboration among them, that leads to a dynamic enterprise. The input to the enterprise comes in from a business vision and business drivers. It could be a visionary innovation that drives the enterprise forward, or it could be other business forces that compel it in a given direction. An enterprise architecture translates a business vision into a business capability.

Architecture Development Method (ADM)

The ADM is the major component of the TOGAF framework. It provides guidance for architects on different levels

It defines the architecture development phases in a cycle - as an overall process template for the architecture development activity. Along with this, it provides a detailed narrative of each phase. This describes each phase in detail, in terms of its objectives, inputs, outputs and the steps to be followed to achieve it. It also provides cross phase interactions and also the central requirements management.

ADM Guidelines & Techniques

This part provides important guidelines and techniques to support real world application of the ADM. This includes adapting the ADM for different scenarios and process styles; iteration and application of ADM across the landscape.

It contains a high level description about using the ADM across different architecture styles - using SOA for example. The Guidelines also support specific important tasks within the ADM such as, capability based planning, defining principles, gap analysis, migration planning, risk management, stakeholder management, etc.

The TOGAF Library (apart from the TOGAF Standard), provides many more guidelines and techniques.

The ADM is not just a textbook solution. It has to be adapted and adopted for the enterprise, based on the business needs; based on the problems at hand. As we work on the ADM, we refine our understanding of the business, this feeds in further improvement and refinement of our business vision. As we work iteratively through the ADM, we can develop an enterprise that can provide the required business capability.

Architecture Content Framework

This provides a detailed model of different architecture work products generated through the ADM life cycle. This includes deliverables, artifacts within the deliverables, and building blocks.

Enterprise Continuum

The Enterprise Continuum provides a model or structure for a virtual repository of artefacts. It provides methods for classifying architecture and solution artifacts. It shows how the different types of artifacts evolve and how they can be leveraged and re-used.

It is based on architectures and solutions (models, patterns, architecture descriptions, etc.) that exist within the enterprise. It also includes the relevant architectures and solutions from the industry at large. These are the ones that the enterprise has collected for use in the development of its architectures.

The business capabilities in place provide an important input to the contents of the enterprise continuum - which in turn, provide a baseline for the business vision.

Architecture Capability Framework

This is a set of resources, guidelines, templates, background information, etc. provided to help the architect establish an architecture practice within an organization. It provides a framework of the enterprise organization to develop and work - in order to build an architecture capability.

The business vision and drivers feed into the Architecture Capability Framework, to provide the size, structure and culture of the capability being developed. This in turn defines the targets, KPI's, and budgets for the specific architecture roles.

On the other hand, the business capability demands and drives the need for an architecture capability model. Based on this, the capability framework ensures the operation of the architecture capability - thus ensuring the fulfillment of the business vision.

The architecture capability that is based on the various business drivers, has an important influence on the way ADM is adapted for the enterprise.