Study guide
12.1 Stakeholders, Concerns, Views & Viewpoints
TOGAF Enterprise Architecture Foundation OGEA-101
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Enterprise Architecture & the TOGAF Standard
1.1 The Enterprise, the Purpose of EA & Its Benefits 1.2 Why the TOGAF Standard: Framework, Documentation Set & Certification 1.3 The Four Architecture Domains & Architecture Abstraction
2 Chapter 2: Enterprise Continuum, Architecture Repository, Content Framework & Capability
2.1 The Enterprise Continuum 2.2 The Architecture Repository 2.3 The TOGAF Content Framework & Enterprise Metamodel 2.4 Architecture Capability
3 Chapter 3: Key TOGAF Terminology
3.1 Terms for Architecture Domains, Levels, States & Capability 3.2 Terms for Work Products, Models, Requirements & Change
4 Chapter 4: ADM Fundamentals, Preliminary Phase & Phase A
4.1 The ADM Cycle, Its Phases & Information Flow 4.2 Draft vs. Approved Deliverables & the Iterative ADM 4.3 Governing EA, Scoping the Architecture & Alternatives 4.4 The Preliminary Phase 4.5 Phase A: Architecture Vision
5 Chapter 5: Architecture Definition — Phases B, C & D
5.1 Phase B: Business Architecture 5.2 Phase C: Information Systems Architectures — Data & Application 5.3 Phase D: Technology Architecture
6 Chapter 6: Opportunities, Migration Planning & Implementation Governance (Phases E, F & G)
6.1 Phase E: Opportunities & Solutions 6.2 Phase F: Migration Planning 6.3 Phase G: Implementation Governance
7 Chapter 7: Phase H, Requirements Management & Agile Delivery
7.1 Phase H: Architecture Change Management 7.2 Requirements Management 7.3 Supporting Agile Software Development with the ADM
8 Chapter 8: ADM Techniques I — Guidelines, Principles, Business Scenarios & Gap Analysis
8.1 ADM Guidelines & Techniques and Architecture Principles 8.2 Business Scenarios 8.3 Gap Analysis
9 Chapter 9: ADM Techniques II — Interoperability, Transformation Readiness & Risk
9.1 Interoperability 9.2 Business Transformation Readiness Assessment 9.3 Risk Management
10 Chapter 10: Applying the ADM
10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases 10.2 The Architecture Landscape: Strategic, Segment & Capability Levels 10.3 Architecture Partitioning 10.4 The Four Purposes of Architecture 10.5 Applying the TOGAF Standard in the Digital Enterprise
11 Chapter 11: Architecture Governance
11.1 Architecture Governance: Concept & Benefits 11.2 The Architecture Board 11.3 Architecture Contracts 11.4 Architecture Compliance
12 Chapter 12: Architecture Content
12.1 Stakeholders, Concerns, Views & Viewpoints 12.2 Building Blocks: ABBs & SBBs 12.3 ADM Deliverables I: Preliminary Phase and Architecture Vision 12.4 ADM Deliverables II: From Architecture Definition to Change
12.1 Stakeholders, Concerns, Views & Viewpoints
Key Takeaways Explain This Topic AI
TOGAF defines a stakeholder as an individual, team, organization, or class thereof, having an interest in a system.
A concern is an interest in a system relevant to one or more of its stakeholders and may determine the acceptability of the system.
An architecture view is a representation of a system from the perspective of a related set of concerns.
An architecture viewpoint is a specification of the conventions for a particular kind of architecture view.
The TOGAF stakeholder power grid quadrants are Key Players, Keep Satisfied, Keep Informed, and Minimal Effort.
Last updated: September 2026
12.1 Stakeholders, Concerns, Views & Viewpoints
"Architecture Content" is worth 5 of 40 questions . The first learning outcome is to define and explain stakeholders, concerns, architecture views, architecture viewpoints, and their relationships . These concepts are adapted from the formal definitions in ISO/IEC/IEEE 42010, and they explain why architects produce different views for different people.
Definitions
- Term TOGAF Standard, 10th Edition definition
- Stakeholder An individual, team, organization, or class thereof, having an interest in a system
Concern An interest in a system relevant to one or more of its stakeholders. Concerns may pertain to any aspect of the system's functioning, development, or operation, including performance, reliability, security, distribution, and evolvability, and may determine the acceptability of the system
Architecture View A representation of a system from the perspective of a related set of concerns
Architecture Viewpoint A specification of the conventions for a particular kind of architecture view. It can also be seen as the definition or schema for that kind of view, establishing the conventions for constructing, interpreting, and using a view to address a specific concern or set of concerns about a system-of-interest
Model Kind Conventions for a type of modeling; an architecture viewpoint references one or more model kinds, and an architecture view incorporates one or more models
How the Concepts Relate
The ability to create specific views of parts of a complex architecture is fundamental to communicating with, and allaying the concerns of, stakeholders. To gain their understanding and support, information must be presented in a form each stakeholder will relate to and understand.
The relationships follow a simple chain:
A system (for TOGAF, often the enterprise itself) has an architecture .
Stakeholders have an interest in the system.
Stakeholders have concerns about the system.
An architecture viewpoint frames particular concerns by setting the conventions for a kind of view.
An architecture view conforms to its viewpoint and addresses the concerns of the stakeholders.
Views are composed of models , built according to the model kinds the viewpoint references.
View Versus Viewpoint
A simple way to remember the difference:
A view is what you see — specific to the architecture for which it is created.
A viewpoint is where you are looking from — the vantage point or perspective that determines what you see. Viewpoints are generic and can be stored in libraries for re-use.
Every view has an associated viewpoint that describes it, at least implicitly. The Architecture Repository's Reference Library can hold a Viewpoint Library of re-usable viewpoint specifications.
The Blueprint Analogy
The Viewpoint (Drafting Standard & Legend) : The engineering standard defining symbols for circuit breakers, 220V wiring, and ground paths. It does not depict a specific building; it defines conventions for drafting any electrical layout.
The View (The Blueprint) : The actual CAD drawing for Floor 10 of a specific building, drawn conforming to the drafting standard.
Stakeholder Management
Identifying stakeholders and their concerns is so important that the ADM Techniques document includes a Stakeholder Management technique, used in Phase A and throughout the ADM. Its steps are:
Identify Stakeholders — who is affected by, or can influence, the architecture work
Classify Stakeholder Positions — for example, their ability to disrupt the change, their current and required understanding, their current and required commitment, and their power and interest
Determine Stakeholder Management Approach — how each stakeholder group will be engaged
Tailor Engagement Deliverables — identify the catalogs, matrices, diagrams, and views that address each group's concerns
The Stakeholder Power Grid
TOGAF uses a power/interest grid to decide the engagement approach:
- Low interest High interest
- High power Keep Satisfied Key Players
- Low power Minimal Effort Keep Informed
Key Players need the fullest engagement; Keep Satisfied stakeholders need enough information to stay content without being overwhelmed; Keep Informed stakeholders need regular updates; Minimal Effort stakeholders need only basic monitoring and communication. The results are recorded in a stakeholder map, which feeds the Communications Plan and the choice of viewpoints .
Worked Example
Stakeholder Key concern Viewpoint selected View produced
Chief Financial Officer Cost of the target architecture and return on investment Business value and roadmap viewpoint Roadmap with costed Transition Architectures
Chief Information Security Officer Protection of customer data Security viewpoint Data flow view showing encryption and access controls
Operations manager Service availability during migration Operational viewpoint Deployment and cutover view
Application developers Interfaces they must build against Application communication viewpoint Interface and integration diagram
The same architecture is represented four ways, each view conforming to a viewpoint chosen to address a specific set of concerns.
Common Exam Pitfalls
Swapping view and viewpoint. The view is the representation; the viewpoint is the specification of conventions for that kind of view.
Thinking a viewpoint is specific to one project. Viewpoints are generic and re-usable; views are specific to an architecture.
Mislabeling the power grid. TOGAF's quadrants are Key Players, Keep Satisfied, Keep Informed, and Minimal Effort.
Forgetting that concerns determine acceptability. Concerns may determine whether the system is acceptable to its stakeholders.