Linked.Archi

Linked.Archi ArchiMate 3.2 Example Viewpoints

Viewpoint Definitions

https://meta.linked.archi/archimate3/viewpoints#

v3.2 draft amvp: Kalin Maldzhanski Linked.Archi Modified: 2026-10-17 License

The ArchiMate 3.2 example viewpoints of Appendix C as arch:Viewpoint individuals. Each states the elements it admits (arch:includesConcept — Grouping and the two junctions in every one, as the specification allows), its stakeholders (arch:targetsStakeholder), the concerns it frames (arch:viewpointFramesConcern) and its purposes (arch:viewpointHasPurpose). The catalogue groups them twice, as SKOS: by the specification's categories and by the scope its tables state (how many layers and aspects a viewpoint spans). The specification calls them examples, not a normative or exhaustive list; organizations may define their own.

Contents

Relationships and dependencies between applications

Application Cooperation Viewpoint

How application components cooperate: the information flowing between them, the services they offer and use, and the orchestration of services that together support a process.
Purpose: Designing
Concerns: Relationships and dependencies between applications, Orchestration and choreography of services, Consistency, Completeness, Reduction of complexity
View type: Diagram
Included concepts:
Location ApplicationComponent ApplicationCollaboration ApplicationInterface ApplicationProcess ApplicationFunction ApplicationInteraction ApplicationEvent ApplicationService DataObject Grouping Junction_And Junction_Or

Application structure

Application Structure Viewpoint

The structure of one or more applications: their components, interfaces and data, and the collaborations they take part in.
Purpose: Designing
Concerns: Application structure, Consistency, Completeness, Reduction of complexity
View type: Diagram
Included concepts:
ApplicationComponent ApplicationInterface ApplicationCollaboration DataObject Grouping Junction_And Junction_Or

Consistency

Application Usage Viewpoint

How applications are used in the enterprise's business processes and functions, and by its actors and roles.
Purpose: Designing, Deciding
Concerns: Consistency, Completeness, Reduction of complexity
View type: Diagram
Included concepts:
BusinessActor BusinessRole BusinessCollaboration BusinessProcess BusinessFunction BusinessInteraction BusinessEvent BusinessObject ApplicationComponent ApplicationCollaboration ApplicationInterface ApplicationProcess ApplicationFunction ApplicationInteraction ApplicationEvent ApplicationService DataObject Grouping Junction_And Junction_Or

Dependencies between business processes

Business Process Cooperation Viewpoint

How business processes relate to each other and to their environment: what triggers what, what flows between them, the information they share and the applications that support them.
Purpose: Designing, Deciding
Concerns: Dependencies between business processes, Consistency, Completeness, Responsibilities
View type: Diagram
Included concepts:
BusinessActor BusinessRole BusinessCollaboration Location BusinessInterface BusinessProcess BusinessFunction BusinessInteraction BusinessEvent BusinessService BusinessObject Representation ApplicationComponent ApplicationCollaboration ApplicationInterface ApplicationProcess ApplicationFunction ApplicationInteraction ApplicationEvent ApplicationService DataObject Grouping Junction_And Junction_Or

Architecture strategy

Capability Map Viewpoint

The enterprise's capabilities, the resources they need and the outcomes they produce.
Purpose: Designing, Deciding
Concerns: Architecture strategy, Architecture tactics, Motivation
View type: Diagram, Catalog
Included concepts:
Outcome Capability Resource Grouping Junction_And Junction_Or

Motivation Viewpoint

The motivation of the architecture as a whole: stakeholders, drivers, assessments, goals, principles, requirements, constraints, outcomes, values and meanings.
Purpose: Designing, Deciding, Informing
Concerns: Architecture strategy, Architecture tactics, Motivation
View type: Diagram
Included concepts:
Stakeholder Driver Assessment Goal Principle Requirement Constraint Outcome Value Meaning Grouping Junction_And Junction_Or

Resource Map Viewpoint

The resources the enterprise has, the capabilities they enable and the work packages that change them.
Purpose: Designing, Deciding
Concerns: Architecture strategy, Architecture tactics, Motivation
View type: Diagram, Catalog
Included concepts:
Resource Capability WorkPackage Grouping Junction_And Junction_Or

Value Stream Viewpoint

The value streams through which the enterprise creates value, the capabilities that support them, the outcomes they lead to and the stakeholders who receive the value.
Purpose: Designing, Deciding
Concerns: Architecture strategy, Architecture tactics, Motivation
View type: Diagram
Included concepts:
ValueStream Capability Outcome Stakeholder Grouping Junction_And Junction_Or

Architecture mission

Goal Realization Viewpoint

How high-level goals are refined into more concrete goals, outcomes, requirements and constraints, and the principles that guide them.
Purpose: Designing, Deciding
Concerns: Architecture mission, Architecture strategy, Architecture tactics, Motivation
View type: Diagram
Included concepts:
Goal Principle Requirement Constraint Outcome Grouping Junction_And Junction_Or

Stakeholder Viewpoint

The stakeholders, their drivers, the assessments of those drivers and the goals and outcomes that address them.
Purpose: Designing, Deciding, Informing
Concerns: Architecture mission, Architecture strategy, Motivation
View type: Diagram, Matrix
Included concepts:
Stakeholder Driver Assessment Goal Outcome Grouping Junction_And Junction_Or

Structure of application platforms and how they relate to supporting technology

Implementation and Deployment Viewpoint

How applications are mapped onto the technology that supports them: platforms, system software and artifacts.
Purpose: Designing, Deciding
Concerns: Structure of application platforms and how they relate to supporting technology
View type: Diagram
Included concepts:
ApplicationComponent ApplicationCollaboration ApplicationInterface ApplicationProcess ApplicationFunction ApplicationInteraction ApplicationEvent ApplicationService DataObject SystemSoftware TechnologyInterface Path TechnologyProcess TechnologyFunction TechnologyInteraction TechnologyService Artifact Grouping Junction_And Junction_Or

Architecture vision

Project Viewpoint

The management of architecture change: work packages, the deliverables and events they produce, who performs them and the goals and outcomes they serve.
Purpose: Deciding, Informing
Concerns: Architecture vision, Architecture policies, Motivation
View type: Diagram, Catalog
Included concepts:
Goal Outcome WorkPackage ImplementationEvent Deliverable BusinessActor BusinessRole Grouping Junction_And Junction_Or

Structure and dependencies of the data and information used

Information Structure Viewpoint

The structure of the information the enterprise uses: business and data objects, their representations, the artifacts that hold them and what they mean.
Purpose: Designing
Concerns: Structure and dependencies of the data and information used, Consistency, Completeness
View type: Diagram
Included concepts:
BusinessObject Representation DataObject Artifact Meaning Grouping Junction_And Junction_Or

History of models

Migration Viewpoint

The transition from an existing architecture to a target architecture, through plateaus and the gaps between them.
Purpose: Designing, Deciding, Informing
Concerns: History of models
View type: Diagram
Included concepts:
Plateau Gap Grouping Junction_And Junction_Or

Competencies, authority and responsibilities

Organization Viewpoint

The structure of an organization: its business actors, roles and collaborations, where they are, and the interfaces through which they are reached.
Purpose: Designing, Deciding, Informing
Concerns: Competencies, authority and responsibilities
View type: Diagram, Catalog
Included concepts:
BusinessActor BusinessRole BusinessCollaboration Location BusinessInterface Grouping Junction_And Junction_Or

Business-oriented results

The physical environment and how it relates to the IT infrastructure

Physical Viewpoint

The physical environment — equipment, facilities, distribution networks and materials — and how it relates to the IT infrastructure.
Purpose: Designing
Concerns: The physical environment and how it relates to the IT infrastructure
View type: Diagram
Included concepts:
Location Node Device Equipment Facility Path CommunicationNetwork DistributionNetwork Material Grouping Junction_And Junction_Or

Product development

Product Viewpoint

What a product contains: the services, behaviour, objects, contracts and value it offers, and who delivers it.
Purpose: Designing, Deciding
Concerns: Product development, Value offered by products
View type: Diagram, Catalog
Included concepts:
BusinessActor BusinessRole BusinessCollaboration BusinessInterface BusinessProcess BusinessFunction BusinessInteraction BusinessEvent BusinessService BusinessObject Product Contract ApplicationComponent ApplicationCollaboration ApplicationInterface ApplicationProcess ApplicationFunction ApplicationInteraction ApplicationEvent ApplicationService DataObject TechnologyService Artifact Material Value Grouping Junction_And Junction_Or

Added value of business processes

Service Realization Viewpoint

How business services are realized by the processes, functions and applications behind them.
Purpose: Designing, Deciding
Concerns: Added value of business processes, Consistency, Completeness, Responsibilities
View type: Diagram
Included concepts:
BusinessActor BusinessRole BusinessCollaboration BusinessInterface BusinessProcess BusinessFunction BusinessInteraction BusinessEvent BusinessService BusinessObject Representation ApplicationComponent ApplicationCollaboration ApplicationInterface ApplicationProcess ApplicationFunction ApplicationInteraction ApplicationEvent ApplicationService DataObject Grouping Junction_And Junction_Or

Strategy development

Strategy Viewpoint

A high-level strategic overview: courses of action, capabilities, value streams, resources and the outcomes they pursue.
Purpose: Designing, Deciding
Concerns: Strategy development
View type: Diagram
Included concepts:
CourseOfAction Capability ValueStream Resource Outcome Grouping Junction_And Junction_Or

Dependencies

Technology Usage Viewpoint

How applications use technology: the nodes, system software, networks and technology services that serve them.
Purpose: Designing
Concerns: Dependencies, Performance, Scalability
View type: Diagram
Included concepts:
ApplicationComponent ApplicationCollaboration ApplicationProcess ApplicationFunction ApplicationInteraction ApplicationEvent DataObject Node Device TechnologyCollaboration SystemSoftware TechnologyInterface CommunicationNetwork Path TechnologyProcess TechnologyFunction TechnologyInteraction TechnologyService TechnologyEvent Artifact Grouping Junction_And Junction_Or

Stability, security, dependencies and costs of the infrastructure

Technology Viewpoint

The infrastructure and platforms beneath the information systems — nodes, devices, system software and networks — and the technology behaviour they offer.
Purpose: Designing
Concerns: Stability, security, dependencies and costs of the infrastructure
View type: Diagram
Included concepts:
Location Node TechnologyCollaboration Device SystemSoftware TechnologyInterface CommunicationNetwork Path TechnologyProcess TechnologyFunction TechnologyInteraction TechnologyService TechnologyEvent Artifact Grouping Junction_And Junction_Or
Source: linked-archi-meta • Linked.Archi