TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Statement of Architecture Work
No Chapter 4 definition — closest official wording
“The Statement of Architecture Work defines the scope and approach that will be used to complete an architecture development cycle.”
It is typically the document against which successful execution of the architecture project will be measured, and may form the basis for a contractual agreement between the supplier and consumer of architecture services.
Source: AC §4.2.20 — Chapter 4 has no entry
Memory aid
Request (sponsor asks) → Statement (architects agree how) → Vision (what it will look like).
Memory aid — not TOGAF wording.
In plain words
The signed “terms of engagement” for one ADM cycle: what will be done, how, by whom, by when, and how success will be judged.
Plain-English summary — not TOGAF wording.
Worked example
CDIPD's SoAW for the Digital Campus cycle: scope = student services; approach = Phases B–D at segment level; roles and deliverables; acceptance criteria; a 6-month plan; signed by the Registrar as sponsor.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Statement of Architecture Work
DEFINES
Scope and approach for one ADM cycle
MEASURES
Successful execution of the architecture project
CREATED IN
Phase A · step 3.3.11
IS EFFECTIVELY
An Architecture Contract with the sponsor
APPROVAL
Formal approval + sponsor sign-off to proceed
NOT TO CONFUSE WITH
Request for Architecture Work (the trigger)
Source: AC §4.2.20 · ADM §3.3.11 · CG §5.2.1
02Typical contents (AC §4.2.20)
| Section | Section |
|---|---|
| Title | Specific change of scope procedures |
| Architecture project request and background | Roles, responsibilities, and deliverables |
| Architecture project description and scope | Acceptance criteria and procedures |
| Overview of Architecture Vision | Architecture project plan and schedule |
| Approvals |
Source: AC §4.2.20
03Phase A · 3.3.11 Develop SoAW; Secure Approval
Assess work productsagainst business performance requirements
Decide domains, detail, viewsbased on purpose, focus, scope, constraints
Estimate resources; roadmap and scheduledocument in the SoAW
Define performance metrics; Communications Plan
Secure formal approvaland gain the sponsor's sign-off to proceed
Source: ADM §3.3.11
04Where it appears in the ADM
Phase A · Step 3.3.11
Develop Statement of Architecture Work; Secure Approval.
ADM §3.3.11
Requirements Management · Input
The Statement of Architecture Work is an input to Requirements Management.
ADM §13.2
05Exam traps
“The SoAW and the Request for Architecture Work are the same” → The Request triggers the cycle; the SoAW defines its scope and approach
“The SoAW is produced in the Preliminary Phase” → Phase A, step 3.3.11
“The SoAW is not a contract” → It is effectively an Architecture Contract between architecting organization and sponsor
“The Architecture Board alone signs it off” → Formal approval under governance procedures plus the sponsor's sign-off
06Self-test — tap to reveal
Q1What does the SoAW define?
The scope and approach for an architecture development cycle.
Q2In which step is it developed?
Phase A step 3.3.11.
Q3What is it effectively?
An Architecture Contract between the architecting organization and the sponsor.
Q4What is it measured against?
It is the document against which successful execution of the project is measured.
Q5Name three typical contents.
E.g. project description and scope; roles, responsibilities and deliverables; acceptance criteria; plan and schedule.
Q6Whose sign-off is needed to proceed?
The sponsor's.
Q7Which Phase A plan is developed in the same step?
The Communications Plan.
Q8What triggers the cycle before the SoAW exists?
A Request for Architecture Work.