TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
View (Architecture View)
Official definition — learn word for word
“A representation of a system from the perspective of a related set of concerns.”
§4.85 “View” refers to §4.20 “Architecture View”. An architecture view consists of one or more architecture models of the system (AC §3.1).
Source: CC §4.20 · CC §4.85 · AC §3.1
Memory aid
A view is what you SEE; a viewpoint is where you are LOOKING FROM (AC §3.1 wording).
Memory aid — not TOGAF wording.
In plain words
One picture or model of the architecture, drawn for one audience's concerns.
Plain-English summary — not TOGAF wording.
Worked example
A “payment security” view for the Finance Officer shows only the payment flow and where card data travels — not the whole campus architecture.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Architecture View
CONSISTS OF
One or more architecture models
GOVERNED BY
An architecture viewpoint
ADDRESSES
A related set of stakeholder concerns
SPECIFIC
Always specific to the architecture it is for
PART OF
An Architecture Description
NOT TO CONFUSE WITH
Viewpoint (generic, re-usable schema)
Source: AC §3.1
02View vs Viewpoint — most-tested pair
| Aspect | Architecture View | Architecture Viewpoint |
|---|---|---|
| Definition | A representation of a system from the perspective of a related set of concerns | A specification of the conventions for a particular kind of architecture view |
| Plain words | What you see | Where you are looking from |
| Generic or specific? | Always specific to the architecture it is created for | Generic; can be stored in libraries for re-use |
| Made of | One or more models | References one or more model kinds |
| Stored in | The Architecture Description | Viewpoint Library in the Reference Library |
Source: CC §4.20, §4.21, §4.87 · AC §3.1
03From stakeholder to view (AC Fig 3-1)
Stakeholderhas interests in the system
has
Concernone or more per stakeholder
framed by
Architecture Viewpointconventions for a kind of view
governs
Architecture Viewaddresses the concerns
Every architecture view has an associated architecture viewpoint that describes it, at least implicitly.
Source: AC §3.1
04Where it appears in the ADM
Phase A · Step 3.3.2
Consider which architecture views and viewpoints need to be developed to satisfy stakeholder requirements.
ADM §3.3.2
Phases B, C, D · Step 1
Select Reference Models, Viewpoints, and Tools.
ADM §4.3.1, §6.3.1, §7.3.1, §8.3.1
05Exam traps
“A view is generic and re-usable” → The viewpoint is generic; a view is specific to its architecture
“A view can exist without a viewpoint” → Every view has an associated viewpoint, at least implicitly
“A view contains exactly one model” → One or more architecture models
“Views are stored in the Viewpoint Library” → Viewpoint specifications are stored there (Reference Library)
“The view frames concerns” → The viewpoint frames concerns; the view addresses them
06Self-test — tap to reveal
Q1Define an architecture view.
A representation of a system from the perspective of a related set of concerns.
Q2What does a view consist of?
One or more architecture models.
Q3View or viewpoint — which is “what you see”?
The view.
Q4Is a view generic or specific?
Specific to the architecture for which it is created.
Q5Does every view have a viewpoint?
Yes, at least implicitly.
Q6Which step in Phases B–D selects viewpoints?
Step 1 — Select Reference Models, Viewpoints, and Tools.
Q7What collection of views and models documents an architecture?
The Architecture Description.
Q8Why create views?
So the architecture can be communicated to and understood by stakeholders, who can verify their concerns are addressed.