TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Architecture Definition Document
No Chapter 4 definition — closest official wording
“The Architecture Definition Document is the deliverable container for the core architectural artifacts created during a project and for important related information.”
It spans all architecture domains (Business, Data, Application, and Technology) and examines all relevant states of the architecture (Baseline, Transition, and Target).
Source: AC §4.2.3 — Chapter 4 has no entry
Memory aid
ADD = the What and Why (qualitative). ARS = the measurable Must-meet (quantitative).
Memory aid — not TOGAF wording.
In plain words
The main architecture “book” for a project: all the key catalogs, matrices and diagrams for every domain and every state, in one signed-off deliverable.
Plain-English summary — not TOGAF wording.
Worked example
DUK's ADD holds the baseline and target student-services architecture, the gap analysis, and the two transition states — built in Phase B, updated in C and D, finalized by the end of Phase F.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Architecture Definition Document
SPANS
All four domains
COVERS STATES
Baseline · Transition · Target
CONTAINS
Core artifacts; gap and impact assessment
BUILT IN
Phases B–D step 9; updated in Phase F
COMPANION
Architecture Requirements Specification
NOT TO CONFUSE WITH
An artifact (it is a deliverable)
Source: AC §4.2.3 · CC §3.6 · ADM §10.3.5
02ADD vs Architecture Requirements Specification
| Aspect | ADD | ARS |
|---|---|---|
| View | Qualitative — communicates the intent of the architects | Quantitative — measurable criteria for implementation |
| Typical content | Scope; goals; principles; Baseline; models per state; rationale; mapping to repository; gap analysis; impact assessment; Transition Architecture | Success measures; requirements; service contracts; implementation guidelines, specs, standards; interoperability; constraints; assumptions |
Source: AC §4.2.3, §4.2.6
03The ADD through the ADM
Phase B · 4.3.9Create/Update the ADD
Phase C · 6.3.9 / 7.3.9Create/Update the ADD
Phase D · 8.3.9Create/Update the ADD
Phase F · 10.3.5Update the ADD if the implementation approach shifted
End of Phase Ffinalized ADD available
Source: ADM §4.3.9, §6.3.9, §7.3.9, §8.3.9, §10.3.5 · CG §5.1
04Where it appears in the ADM
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 F · Step 10.3.5
Confirm Architecture Roadmap and Update Architecture Definition Document.
ADM §10.3.5
End of Phase F
The finalized ADD is available.
CG §5.1
05Exam traps
“The ADD only describes the target” → It examines Baseline, Transition, and Target
“The ADD only covers technology” → It spans all four domains
“The ADD is quantitative” → Qualitative; the ARS is quantitative
“The ADD is an artifact” → It is a deliverable that contains artifacts
06Self-test — tap to reveal
Q1What is the ADD?
The deliverable container for the core architectural artifacts created during a project.
Q2Which domains does it span?
All four.
Q3Which states does it examine?
Baseline, Transition, Target.
Q4Qualitative or quantitative?
Qualitative.
Q5What is its companion deliverable?
The Architecture Requirements Specification.
Q6Which step in Phases B–D creates/updates it?
Step 9.
Q7Which Phase F step updates it?
10.3.5.
Q8In CC §3.6's example, what artifact describes the target call handling process?
A process flow diagram.