Linked.Archi ArchiMate 3.2 Example Viewpoints
ArchiMate 3.2 example viewpoints as arch:Viewpoint individuals. Each viewpoint specifies allowed element types (arch:includesConcept), target stakeholders (arch:targetsStakeholder), and framed concerns (arch:viewpointFramesConcern). Organizations may define additional custom viewpoints.
Linked.Archi
ArchiMate 3.2 Viewpoint Catalog
Classification of ArchiMate example viewpoints by category, following the ArchiMate specification's own grouping from Chapter 14 and Appendix C. The four top-level categories correspond to the ArchiMate framework dimensions. The sub-categories under Basic Viewpoints (Composition, Support, Cooperation, Realization) correspond to the ArchiMate viewpoint classification matrix.
This grouping is ArchiMate-specific. Other frameworks use different organizations — e.g., TOGAF groups viewpoints by ADM phase (A through H). ISO/IEC/IEEE 42010 does not prescribe a specific grouping.
Basic Viewpoints
Viewpoints covering the three core layers (Business, Application, Technology).
Composition Viewpoints
Viewpoints showing internal structure and aggregation of elements.
Support Viewpoints
Viewpoints showing how elements in one layer support elements in a higher layer.
Cooperation Viewpoints
Viewpoints showing how peer elements cooperate across aspects.
Realization Viewpoints
Viewpoints showing how elements realize more abstract elements.
Motivation Viewpoints
Viewpoints for modeling motivational aspects — stakeholders, goals, requirements.
Strategy Viewpoints
Viewpoints for strategic direction — capabilities, resources, value streams.
Implementation & Migration Viewpoints
Viewpoints for managing architecture change — projects, migration, plateaus.
Deciding
Evaluating options, portfolio rationalization, lifecycle planning, impact analysis.
Designing
Creating or refining architecture — structure, integration, deployment topology.
Informing
Communicating architecture to stakeholders — overviews, landscapes, roadmaps.
Governing
Compliance checking, standards enforcement, migration tracking.
Active Structure
Elements that perform behavior — actors, components, nodes, interfaces.
Behavior
Elements representing dynamic behavior — processes, functions, services, events.
Passive Structure
Elements on which behavior is performed — objects, artifacts, materials.
Motivation
Elements representing the why — goals, requirements, stakeholders, drivers.
Composite
Elements combining multiple aspects — products, groupings, locations.
Strategic
High-level direction, capabilities, and value streams.
Operational
Day-to-day business processes and organizational structure.
Application
Software systems supporting business operations.
Infrastructure
Technology platforms, networks, and physical assets.
Governance
Change management, migration, and project delivery.
Enterprise Architect
Solution Architect
Business Architect
Application Architect
Infrastructure Architect
Security Architect
Business Manager
Product Manager
Process Owner
Software Developer
Operations Manager
Project Manager
CIO
CEO
Data Architect
Organizational structure and responsibilities
Information structure and data consistency
Infrastructure stability and security
Physical environment and IT infrastructure relationships
Deployment structure and artifact mapping
Business process cooperation and information exchange
Application integration and data sharing
Service realization by processes and roles
Application support for business processes
Technology support for applications
Stakeholder alignment and goal setting
Goal decomposition and requirements traceability
Requirements traceability to architecture elements
Full motivation landscape and rationale
Product offering and value proposition
Strategic direction and capability planning
Capability landscape and composition
Outcome delivery through capabilities
Resource allocation to capabilities
Project delivery and architecture change
Architecture migration and transition planning
Change management across architecture layers
Impact of change and flexibility
Cost optimization and rationalization
Architecture overview and cross-layer consistency
Structural Concerns
Understanding what exists — the static structure of the enterprise.
Behavioral Concerns
Understanding how things work together — processes, services, and cooperation.
Motivation Concerns
Understanding why — goals, requirements, stakeholder interests, and value.
Strategic Concerns
Understanding direction — capabilities, resources, and strategic planning.
Governance Concerns
Managing change — migration, projects, impact analysis, and cost.
Organization Viewpoint
Shows the structure of the enterprise in terms of its business actors, roles, collaborations, and their relationships.
Information Structure Viewpoint
Shows the structure of the information used in the enterprise, including business objects, data objects, and their relationships.
Technology Viewpoint
Shows the infrastructure and platforms underlying the information systems, in terms of nodes, devices, system software, networks, and artifacts.
Layered Viewpoint
Provides an overview across multiple layers of the architecture, showing how elements from different layers relate through serving and realization.
Physical Viewpoint
Shows the physical environment and how it relates to IT infrastructure — equipment, facilities, distribution networks, and materials.
Product Viewpoint
Shows the products offered by the enterprise and the services, contracts, and business objects associated with them.
Application Usage Viewpoint
Shows how applications support business processes and access business objects.
Technology Usage Viewpoint
Shows how technology infrastructure supports application components through nodes, devices, and system software.
Business Process Cooperation Viewpoint
Shows the relationships between business processes, including how they trigger each other, exchange information, and are supported by application services.
Application Cooperation Viewpoint
Shows the relationships between application components in terms of information flows, service dependencies, and shared data.
Service Realization Viewpoint
Shows how business services are realized by business processes performed by business roles.
Implementation and Deployment Viewpoint
Shows how applications are realized by artifacts and how artifacts are deployed on technology infrastructure.
Stakeholder Viewpoint
Shows the stakeholders, their concerns, and the goals that address those concerns.
Goal Realization Viewpoint
Shows how goals are refined into more concrete goals and how they are realized by requirements and constraints.
Requirements Realization Viewpoint
Shows how requirements are realized by core elements such as business processes, application components, and services.
Motivation Viewpoint
Shows the full motivation structure: stakeholders, drivers, assessments, goals, outcomes, principles, requirements, and constraints, and how they relate to each other.
Strategy Viewpoint
Shows the strategic direction of the enterprise in terms of resources, capabilities, value streams, and courses of action, and how they relate to motivation elements.
Capability Map Viewpoint
Shows the capabilities of the enterprise and how they are composed and related, typically as a hierarchical map.
Outcome Realization Viewpoint
Shows how outcomes are realized by capabilities and core elements, linking strategic intent to operational architecture.
Resource Map Viewpoint
Shows the resources of the enterprise and how they are assigned to capabilities and realized by core elements.
Project Viewpoint
Shows the work packages, deliverables, and their relationships to the architecture elements they change or create.
Migration Viewpoint
Shows the transition from baseline to target architecture through plateaus and gaps, and the work packages that implement the transition.
Implementation and Migration Viewpoint
Shows the full implementation and migration landscape including plateaus, gaps, work packages, deliverables, and their relationships to architecture elements across all layers.