Linked.Archi ArchiMate 3.2 Example Viewpoints
type: Ontology
imports: core#
license: http://creativecommons.org/licenses/by/4.0/
preferred namespace prefix: amvp
creator: Kalin Maldzhanski
description: 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.
created: 2026-04-14
modified: 2026-04-14
publisher: Linked.Archi
publisher: linked.archi
status: draft
source: ch-Example-Viewpoints.html
version IRI: 3.2.0#
version info: 3.2.0

ArchiMate 3.2 Viewpoint Catalog
type: ConceptScheme
definition: 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.
scope note: 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.
source: ch-Example-Viewpoints.html
has top concept: Basic Viewpoints
has top concept: Motivation Viewpoints
has top concept: Strategy Viewpoints
has top concept: Implementation & Migration Viewpoints

Basic Viewpoints
type: Concept
definition: Viewpoints covering the three core layers (Business, Application, Technology).
top concept of: ArchiMate 3.2 Viewpoint Catalog
in scheme: ArchiMate 3.2 Viewpoint Catalog

Composition Viewpoints
type: Concept
definition: Viewpoints showing internal structure and aggregation of elements.
broader: Basic Viewpoints
in scheme: ArchiMate 3.2 Viewpoint Catalog
narrower: Organization Viewpoint
narrower: Information Structure Viewpoint
narrower: Technology Viewpoint
narrower: Layered Viewpoint
narrower: Physical Viewpoint

Support Viewpoints
type: Concept
definition: Viewpoints showing how elements in one layer support elements in a higher layer.
broader: Basic Viewpoints
in scheme: ArchiMate 3.2 Viewpoint Catalog
narrower: Product Viewpoint
narrower: Application Usage Viewpoint
narrower: Technology Usage Viewpoint

Cooperation Viewpoints
type: Concept
definition: Viewpoints showing how peer elements cooperate across aspects.
broader: Basic Viewpoints
in scheme: ArchiMate 3.2 Viewpoint Catalog
narrower: Business Process Cooperation Viewpoint
narrower: Application Cooperation Viewpoint

Realization Viewpoints
type: Concept
definition: Viewpoints showing how elements realize more abstract elements.
broader: Basic Viewpoints
in scheme: ArchiMate 3.2 Viewpoint Catalog
narrower: Service Realization Viewpoint
narrower: Implementation and Deployment Viewpoint

Motivation Viewpoints
type: Concept
definition: Viewpoints for modeling motivational aspects — stakeholders, goals, requirements.
top concept of: ArchiMate 3.2 Viewpoint Catalog
in scheme: ArchiMate 3.2 Viewpoint Catalog
narrower: Stakeholder Viewpoint
narrower: Goal Realization Viewpoint
narrower: Requirements Realization Viewpoint
narrower: Motivation Viewpoint

Strategy Viewpoints
type: Concept
definition: Viewpoints for strategic direction — capabilities, resources, value streams.
top concept of: ArchiMate 3.2 Viewpoint Catalog
in scheme: ArchiMate 3.2 Viewpoint Catalog
narrower: Strategy Viewpoint
narrower: Capability Map Viewpoint
narrower: Outcome Realization Viewpoint
narrower: Resource Map Viewpoint

Implementation & Migration Viewpoints
type: Concept
definition: Viewpoints for managing architecture change — projects, migration, plateaus.
top concept of: ArchiMate 3.2 Viewpoint Catalog
in scheme: ArchiMate 3.2 Viewpoint Catalog
narrower: Project Viewpoint
narrower: Migration Viewpoint
narrower: Implementation and Migration Viewpoint

Deciding
type: Purpose
definition: Evaluating options, portfolio rationalization, lifecycle planning, impact analysis.

Designing
type: Purpose
definition: Creating or refining architecture — structure, integration, deployment topology.

Informing
type: Purpose
definition: Communicating architecture to stakeholders — overviews, landscapes, roadmaps.

Governing
type: Purpose
definition: Compliance checking, standards enforcement, migration tracking.

Active Structure
type: Aspect
definition: Elements that perform behavior — actors, components, nodes, interfaces.

Behavior
type: Aspect
definition: Elements representing dynamic behavior — processes, functions, services, events.

Passive Structure
type: Aspect
definition: Elements on which behavior is performed — objects, artifacts, materials.

Motivation
type: Aspect
definition: Elements representing the why — goals, requirements, stakeholders, drivers.

Composite
type: Aspect
definition: Elements combining multiple aspects — products, groupings, locations.

Strategic
type: Perspective
definition: High-level direction, capabilities, and value streams.

Operational
type: Perspective
definition: Day-to-day business processes and organizational structure.

Application
type: Perspective
definition: Software systems supporting business operations.

Infrastructure
type: Perspective
definition: Technology platforms, networks, and physical assets.

Governance
type: Perspective
definition: Change management, migration, and project delivery.

Enterprise Architect
type: Stakeholder

Solution Architect
type: Stakeholder

Business Architect
type: Stakeholder

Application Architect
type: Stakeholder

Infrastructure Architect
type: Stakeholder

Security Architect
type: Stakeholder

Business Manager
type: Stakeholder

Product Manager
type: Stakeholder

Process Owner
type: Stakeholder

Software Developer
type: Stakeholder

Operations Manager
type: Stakeholder

Project Manager
type: Stakeholder

CIO
type: Stakeholder

CEO
type: Stakeholder

Data Architect
type: Stakeholder

Organizational structure and responsibilities
type: Concern
broader: Structural Concerns

Information structure and data consistency
type: Concern
broader: Structural Concerns

Infrastructure stability and security
type: Concern
broader: Structural Concerns

Physical environment and IT infrastructure relationships
type: Concern
broader: Structural Concerns

Deployment structure and artifact mapping
type: Concern
broader: Structural Concerns

Business process cooperation and information exchange
type: Concern
broader: Behavioral Concerns

Application integration and data sharing
type: Concern
broader: Behavioral Concerns

Service realization by processes and roles
type: Concern
broader: Behavioral Concerns

Application support for business processes
type: Concern
broader: Behavioral Concerns

Technology support for applications
type: Concern
broader: Behavioral Concerns

Stakeholder alignment and goal setting
type: Concern
broader: Motivation Concerns

Goal decomposition and requirements traceability
type: Concern
broader: Motivation Concerns

Requirements traceability to architecture elements
type: Concern
broader: Motivation Concerns

Full motivation landscape and rationale
type: Concern
broader: Motivation Concerns

Product offering and value proposition
type: Concern
broader: Motivation Concerns

Strategic direction and capability planning
type: Concern
broader: Strategic Concerns

Capability landscape and composition
type: Concern
broader: Strategic Concerns

Outcome delivery through capabilities
type: Concern
broader: Strategic Concerns

Resource allocation to capabilities
type: Concern
broader: Strategic Concerns

Project delivery and architecture change
type: Concern
broader: Governance Concerns

Architecture migration and transition planning
type: Concern
broader: Governance Concerns

Change management across architecture layers
type: Concern
broader: Governance Concerns

Impact of change and flexibility
type: Concern
broader: Governance Concerns

Cost optimization and rationalization
type: Concern
broader: Governance Concerns

Architecture overview and cross-layer consistency
type: Concern
broader: Governance Concerns

Structural Concerns
type: Concept
definition: Understanding what exists — the static structure of the enterprise.

Behavioral Concerns
type: Concept
definition: Understanding how things work together — processes, services, and cooperation.

Motivation Concerns
type: Concept
definition: Understanding why — goals, requirements, stakeholder interests, and value.

Strategic Concerns
type: Concept
definition: Understanding direction — capabilities, resources, and strategic planning.

Governance Concerns
type: Concept
definition: Managing change — migration, projects, impact analysis, and cost.

Organization Viewpoint
type: Viewpoint
definition: Shows the structure of the enterprise in terms of its business actors, roles, collaborations, and their relationships.
includes concept: BusinessActor
includes concept: BusinessRole
includes concept: BusinessCollaboration
includes concept: BusinessInterface
includes concept: Location
targets stakeholder: Business Manager
targets stakeholder: Business Architect
targets stakeholder: Enterprise Architect
viewpoint frames concern: Organizational structure and responsibilities
viewpoint covers aspect: Active Structure
viewpoint from perspective: Operational
viewpoint has purpose: Informing
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Composition Viewpoints
view type: Diagram
view type: Catalog

Information Structure Viewpoint
type: Viewpoint
definition: Shows the structure of the information used in the enterprise, including business objects, data objects, and their relationships.
includes concept: BusinessObject
includes concept: DataObject
includes concept: Representation
includes concept: Contract
includes concept: Meaning
targets stakeholder: Data Architect
targets stakeholder: Application Architect
targets stakeholder: Business Architect
viewpoint frames concern: Information structure and data consistency
viewpoint covers aspect: Passive Structure
viewpoint from perspective: Operational
viewpoint has purpose: Informing
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Composition Viewpoints
view type: Diagram

Technology Viewpoint
type: Viewpoint
definition: Shows the infrastructure and platforms underlying the information systems, in terms of nodes, devices, system software, networks, and artifacts.
includes concept: Node
includes concept: Device
includes concept: SystemSoftware
includes concept: Path
includes concept: CommunicationNetwork
includes concept: Artifact
includes concept: TechnologyFunction
includes concept: TechnologyProcess
includes concept: TechnologyService
includes concept: TechnologyInterface
targets stakeholder: Infrastructure Architect
targets stakeholder: Operations Manager
targets stakeholder: Security Architect
viewpoint frames concern: Infrastructure stability and security
viewpoint covers aspect: Active Structure
viewpoint covers aspect: Behavior
viewpoint from perspective: Infrastructure
viewpoint has purpose: Informing
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Composition Viewpoints
view type: Diagram

Layered Viewpoint
type: Viewpoint
definition: Provides an overview across multiple layers of the architecture, showing how elements from different layers relate through serving and realization.
includes concept: BusinessProcess
includes concept: BusinessFunction
includes concept: BusinessService
includes concept: ApplicationComponent
includes concept: ApplicationService
includes concept: Node
includes concept: Device
includes concept: SystemSoftware
includes concept: TechnologyService
targets stakeholder: Enterprise Architect
targets stakeholder: CIO
viewpoint frames concern: Architecture overview and cross-layer consistency
viewpoint frames concern: Impact of change and flexibility
viewpoint covers aspect: Behavior
viewpoint from perspective: Operational
viewpoint from perspective: Application
viewpoint from perspective: Infrastructure
viewpoint has purpose: Informing
viewpoint has purpose: Deciding
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Composition Viewpoints
view type: Diagram

Physical Viewpoint
type: Viewpoint
definition: Shows the physical environment and how it relates to IT infrastructure — equipment, facilities, distribution networks, and materials.
includes concept: Equipment
includes concept: Facility
includes concept: DistributionNetwork
includes concept: Material
includes concept: Node
includes concept: Device
includes concept: Path
targets stakeholder: Infrastructure Architect
targets stakeholder: Operations Manager
viewpoint frames concern: Physical environment and IT infrastructure relationships
viewpoint covers aspect: Active Structure
viewpoint from perspective: Infrastructure
viewpoint has purpose: Informing
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Composition Viewpoints
view type: Diagram

Product Viewpoint
type: Viewpoint
definition: Shows the products offered by the enterprise and the services, contracts, and business objects associated with them.
includes concept: Product
includes concept: BusinessService
includes concept: ApplicationService
includes concept: TechnologyService
includes concept: Contract
includes concept: BusinessObject
includes concept: BusinessProcess
includes concept: BusinessInterface
includes concept: Value
targets stakeholder: Product Manager
targets stakeholder: Business Manager
targets stakeholder: Business Architect
viewpoint frames concern: Product offering and value proposition
viewpoint covers aspect: Composite
viewpoint from perspective: Operational
viewpoint has purpose: Deciding
viewpoint has purpose: Informing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Support Viewpoints
view type: Diagram
view type: Catalog

Application Usage Viewpoint
type: Viewpoint
definition: Shows how applications support business processes and access business objects.
includes concept: BusinessProcess
includes concept: BusinessFunction
includes concept: BusinessObject
includes concept: ApplicationComponent
includes concept: ApplicationService
includes concept: DataObject
targets stakeholder: Application Architect
targets stakeholder: Process Owner
targets stakeholder: Business Architect
viewpoint frames concern: Application support for business processes
viewpoint covers aspect: Behavior
viewpoint from perspective: Application
viewpoint has purpose: Deciding
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Support Viewpoints
view type: Diagram

Technology Usage Viewpoint
type: Viewpoint
definition: Shows how technology infrastructure supports application components through nodes, devices, and system software.
includes concept: ApplicationComponent
includes concept: Node
includes concept: Device
includes concept: SystemSoftware
includes concept: TechnologyService
includes concept: Artifact
includes concept: CommunicationNetwork
targets stakeholder: Infrastructure Architect
targets stakeholder: Application Architect
targets stakeholder: Operations Manager
viewpoint frames concern: Technology support for applications
viewpoint covers aspect: Active Structure
viewpoint from perspective: Infrastructure
viewpoint has purpose: Deciding
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Support Viewpoints
view type: Diagram

Business Process Cooperation Viewpoint
type: Viewpoint
definition: Shows the relationships between business processes, including how they trigger each other, exchange information, and are supported by application services.
includes concept: BusinessProcess
includes concept: BusinessFunction
includes concept: BusinessInteraction
includes concept: BusinessEvent
includes concept: BusinessService
includes concept: BusinessRole
includes concept: BusinessCollaboration
includes concept: BusinessObject
includes concept: ApplicationService
includes concept: Representation
targets stakeholder: Process Owner
targets stakeholder: Business Architect
targets stakeholder: Business Manager
viewpoint frames concern: Business process cooperation and information exchange
viewpoint covers aspect: Behavior
viewpoint from perspective: Operational
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Cooperation Viewpoints
view type: Diagram

Application Cooperation Viewpoint
type: Viewpoint
definition: Shows the relationships between application components in terms of information flows, service dependencies, and shared data.
includes concept: ApplicationComponent
includes concept: ApplicationCollaboration
includes concept: ApplicationInterface
includes concept: ApplicationFunction
includes concept: ApplicationInteraction
includes concept: ApplicationService
includes concept: DataObject
targets stakeholder: Application Architect
targets stakeholder: Solution Architect
targets stakeholder: Software Developer
viewpoint frames concern: Application integration and data sharing
viewpoint covers aspect: Active Structure
viewpoint covers aspect: Behavior
viewpoint from perspective: Application
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Cooperation Viewpoints
view type: Diagram

Service Realization Viewpoint
type: Viewpoint
definition: Shows how business services are realized by business processes performed by business roles.
includes concept: BusinessService
includes concept: BusinessProcess
includes concept: BusinessFunction
includes concept: BusinessInteraction
includes concept: BusinessRole
includes concept: BusinessCollaboration
includes concept: BusinessObject
includes concept: DataObject
includes concept: ApplicationService
includes concept: ApplicationComponent
targets stakeholder: Business Architect
targets stakeholder: Process Owner
targets stakeholder: Application Architect
viewpoint frames concern: Service realization by processes and roles
viewpoint covers aspect: Behavior
viewpoint from perspective: Operational
viewpoint from perspective: Application
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Realization Viewpoints
view type: Diagram

Implementation and Deployment Viewpoint
type: Viewpoint
definition: Shows how applications are realized by artifacts and how artifacts are deployed on technology infrastructure.
includes concept: ApplicationComponent
includes concept: Artifact
includes concept: Node
includes concept: Device
includes concept: SystemSoftware
includes concept: Path
includes concept: CommunicationNetwork
targets stakeholder: Infrastructure Architect
targets stakeholder: Software Developer
targets stakeholder: Operations Manager
viewpoint frames concern: Deployment structure and artifact mapping
viewpoint covers aspect: Active Structure
viewpoint from perspective: Infrastructure
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Realization Viewpoints
view type: Diagram

Stakeholder Viewpoint
type: Viewpoint
definition: Shows the stakeholders, their concerns, and the goals that address those concerns.
includes concept: Stakeholder
includes concept: Driver
includes concept: Assessment
includes concept: Goal
includes concept: Outcome
includes concept: Principle
includes concept: Requirement
includes concept: Constraint
targets stakeholder: Enterprise Architect
targets stakeholder: Business Manager
targets stakeholder: CIO
targets stakeholder: CEO
viewpoint frames concern: Stakeholder alignment and goal setting
viewpoint covers aspect: Motivation
viewpoint from perspective: Strategic
viewpoint has purpose: Deciding
viewpoint has purpose: Informing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Motivation Viewpoints
view type: Diagram
view type: Matrix

Goal Realization Viewpoint
type: Viewpoint
definition: Shows how goals are refined into more concrete goals and how they are realized by requirements and constraints.
includes concept: Goal
includes concept: Outcome
includes concept: Principle
includes concept: Requirement
includes concept: Constraint
targets stakeholder: Enterprise Architect
targets stakeholder: Business Manager
viewpoint frames concern: Goal decomposition and requirements traceability
viewpoint covers aspect: Motivation
viewpoint from perspective: Strategic
viewpoint has purpose: Deciding
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Motivation Viewpoints
view type: Diagram

Requirements Realization Viewpoint
type: Viewpoint
definition: Shows how requirements are realized by core elements such as business processes, application components, and services.
includes concept: Requirement
includes concept: Constraint
includes concept: Goal
includes concept: BusinessProcess
includes concept: BusinessFunction
includes concept: BusinessService
includes concept: ApplicationComponent
includes concept: ApplicationService
includes concept: DataObject
targets stakeholder: Solution Architect
targets stakeholder: Application Architect
targets stakeholder: Business Architect
viewpoint frames concern: Requirements traceability to architecture elements
viewpoint covers aspect: Motivation
viewpoint from perspective: Strategic
viewpoint from perspective: Application
viewpoint has purpose: Deciding
viewpoint has purpose: Designing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Motivation Viewpoints
view type: Diagram
view type: Matrix

Motivation Viewpoint
type: Viewpoint
definition: Shows the full motivation structure: stakeholders, drivers, assessments, goals, outcomes, principles, requirements, and constraints, and how they relate to each other.
includes concept: Stakeholder
includes concept: Driver
includes concept: Assessment
includes concept: Goal
includes concept: Outcome
includes concept: Principle
includes concept: Requirement
includes concept: Constraint
includes concept: Meaning
includes concept: Value
targets stakeholder: Enterprise Architect
targets stakeholder: CIO
targets stakeholder: CEO
targets stakeholder: Business Manager
viewpoint frames concern: Full motivation landscape and rationale
viewpoint covers aspect: Motivation
viewpoint from perspective: Strategic
viewpoint has purpose: Informing
viewpoint has purpose: Deciding
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Motivation Viewpoints
view type: Diagram

Strategy Viewpoint
type: Viewpoint
definition: 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.
includes concept: Resource
includes concept: Capability
includes concept: ValueStream
includes concept: CourseOfAction
includes concept: Goal
includes concept: Outcome
includes concept: Principle
includes concept: Requirement
targets stakeholder: CEO
targets stakeholder: CIO
targets stakeholder: Enterprise Architect
targets stakeholder: Business Manager
viewpoint frames concern: Strategic direction and capability planning
viewpoint covers aspect: Behavior
viewpoint from perspective: Strategic
viewpoint has purpose: Deciding
viewpoint has purpose: Informing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Strategy Viewpoints
view type: Diagram

Capability Map Viewpoint
type: Viewpoint
definition: Shows the capabilities of the enterprise and how they are composed and related, typically as a hierarchical map.
includes concept: Capability
includes concept: Resource
includes concept: ValueStream
includes concept: CourseOfAction
includes concept: Outcome
targets stakeholder: Enterprise Architect
targets stakeholder: CIO
targets stakeholder: Business Manager
viewpoint frames concern: Capability landscape and composition
viewpoint covers aspect: Behavior
viewpoint from perspective: Strategic
viewpoint has purpose: Deciding
viewpoint has purpose: Informing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Strategy Viewpoints
view type: Diagram
view type: Catalog

Outcome Realization Viewpoint
type: Viewpoint
definition: Shows how outcomes are realized by capabilities and core elements, linking strategic intent to operational architecture.
includes concept: Outcome
includes concept: Capability
includes concept: ValueStream
includes concept: BusinessProcess
includes concept: BusinessFunction
includes concept: ApplicationComponent
includes concept: Value
targets stakeholder: Enterprise Architect
targets stakeholder: Business Manager
targets stakeholder: CIO
viewpoint frames concern: Outcome delivery through capabilities
viewpoint covers aspect: Behavior
viewpoint from perspective: Strategic
viewpoint has purpose: Deciding
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Strategy Viewpoints
view type: Diagram

Resource Map Viewpoint
type: Viewpoint
definition: Shows the resources of the enterprise and how they are assigned to capabilities and realized by core elements.
includes concept: Resource
includes concept: Capability
includes concept: BusinessActor
includes concept: BusinessRole
includes concept: ApplicationComponent
includes concept: Node
targets stakeholder: Enterprise Architect
targets stakeholder: Business Manager
targets stakeholder: Operations Manager
viewpoint frames concern: Resource allocation to capabilities
viewpoint covers aspect: Active Structure
viewpoint from perspective: Strategic
viewpoint has purpose: Deciding
viewpoint has purpose: Informing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Strategy Viewpoints
view type: Diagram
view type: Catalog

Project Viewpoint
type: Viewpoint
definition: Shows the work packages, deliverables, and their relationships to the architecture elements they change or create.
includes concept: WorkPackage
includes concept: Deliverable
includes concept: ImplementationEvent
includes concept: BusinessProcess
includes concept: ApplicationComponent
includes concept: Node
includes concept: Goal
targets stakeholder: Project Manager
targets stakeholder: Enterprise Architect
targets stakeholder: Solution Architect
viewpoint frames concern: Project delivery and architecture change
viewpoint covers aspect: Behavior
viewpoint from perspective: Governance
viewpoint has purpose: Governing
viewpoint has purpose: Deciding
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Implementation & Migration Viewpoints
view type: Diagram
view type: Catalog

Migration Viewpoint
type: Viewpoint
definition: Shows the transition from baseline to target architecture through plateaus and gaps, and the work packages that implement the transition.
includes concept: Plateau
includes concept: Gap
includes concept: WorkPackage
includes concept: Deliverable
includes concept: ImplementationEvent
targets stakeholder: Enterprise Architect
targets stakeholder: Project Manager
targets stakeholder: CIO
viewpoint frames concern: Architecture migration and transition planning
viewpoint covers aspect: Composite
viewpoint from perspective: Governance
viewpoint has purpose: Governing
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Implementation & Migration Viewpoints
view type: Diagram

Implementation and Migration Viewpoint
type: Viewpoint
definition: Shows the full implementation and migration landscape including plateaus, gaps, work packages, deliverables, and their relationships to architecture elements across all layers.
includes concept: Plateau
includes concept: Gap
includes concept: WorkPackage
includes concept: Deliverable
includes concept: ImplementationEvent
includes concept: BusinessProcess
includes concept: ApplicationComponent
includes concept: Node
includes concept: Goal
includes concept: Requirement
targets stakeholder: Enterprise Architect
targets stakeholder: Project Manager
targets stakeholder: CIO
targets stakeholder: Operations Manager
viewpoint frames concern: Change management across architecture layers
viewpoint frames concern: Architecture migration and transition planning
viewpoint covers aspect: Behavior
viewpoint covers aspect: Composite
viewpoint from perspective: Governance
viewpoint has purpose: Governing
viewpoint has purpose: Deciding
in scheme: ArchiMate 3.2 Viewpoint Catalog
broader: Implementation & Migration Viewpoints
view type: Diagram