TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Deliverable
Official definition — learn word for word
“An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders.”
Deliverables represent the output of projects; those in documentation form are typically archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time.
Source: CC §4.40 · CC §3.6
Memory aid
Deliverable = the signed parcel. Artifacts = what's inside. Building blocks = what the contents describe.
Memory aid — not TOGAF wording.
In plain words
A formal, contracted work product that stakeholders review and sign off.
Plain-English summary — not TOGAF wording.
Worked example
The Architecture Definition Document for DUK student services, reviewed and signed off by the Registrar and the CIO.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Deliverable
IS
Contractually specified; formally signed off
CONTAINS
One or more artifacts
AT PROJECT END
Archived, or moved into the Architecture Repository
EXAMPLE
Architecture Definition Document (ADD)
MAY BE SHAPED BY
PRINCE2 · PMBOK · MSP · CMMI (project mgmt)
NOT TO CONFUSE WITH
Artifact (not signed off on its own)
Source: CC §3.6, §4.40 · AC §4.1
02Deliverable vs Artifact vs Building Block
| Type | Chapter 4 definition | Key words |
|---|---|---|
| Deliverable (§4.40) | An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders | Contract · sign-off · project output |
| Artifact (§4.23) | An architectural work product that describes an aspect of the architecture | Catalog · matrix · diagram |
| Building Block (§4.26) | A potentially re-usable component that can be combined with other building blocks to deliver architectures and solutions | ABB · SBB · re-use |
“An artifact may or may not be considered a deliverable based on the contractual specification” (CC §3.6).
Source: CC §3.6, §4.23, §4.26, §4.40
03Example: Architecture Definition Document (CC Fig 3-3)
DeliverableArchitecture Definition Document
contains
ArtifactProcess Flow Diagram
describes
Building blocksTarget Call Handling Process + Customer Services Representative
Source: CC §3.6 (Figs 3-2, 3-3)
04Where it appears in the ADM
Phase A · Step 3.3.11
Develop Statement of Architecture Work; Secure Approval.
ADM §3.3.11
Phases B, C, D · Step 9
Create/Update the Architecture Definition Document.
ADM §4.3.9, §6.3.9, §7.3.9, §8.3.9
Phase G · Outputs
Architecture Contract (signed), Compliance Assessments, Change Requests.
ADM §11.4
05Exam traps
“An artifact is signed off by stakeholders” → The deliverable is; it contains artifacts
“Deliverable descriptions must be followed to the letter” → Not suggested — but each element should be considered carefully
“Deliverables are deleted at project end” → Archived, or transitioned into the Architecture Repository
“Every artifact is also a deliverable” → An artifact may or may not be a deliverable, based on the contractual specification
06Self-test — tap to reveal
Q1Define a deliverable.
An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders.
Q2What do deliverables represent?
The output of projects.
Q3What happens to documentation deliverables at project end?
Archived, or transitioned into the Architecture Repository.
Q4What does a deliverable contain?
One or more artifacts.
Q5Can an artifact also be a deliverable?
It may or may not, depending on the contractual specification.
Q6Which deliverable documents an Architecture Description?
The Architecture Definition Document.
Q7Which Phase A step produces the Statement of Architecture Work?
Step 3.3.11.
Q8What may constrain or alter deliverables (AC §4.1)?
Overarching project or process management, e.g. PRINCE2, PMBOK, MSP, CMMI.