Study guide

8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

TOGAF Enterprise Architecture Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction to TOGAF & Enterprise Architecture Concepts

1.1 Overview of TOGAF Standard 10th Edition & Enterprise Architecture Concepts 1.2 The Structure of the TOGAF Standard (Easily Navigated Body of Knowledge) 1.3 Core Concepts: Enterprise, Architecture, Deliverables, Artifacts, and Building Blocks 1.4 TOGAF Certification Paths & the OGEA-101 Exam Plan

2 Chapter 2: ADM Foundation & Preliminary Phase

2.1 The Architecture Development Method (ADM) Cycle & Requirements Management 2.2 Preliminary Phase: Scope, Principles, and Architecture Capability Setup 2.3 Tailoring the ADM & Applying Iteration / Architecture Levels 2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

3 Chapter 3: ADM Architecture Vision & Business Architecture

3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition 3.2 Business Architecture Scope, Strategy & Capability Mapping 3.3 Phase B: Business Architecture Inputs, Steps, Outputs & Artifacts 3.4 Business Scenarios & Value Stream Modeling

4 Chapter 4: ADM Information Systems Architectures (Phase C)

4.1 Information Systems Architectures Overview & Phase C Strategy 4.2 Phase C Data Architecture: Principles, Data Models & Governance 4.3 Phase C Application Architecture: Logical Components, Services & Interfaces 4.4 Data and Application Integration, Migration & Interoperability

5 Chapter 5: ADM Technology Architecture & Solution Realization (Phases D, E, F)

5.1 Phase D: Technology Architecture, Platform Services & Infrastructure 5.2 Phase E: Opportunities and Solutions & Initial Implementation Strategy 5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization 5.4 Transition Architectures & Implementation Dependencies

6 Chapter 6: ADM Governance, Change & Requirements Management (Phases G, H)

6.1 Phase G: Implementation Governance & Architecture Compliance 6.2 Phase H: Architecture Change Management & Driver Monitoring 6.3 Requirements Management: Central Flow, Impact Analysis & Traceability 6.4 Architecture Contracts, Dispensations & Compliance Reviews

7 Chapter 7: BDAT Architecture Domains Deep-Dive

7.1 Business Architecture Domain: Functions, Processes & Value Streams 7.2 Data Architecture Domain: Data Entities, Storage & Data Management 7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns 7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

8 Chapter 8: Architecture Content — Content Framework, Enterprise Metamodel & Artifacts

8.1 Architecture Content Framework Overview & Deliverables vs Artifacts vs Building Blocks 8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs) 8.3 The Enterprise Metamodel: Core Concepts, Entities & Attributes 8.4 Architecture Catalogs, Matrices & Diagrams (Visual Representation) 8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

9 Chapter 9: Architecture Governance, Capability & Maturity

9.1 Architecture Governance Framework & The Role of the Architecture Board 9.2 Establishing an Architecture Capability & Organizational Structure 9.3 Architecture Skills Framework, Roles & Competency Levels 9.4 Architecture Maturity Models & Capability Assessments

10 Chapter 10: Enterprise Continuum, Reference Models & Key Techniques

10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning 10.2 Technical Reference Model (TRM) & Integrated Information Infrastructure Reference Model (III-RM) 10.3 Core EA Techniques: Gap Analysis, Interoperability, Risk, Capability-Based Planning & Architecture Patterns

8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

Key Takeaways Explain This Topic AI

A viewpoint defines the conventions for constructing and using a view; a view is what you actually get when you apply a viewpoint to a specific architecture.

TOGAF frames the relationship as: stakeholders have concerns, concerns are addressed by views, and views are governed by viewpoints.

The memory hook is optical: the viewpoint is where you stand and what you look through; the view is what you see from there.

TOGAF draws its view and viewpoint concepts from ISO/IEC/IEEE 42010, the international standard for architecture description.

Selecting viewpoints is a deliberate Phase A and Phase B–D step: architects choose viewpoints to cover stakeholder concerns, then produce the corresponding views as catalogs, matrices, and diagrams.

Last updated: August 2026

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

Term Definition Practical Test

Stakeholder An individual, team, organization, or class thereof having an interest in, or concerns relative to, the outcome of the architecture. "Who cares what this looks like, and who can block it?"

Concern An interest in a system relevant to one or more of its stakeholders. Concerns determine the acceptability of the system. "What would make this stakeholder say no?"

Architecture Viewpoint A specification of the conventions for constructing and using a view — the template, notation, model kinds, and rules. "What are the rules for drawing this kind of picture?"

Architecture View A representation of a system from the perspective of a related set of concerns — the actual work product produced by applying a viewpoint. "What does this particular enterprise look like through that lens?"

  • 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:

Viewpoint (the specification) View (the work product)

Cost viewpoint: show application portfolio by annual run cost, licence model, and contract renewal date Acme's FY2027 application cost view, showing 14 applications and £4.2m of renewals in Q3

Deployment viewpoint: show nodes, network zones, and hosting location for every physical component The deployment view of Acme's order platform across two AWS regions

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:

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.

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:

  • Stakeholder Primary Concern Viewpoint Selected View Produced
  • CFO Total cost of ownership and renewal exposure Cost viewpoint FY2027 application cost view
  • CISO Data crossing trust boundaries Security viewpoint Payments platform security view
  • Head of Operations Failure modes and recovery time Availability viewpoint Order platform availability view
  • Regulator Where personal data is stored and processed Data residency viewpoint Personal data location view

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.