TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Request for Architecture Work
No Chapter 4 definition — closest official wording
“This is a document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle.”
All the information in this document should be at a high level.
Source: AC §4.2.17 — Chapter 4 has no entry
Memory aid
Request → Phase A. The sponsor asks; the architects respond with a Statement of Architecture Work.
Memory aid — not TOGAF wording.
In plain words
The sponsor's formal “please start” note: why the work is needed, the goals, the limits and the budget — kept high level.
Plain-English summary — not TOGAF wording.
Worked example
The DUK Registrar sends CDIPD a Request for Architecture Work: goal = single digital campus; time limit = before the 2027 admissions cycle; budget cap; current systems described briefly.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Request for Architecture Work
FROM → TO
Sponsoring org → architecture org
PURPOSE
Trigger the start of a development cycle
CREATED FROM
Preliminary · approved Change Requests · F
PHASE H · 12.3.7
Produce a new Request (for major changes)
DETAIL
High level; reference plans, don't copy
NOT TO CONFUSE WITH
Statement of Architecture Work
Source: AC §4.2, §4.2.17 · ADM §12.3.7, §12.4
02Typical contents (AC §4.2.17)
| Section | Section |
|---|---|
| Organization sponsors | Budget information, financial constraints |
| Organization's mission statement | External constraints, business constraints |
| Business goals (and changes) | Current business system description |
| Strategic plans of the business | Current architecture/IT system description |
| Time limits | Description of developing organization |
| Changes in the business environment; organizational constraints | Description of resources available to developing organization |
Source: AC §4.2.17
03Where a Request comes from
Preliminary Phase outputor
Approved architecture Change Requestse.g. Phase H step 12.3.7
or
Terms of reference from migration planning
Triggers the start of an architecture development cyclePhase A
Source: AC §4.2.17 · ADM §12.3.7
04Where it appears in the ADM
Preliminary · Output
A Request for Architecture Work can be created as an output of the Preliminary Phase.
AC §4.2.17
Phase H · Step 12.3.7
Activate the Process to Implement Change — produce a new Request for Architecture Work and request for investment.
ADM §12.3.7
Phase H · Outputs
New Request for Architecture Work, to move to another cycle (for major changes).
ADM §12.4
05Exam traps
“The architects write the Request” → It is sent from the sponsoring organization to the architecture organization
“The Request should be detailed” → All information should be at a high level
“Copy the strategic plans into it” → Reference the title of the strategic plans rather than copying them
“Requests only come from the Preliminary Phase” → Also from approved Change Requests, or migration planning
06Self-test — tap to reveal
Q1What is a Request for Architecture Work?
A document sent from the sponsoring organization to the architecture organization to trigger an architecture development cycle.
Q2Who sends it?
The sponsoring organization.
Q3At what level of detail?
High level.
Q4Name three sources.
Preliminary Phase output; approved Change Requests; migration planning terms of reference.
Q5Which Phase H step produces a new one?
12.3.7.
Q6Should strategic plans be copied in?
No — reference their title.
Q7Name three typical contents.
E.g. sponsors, business goals, time limits, budget information, constraints.
Q8What responds to it in Phase A?
The Statement of Architecture Work.