Unlocking TOGAF: How Content Frameworks Shape Enterprise Architecture

Before TOGAF 9, the standard lacked detailed enterprise‑architecture content and relied on other frameworks like Zachman. With the introduction of the Content Framework, TOGAF became a complete, standalone architecture standard.

The Architecture Development Method (ADM) guides an organization from a baseline state to a target state, adapting dynamically to external changes. Each ADM phase consumes specific inputs and produces outputs, all defined and organized by the Content Framework.

The Content Framework classifies inputs and outputs for each ADM phase, using a Content Meta‑Model to define architecture elements (building blocks) and their relationships. It also maps these elements to stakeholder viewpoints, ensuring accurate, shared communication.

Enterprise Architecture Work Product Classification

Work products are grouped into three categories:

Architecture Deliverables : Contractual documents reviewed and signed by stakeholders, representing the final outputs of an architecture project.

Architectural Artifacts : Detailed, viewpoint‑specific outputs such as network diagrams, use‑case descriptions, or requirement matrices, presented as catalogs, matrices, or diagrams.

Building Blocks : Reusable components (Architecture Building Blocks – ABBs, and Solution Building Blocks – SBBs) that model business, application, data, or technology capabilities.

Architecture Deliverables

Deliverables are formal, contract‑based outputs linked to each ADM phase. They can be customized to fit an organization’s processes and include items such as architecture contracts, definition documents, principles, and roadmaps.

Building Blocks

ABBs capture architectural requirements and guide solution development, while SBBs describe concrete implementations, products, and components. Both types include functional descriptions, interfaces, dependencies, and mapping to business and organizational entities.

Architectural Artifacts

Artifacts provide stakeholder‑specific views of the architecture, using catalogs, matrices, and diagrams to illustrate business processes, data models, application interactions, and technology infrastructure.

Key Artifact Types

Principles catalog – lists business and architecture principles.

Stakeholder map matrix – identifies stakeholders, concerns, and impact.

Value‑chain diagram – shows high‑level business interactions.

Solution concept diagram – outlines high‑level solution direction.

Various catalogs (organization, role, business service, data entity, etc.) and matrices that map relationships between actors, roles, processes, systems, and data.

Building Block Usage Principles

Architectures should include only relevant building blocks, respect standards, and consider interoperability, reusability, and replaceability. Proper classification (reusable, to be developed, or to be purchased) and appropriate integration levels help create coherent, adaptable enterprise architectures.