Linked.Archi Core Viewpoints
type: Ontology
imports: core#
license: http://creativecommons.org/licenses/by/4.0/
preferred namespace prefix: archvp
creator: Kalin Maldzhanski
description: Framework-agnostic architecture viewpoints derived from ISO/IEC/IEEE 42010 and common architecture practice. These are universal viewpoints that any modeling language can use — ArchiMate, TOGAF, C4, Backstage, or custom metamodels can specialize or reference them.
created: 2026-04-15
modified: 2026-04-15
publisher: Linked.Archi
publisher: linked.archi
status: draft
version IRI: 0.1.0#
version info: 0.1.0

Deciding
type: Purpose
definition: Evaluating options, making trade-offs, selecting alternatives.

Designing
type: Purpose
definition: Creating or refining architecture — defining structure and behavior.

Informing
type: Purpose
definition: Communicating architecture to stakeholders for understanding and alignment.

Governing
type: Purpose
definition: Ensuring compliance, enforcing standards, managing change.

Structure
type: Concern
definition: What components exist and how they are organized.

Behavior
type: Concern
definition: How components interact, what processes execute, what flows occur.

Deployment
type: Concern
definition: Where components run and how they are distributed.

Dependencies
type: Concern
definition: What depends on what — impact analysis and change propagation.

Governance
type: Concern
definition: Who owns what, what standards apply, what decisions were made.

Evolution
type: Concern
definition: How the architecture changes over time — roadmaps and transitions.

Quality
type: Concern
definition: Non-functional characteristics — performance, security, reliability.

Cost
type: Concern
definition: Financial aspects — total cost of ownership, licensing, operational cost.

Integration
type: Concern
definition: How systems connect — interfaces, protocols, data exchange.

Stakeholder Interests
type: Concern
definition: Who cares about what — mapping stakeholders to their concerns.

Landscape Overview
type: Viewpoint
definition: High-level overview of the architecture showing major components and their relationships across all domains. The entry point for understanding the architecture.
viewpoint has purpose: Informing
viewpoint frames concern: Structure
viewpoint frames concern: Dependencies
view type: Diagram

Component Catalog
type: Viewpoint
definition: Inventory of all architecture components with key attributes (owner, status, domain, technology). The foundation for portfolio management.
viewpoint has purpose: Informing
viewpoint has purpose: Deciding
viewpoint frames concern: Structure
viewpoint frames concern: Governance
view type: Catalog

Process Flow
type: Viewpoint
definition: Shows the sequence of activities in a process, including decision points, parallel paths, and handoffs between actors.
viewpoint has purpose: Designing
viewpoint frames concern: Behavior
view type: Diagram

Interface Map
type: Viewpoint
definition: Shows how components connect to each other — interfaces, protocols, data flows, and integration patterns.
viewpoint has purpose: Designing
viewpoint frames concern: Integration
viewpoint frames concern: Dependencies
view type: Diagram

Deployment Map
type: Viewpoint
definition: Shows where components are deployed — infrastructure nodes, environments, locations, and their hosting relationships.
viewpoint has purpose: Designing
viewpoint has purpose: Informing
viewpoint frames concern: Deployment
view type: Diagram

Dependency Matrix
type: Viewpoint
definition: Shows dependencies between components as a matrix — which components depend on which, enabling impact analysis.
viewpoint has purpose: Deciding
viewpoint frames concern: Dependencies
view type: Matrix

Impact Analysis
type: Viewpoint
definition: Shows the propagation of change from a source component through its dependencies — what breaks if this changes.
viewpoint has purpose: Deciding
viewpoint frames concern: Dependencies
viewpoint frames concern: Evolution
view type: Diagram
view type: Matrix

Decision Log
type: Viewpoint
definition: Catalog of architecture decisions with their context, options considered, rationale, and status. Supports traceability and institutional memory.
viewpoint has purpose: Governing
viewpoint frames concern: Governance
view type: Catalog

Stakeholder Map
type: Viewpoint
definition: Maps stakeholders to their concerns, influence, and the viewpoints that address them. The starting point for architecture communication planning.
viewpoint has purpose: Informing
viewpoint has purpose: Deciding
viewpoint frames concern: Stakeholder Interests
view type: Matrix

Standards Compliance
type: Viewpoint
definition: Shows which components comply with which standards, and where deviations exist. Supports governance reviews.
viewpoint has purpose: Governing
viewpoint frames concern: Governance
viewpoint frames concern: Quality
view type: Matrix

Roadmap
type: Viewpoint
definition: Shows the planned evolution of the architecture over time — current state, target state, and the transition steps between them.
viewpoint has purpose: Deciding
viewpoint has purpose: Informing
viewpoint frames concern: Evolution
view type: Diagram

Gap Analysis
type: Viewpoint
definition: Shows the differences between baseline and target architecture — what needs to be added, changed, or removed.
viewpoint has purpose: Deciding
viewpoint frames concern: Evolution
viewpoint frames concern: Cost
view type: Matrix