8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

Architecture that cannot be communicated is worthless, and architecture communicated the same way to everybody communicates to nobody. A CFO worried about licence spend and a security architect worried about lateral movement need different pictures of the same system. TOGAF gives that intuition a precise vocabulary — four terms that examiners test relentlessly because candidates habitually swap two of them.

---

The Four Terms, Defined Precisely

The chain that connects them, and the sentence to memorize:

   STAKEHOLDERS  ---- have ---->  CONCERNS
                                     |
                                addressed by
                                     v
   VIEWPOINTS  ---- govern ---->   VIEWS  ---- shown to ---->  STAKEHOLDERS

Stakeholders have concerns; concerns are addressed by views; views are governed by viewpoints.

---

Viewpoint vs View: The Distinction Candidates Get Wrong

Both terms describe seeing, which is why they blur. The reliable disambiguation is optical:

• The viewpoint is where you stand and what you look through — the lens, the rules, the conventions. It exists before and independently of any particular enterprise. It can be reused across a hundred organizations.
• The view is what you see from there — the concrete result of applying that lens to this architecture. It is specific to one enterprise at one point in time.

A worked pair makes it concrete. A Security Viewpoint specifies that a security view must show trust zones as bounded regions, data flows crossing zone boundaries as annotated arrows, authentication points as labelled gates, and must identify the data classification of every crossing flow. That is a reusable specification: it says nothing about any specific company. The Security View of the Acme payments platform is the diagram produced by applying that specification to Acme — showing Acme's actual DMZ, its actual token service, and the three flows that cross into the cardholder data environment. Change companies and the viewpoint stays; the view is redrawn from scratch.

Two more pairings worth having ready:

Both concepts come to TOGAF from ISO/IEC/IEEE 42010, the international standard for architecture description, which is where the formal definitions originate. That lineage is worth knowing: it explains why the vocabulary is shared with other architecture disciplines and why TOGAF does not invent its own competing definitions.

---

Where Views and Viewpoints Fit in the ADM

Viewpoint selection is not an afterthought at documentation time. It is a deliberate step, and it happens twice:

1. Phase A (Architecture Vision). Architects identify stakeholders, elicit and document their concerns, and build the Stakeholder Map. From those concerns they determine which viewpoints will be required. Doing this early is what prevents the classic late-stage failure: a target architecture that is complete and correct but has no artifact that answers the CFO's question, discovered a week before the funding decision.
2. Phases B, C, and D. The first step of each domain phase is to select reference models, viewpoints, and tools. The architect then produces the corresponding views, which materialize as the catalogs, matrices, and diagrams described in Section 8.4.

That last connection is the one to hold on to for the exam: a view is realized as artifacts. Catalogs, matrices, and diagrams are the physical forms views take; the view is the conceptual answer to a set of concerns, and the artifacts are how it reaches a stakeholder's screen.

---

Coverage: The Real Test of a Viewpoint Set

The point of the discipline is coverage. For every documented concern, some view must address it, and every view must be governed by a stated viewpoint. A simple coverage matrix catches the gaps early:

An empty cell in the third column is a stakeholder whose concern you have recorded and then quietly ignored — which is usually where architecture engagements go wrong. An empty cell in the second column is worse: a view drawn with no stated conventions, which nobody else can reproduce or maintain.

---

Exam Focus

The Architecture Content syllabus area is worth 5 of the 40 questions on OGEA-101, and the stakeholder/concern/view/viewpoint relationship is one of its named learning outcomes. Expect at least one question that hinges purely on telling a viewpoint from a view. Anchor on the definitions: a viewpoint specifies the conventions for constructing and using a view; a view is the representation produced from those conventions.