Understanding the Architecture Content Framework in TOGAF: A Comprehensive Overview

Table of Contents hide

1 Deliverables

2 Artifacts

3 Building Blocks

4 The Relationship Among Deliverables, Artifacts and Building Blocks

5 Example – Architecture Definition Document

6 The Content MetaModel

7 The Relationship Between the TOGAF ADM and the Content Framework

8 Summary

The Open Group Architecture Framework (TOGAF) is a popular framework for enterprise architecture. It provides a structured approach for designing, planning, implementing, and managing enterprise architecture. One of the key components of TOGAF is the Architecture Content Framework, which describes the types of architectural work products that should be produced during the development of an enterprise architecture. In this article, we will explore the key concepts of the Architecture Content Framework, including building blocks, artifacts, and deliverables, and how they relate to the TOGAF Architecture Development Method (ADM).

As mentioned before, the Architecture Content Framework is a component of the TOGAF standard that provides a structure for organizing and classifying the various types of architectural work products used within an enterprise architecture. The framework divides architectural work products into three categories:

Deliverables

In TOGAF, a deliverable is a specific type of work product that is formally reviewed, agreed upon, and signed off by stakeholders. Deliverables are typically contractually specified, meaning that they are defined and agreed upon in a contract or agreement between the enterprise and its stakeholders.

Deliverables are an important output of projects within the enterprise architecture framework. They represent the tangible results of the project, such as documents, reports, or other artifacts that provide insight into the architecture landscape at a specific point in time. These deliverables can be used to communicate the project’s progress, ensure that stakeholders are aligned, and support decision-making throughout the project’s lifecycle.

Once a project is completed, any deliverables that are in documentation form will typically be archived or stored in an Architecture Repository. The Architecture Repository serves as a reference model, standard, or snapshot of the architecture landscape at a specific point in time. This can be useful for future projects or initiatives, as it provides a historical record of the organization’s architecture and the decisions that were made along the way.

Examples of deliverables within the TOGAF framework might include:

an Architecture Vision document,
a Business Architecture document, or
a Data Architecture document.

Each of these deliverables represents a specific aspect of the enterprise architecture and provides valuable insight into the organization’s current state and its goals for the future.

Artifacts

In TOGAF, artifacts are defined as architectural work products that describe a specific aspect of the architecture. These can take the form of lists, matrices, diagrams, or other types of documentation that provide insight into different aspects of the architecture landscape.

Artifacts can be classified into three types: catalogs, matrices, and diagrams.

Catalogs are lists of related items, such as a list of business capabilities or a list of technology components.
Matrices show relationships between different elements, such as a matrix that shows how business capabilities relate to business processes.
Diagrams are visual representations of architecture elements, such as a diagram of a system or a process flow diagram.

Artifacts are often contained within deliverables, which are formally reviewed, agreed upon, and signed off by stakeholders. For example, a Business Architecture document may contain a catalog of business capabilities, a matrix showing the relationships between those capabilities and the business processes that support them, and a diagram of the high-level business architecture.

In addition to being contained within deliverables, artifacts can also be stored in an Architecture Repository for future reference. The Architecture Repository serves as a central location for storing and managing all of the artifacts and other resources that are used in the enterprise architecture framework. This can include everything from architecture principles and standards to reference models and templates.

Overall, artifacts are an important part of the TOGAF framework, as they provide a tangible way to document and communicate different aspects of the architecture landscape. By creating and maintaining high-quality artifacts, organizations can improve their ability to manage and optimize their enterprise architecture over time.

Building Blocks

Building Blocks are components of enterprise capability that can be combined with other building blocks to deliver architectures and solutions. They can be defined at different levels of detail, depending on the stage of architecture development. For example, in the early stages of development, a building block may be a high-level description or outline of a concept, while in later stages, it may be more fully specified with accompanying artifacts.

Architecture Building Blocks (ABBs) are building blocks that describe the required capability of an enterprise architecture. They are used to shape the specification of Solution Building Blocks (SBBs) that will be used to implement that capability. ABBs are typically higher-level building blocks that are more abstract in nature and provide an overall structure for the architecture.

Solution Building Blocks (SBBs), on the other hand, are the components that will be used to implement the required capability. SBBs are lower-level building blocks that are more specific and concrete in nature. They can be used to realize the architectures and solutions of the enterprise, and are typically supported by complementary artifacts such as diagrams, models, or specifications.

To give an example, suppose an enterprise wants to develop a customer services capability. The Architecture Building Block might be a high-level description of the customer services capability, while the Solution Building Blocks could include specific components such as customer data management software, a customer service process, and a customer-facing application. These SBBs could be further decomposed into even more detailed building blocks, such as specific software modules or individual steps in the customer service process.

By using these three categories to describe the different types of architectural work products, the Architecture Content Framework provides a comprehensive approach to organizing and managing enterprise architecture work products.

The Relationship Among Deliverables, Artifacts and Building Blocks

The relationship between deliverables, artifacts, and building blocks is an important aspect of the TOGAF framework.

Deliverables are formal work products that are contractually specified and reviewed, agreed upon, and signed off by stakeholders. These deliverables represent the output of projects and typically take the form of documentation that is archived or transitioned into an Architecture Repository for future reference. Deliverables can contain many artifacts, which are architectural work products that describe a specific aspect of the architecture.

Artifacts, in turn, can be classified as catalogs, matrices, or diagrams, and can represent a range of different architecture elements, such as business capabilities, data models, or technology components. Artifacts can also be used to describe the relationships between different architecture elements, such as how business capabilities relate to business processes.

Building blocks, on the other hand, represent reusable components of enterprise capability that can be combined with other building blocks to deliver architectures and solutions. Architecture Building Blocks (ABBs) describe required capabilities and shape the specification of Solution Building Blocks (SBBs), which represent the components that will be used to implement the required capability. For example, a customer services capability may be required within an enterprise, supported by many SBBs, such as processes, data, and application software.

So, the relationship between deliverables, artifacts, and building blocks is that deliverables can contain many artifacts, which can be used to describe different aspects of the architecture landscape. Building blocks, such as ABBs and SBBs, are used to implement the required capabilities described by the artifacts and deliverables. By using building blocks, organizations can create reusable components that can be combined to deliver architectures and solutions more efficiently and effectively.

Example – Architecture Definition Document

The example provided refers to the relationship between deliverables, artifacts, and building blocks in the context of creating an Architecture Definition Document.

The Architecture Definition Document is a formal deliverable that documents an Architecture Description, which provides a comprehensive view of the enterprise architecture. This document will typically contain a number of complementary artifacts, which are specific work products that describe a particular aspect of the architecture.

In the given example, a process flow diagram is created to describe the target call handling process, which is a building block that represents a specific capability required by the architecture. The process flow diagram is an artifact that describes the interactions, inputs, and outputs of the call handling process. This artifact can also describe other building blocks, such as the actors involved in the process, like the Customer Services Representative.

This example illustrates how deliverables, artifacts, and building blocks are interrelated within the TOGAF framework. The Architecture Definition Document is the formal deliverable that contains a collection of complementary artifacts that describe the building blocks relevant to the architecture. These artifacts, in turn, describe the specific capabilities, processes, data models, and technology components that make up the enterprise architecture.

The Content MetaModel

The Content Metamodel is a conceptual framework used in TOGAF to define and organize the types of building blocks that may exist within an architecture, and how they can be described and related to one another. In other words, the Content Metamodel is a conceptual model that describes the architecture content in terms of its components and their relationships. It provides a high-level view of the architecture content, including the types of artifacts and building blocks that are used, as well as the relationships between them. The Content Metamodel is used to organize and classify the architecture content and to ensure that it is consistent and aligned with the overall architecture vision and objectives.

The Relationship Between the TOGAF ADM and the Content Framework

The TOGAF ADM (Architecture Development Method) is a process for developing an enterprise architecture that takes the enterprise from a current baseline state to a future target state. The ADM consists of several phases, including visioning, architecture definition, transformation planning, and Architecture Governance, each with its own set of inputs and outputs.

The content framework provides a structure for the deliverables that are produced during each phase of the ADM. It defines the types of deliverables that should be produced, such as catalogs, matrices, and diagrams, and how they fit into the overall architecture view of the enterprise. The content framework also defines the relationships between different building blocks and how they can be described and related to one another.

By using the content framework as a companion to the ADM, architects can ensure that they are producing the right types of deliverables at each stage of the process and that they are aligned with the overall architecture view of the enterprise. The ADM provides the process for creating an architecture, while the content framework provides the structure for the deliverables that make up the architecture. Together, they form a comprehensive approach for developing an enterprise architecture.

Summary

The Architecture Content Framework is a key component of the TOGAF framework for enterprise architecture. It provides a structured approach for describing the types of architectural work products that should be produced during the development of an enterprise architecture. The framework is based on three categories: deliverables, artifacts, and building blocks. Deliverables are work products that are formally reviewed and agreed upon by stakeholders, while artifacts are architectural work products that describe a specific aspect of the architecture. Building blocks are reusable components of enterprise capability that can be combined to deliver architectures and solutions.

The Architecture Content Framework is closely related to the TOGAF Architecture Development Method (ADM), which describes the process of moving from a baseline state of the enterprise to a target state of the enterprise. The ADM requires inputs at each stage of the process and produces outputs as a result of executing a number of steps. The Architecture Content Framework provides an underlying structure for the ADM that defines inputs and outputs in more detail and puts each deliverable into the context of the holistic architecture view of the enterprise.