TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Architecture Vision
Official definition — learn word for word
“A succinct description of the Target Architecture that describes its business value and the changes to the enterprise that will result from its successful deployment. It serves as an aspirational vision and a boundary for detailed architecture development.”
Its purpose is to provide key stakeholders with a formally agreed outcome (AC §4.2.8).
Source: CC §4.22 · AC §4.2.8
Memory aid
Vision = postcard of the Target, drawn in Phase A with informal techniques.
Memory aid — not TOGAF wording.
In plain words
The one-page “elevator pitch” of where the architecture is going and why it's worth it — agreed early so everyone aims at the same outcome.
Plain-English summary — not TOGAF wording.
Worked example
“By 2028 every DUK student uses one login and one portal for admission, fees and results; fee collection time halves.” Backed by a simple solution concept diagram.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Architecture Vision
CREATED IN
Phase A · step 3.3.8
GIVES
A formally agreed outcome
HIGH LEVEL
Baseline + Target; informal techniques
TECHNIQUE
Business scenarios; solution concept diagram
SUMMARY OF
The full Architecture Definition
NOT TO CONFUSE WITH
Statement of Architecture Work (scope, approach)
Source: AC §4.2.8 · ADM §3.3.8
02Vision vs Statement of Architecture Work vs ADD
| Deliverable | Purpose | When |
|---|---|---|
| Architecture Vision | Summary of the changes from deploying the Target; a formally agreed outcome | Phase A · 3.3.8 |
| Statement of Architecture Work | Scope and approach for the architecture development cycle; the measure of success | Phase A · 3.3.11 |
| Architecture Definition Document | Container for the core artifacts; all domains and states | Phases B–D · step 9 |
Source: AC §4.2.3, §4.2.8, §4.2.20 · ADM §3.3.8, §3.3.11
03Phase A · 3.3.8 Develop Architecture Vision
Decide the overall architecturehow domain deliverables fit together
High-level Baseline and Targetfrom concerns, capability requirements, scope, constraints, principles
Use informal techniquese.g. a simple solution concept diagram; business scenarios
Store initial versionsin the Architecture Repository
Source: ADM §3.3.8
04Where it appears in the ADM
Phase A · Step 3.3.8
Develop Architecture Vision.
ADM §3.3.8
Phases B, C, D · Step 3
Target descriptions are developed to the extent necessary to support the Architecture Vision.
ADM §4.3.3
05Exam traps
“The Architecture Vision is a detailed design” → High level, often using informal techniques
“The Vision is created in Phase B” → Phase A, step 3.3.8
“The Vision is the same as the Target Architecture” → It is a succinct description of the Target
“Business scenarios are only used in Phase A” → Also at more detailed levels, e.g. Phase B
06Self-test — tap to reveal
Q1Define the Architecture Vision.
A succinct description of the Target Architecture: its business value and the changes that will result.
Q2What two roles does it serve?
An aspirational vision and a boundary for detailed architecture development.
Q3Which step develops it?
Phase A step 3.3.8.
Q4What does it give key stakeholders?
A formally agreed outcome.
Q5Which diagram is common here?
A simple solution concept diagram.
Q6Which technique discovers business requirements for it?
Business scenarios.
Q7It is a summary version of what?
The full Architecture Definition.
Q8Where are initial versions stored?
In the Architecture Repository.