Building Blocks & ContentTGF-C4 · theory

Source · TOGAF Standard, 10th Edition — Architecture Content

Why this matters

Architecture Content — Intro

Every ADM phase produces something. The Architecture Content Framework is TOGAF's vocabulary for those work products, so that a 'deliverable', an 'artifact' and a 'building block' mean precise, different things — not loose synonyms.

Examiners love this topic because the terms are easy to blur. Nail the three definitions and the ABB-vs-SBB distinction and you've got it.

The concept: three kinds of work product

Content Framework §I

A deliverable is a contractually specified, formally reviewed and signed-off work product — an output an engagement is committed to produce (e.g. the Architecture Definition Document). Deliverables are typically archived or become part of the Repository.

An artifact is a finer-grained work product describing one aspect of the architecture. Artifacts come in three kinds: catalogs (lists of things), matrices (relationships between things), and diagrams (pictures).

A building block is a (potentially reusable) component of capability. The relationship: deliverables contain artifacts, and artifacts describe building blocks.

ABBs vs SBBs — needed vs used

Content Framework — Building Blocks

Building blocks come in two kinds:

Architecture Building Blocks (ABBs) describe required capability and are largely technology-neutral — they shape the solution. They are elaborated chiefly in the architecture phases (B–D), though refined across the ADM. Solution Building Blocks (SBBs) represent the actual implementation — products, bought or built — and are firmed up as you move into Opportunities & Solutions and Migration (E–F).

Mnemonic: ABB = what's needed; SBB = what's used.

Worked example

In the loan programme, an ABB might be 'an asynchronous event backbone with at-least-once delivery' — a required capability, no vendor named. The matching SBB is 'Apache Kafka, 3 brokers, configured for idempotent producers'. The Architecture Definition Document (a deliverable) would contain a component catalog and an interaction matrix (artifacts) that describe both building blocks.

How it connects

These work products are the outputs of the ADM phases (TGF‑C2), and they're classified and stored via the Enterprise Continuum & Repository (TGF‑C3) — an ABB may sit at the Common Systems level, an SBB at the organisation-specific level. Deliverables are what governance reviews and signs off.

Common traps
  • Deliverable vs artifact: a deliverable is contractual & signed-off; an artifact is a finer-grained catalog/matrix/diagram inside it.
  • ABB ≠ SBB. ABB = required capability (what's needed, tech-neutral); SBB = the implementation (what's used).
  • The three artifact types are catalog (list), matrix (relationships), diagram (picture) — don't swap them.
  • Building blocks are refined across the ADM — don't state they're created only in one fixed phase.
Key takeaways
  • Deliverable (contractual, signed-off) ⊃ artifact (catalog/matrix/diagram) → describes building block.
  • ABB = what's needed (tech-neutral); SBB = what's used (implementation).
  • The Architecture Definition Document is the canonical example of a deliverable.