TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Artifact
Official definition — learn word for word
“An architectural work product that describes an aspect of the architecture.”
Generally classified as catalogs (lists of things), matrices (showing relationships between things), and diagrams (pictures of things).
A deliverable may contain one or more artifacts, and artifacts form the content of the Architecture Repository.
Source: CC §4.23 · CC §3.6 · AC ch. 1
Memory aid
C-M-D: a LIST, a GRID, a PICTURE.
Catalog = a list
Matrix = a grid of relationships
Diagram = a picture
Memory aid — not TOGAF wording.
In plain words
One list, grid or diagram that shows one aspect of the architecture.
Plain-English summary — not TOGAF wording.
Worked example
DUK's Application Portfolio Catalog listing every student system; an Application/Data matrix showing which system creates or updates the student record.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Artifact
CATALOG
Lists of building blocks of a type — governance/ref.
MATRIX
Relationships between two or more model entities
DIAGRAM
Architectural content in a graphical format
CONTAINED IN
Deliverables
FORMS CONTENT OF
The Architecture Repository
NOT TO CONFUSE WITH
Deliverable (signed off)
Source: CC §3.6 · AC §3.6
02Recommended artifacts — frequently asked (AC §3.6.1–3.6.8)
| Phase | Catalogs | Matrices | Diagrams |
|---|---|---|---|
| Preliminary | Principles | — | — |
| A · Vision | Stakeholder | — | Value Chain · Solution Concept (“pencil sketch”) |
| B · Business | Organization/Actor · Role · … | Business Interaction · Actor/Role | Business Footprint · Process Flow · … |
| C · Data | Data Entity/Data Component | Data Entity/Business Function · Application/Data | Data Dissemination · … |
| C · Application | Application Portfolio · Interface | Application Interaction · Role/Application · … | Application Communication · … |
| D · Technology | Technology Standards · Technology Portfolio | Application/Technology | Environments and Locations · … |
| E · Opp. & Solutions | — | — | Project Context · Benefits |
| Requirements Mgmt | Requirements | — | — |
Phases F, G and H have no artifacts listed in §3.6.
Source: AC §3.6.1–3.6.8
03How they relate (AC Fig 1-1 and its Fig 1-2 example)
DeliverableArchitecture Definition Document — signed off by stakeholders
contains
ArtifactsProcess Flow Diagram — architecture views of the building blocks
describe
Building blocksTarget Call Handling Process + Customer Services Representative
A single artifact can describe several building blocks (the process and the actors in it).
Source: AC ch. 1 (Figs 1-1, 1-2) · CC §3.6
04Where it appears in the ADM
Preliminary
Principles Catalog.
AC §3.6.1
Phase A
Stakeholder Catalog; Value Chain and Solution Concept diagrams.
AC §3.6.2
Requirements Management
Requirements Catalog.
AC §3.6.8
05Exam traps
“An artifact is signed off by stakeholders” → That's a deliverable; a deliverable contains artifacts
“Stakeholder Catalog is Preliminary” → Phase A; Preliminary has the Principles Catalog
“Requirements Catalog is Phase A” → Requirements Management
“Application/Data Matrix belongs to Application Architecture” → It is listed under Phase C Data
“Application/Technology Matrix is Phase C” → Phase D
“Project Context / Benefits diagrams are Phase F” → Phase E; F, G, H list no artifacts
“A CRUD view is a diagram” → The Standard's example of a matrix (list-based, hard to draw)
06Self-test — tap to reveal
Q1Define an artifact.
A work product describing an aspect of the architecture.
Q2Three classes?
Catalogs, matrices, diagrams.
Q3Deliverable vs artifact?
A deliverable is contractually specified and signed off; it contains artifacts.
Q4What do artifacts form?
The content of the Architecture Repository.
Q5“Pencil sketch” of the solution?
Solution Concept Diagram, Phase A.
Q6Only Preliminary artifact?
Principles Catalog.
Q7Phase E artifacts?
Project Context and Benefits diagrams.
Q8Relationships list-based, not graphical?
Use a matrix.