Architecture Content Framework and Deliverables
Artifacts, deliverables and building blocks
TOGAF's content framework tells you what to produce. Artifacts are fine-grained work products in three kinds: catalogs (lists of things - e.g. an application portfolio catalog), matrices (relationships between things - e.g. a data-entity/application matrix) and diagrams (pictures - e.g. a business process flow). Deliverables are the formally reviewed and agreed packages: Architecture Definition Document, Architecture Requirements Specification, Architecture Roadmap, Statement of Architecture Work, Architecture Contract, Implementation and Migration Plan. Building Blocks are reusable components: Architecture Building Blocks (ABBs) define required capability and shape the architecture; Solution Building Blocks (SBBs) are the concrete, vendor-aware implementations.
The Architecture Repository holds the Architecture Metamodel, Architecture Capability, Architecture Landscape, Standards Information Base, Reference Library and Governance Log, plus the Architecture Requirements Repository.
Traps: an artifact is not a deliverable, and a catalog is not a matrix. Expect questions of the form 'which deliverable contains X' - the Architecture Definition Document holds baseline and target architectures and the gap analysis; the Architecture Requirements Specification holds requirements; the Architecture Roadmap holds work packages over time; the Statement of Architecture Work holds scope and approach for one ADM cycle; the Architecture Contract binds the architecture function and the sponsor for one project. Do not confuse the last two. On viewpoints: a catalog serves one viewpoint, a matrix two, a diagram two or more.
Rule of thumb: ask 'is this about a thing, a relationship, or a picture?' - catalog, matrix, diagram respectively.