Linked.Archi

Linked.Archi UML 2.5.1 Viewpoints

Viewpoint Definitions

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

v0.1.0 draft umlvp: Kalin Maldzhanski Linked.Archi Modified: 2026-02-01 License

UML 2.5.1 diagram types formalized as Linked.Archi viewpoints. Each of the 14 UML diagram types is represented as an arch:Viewpoint instance with its included concepts, purpose, and framed concerns.

Contents

BehaviorConcern

Activity Diagram

Shows workflows with actions, control flows, object flows, decision nodes, fork/join nodes, and swim lanes. Used for business process and algorithm modeling.
Purpose: Designing
Concerns: BehaviorConcern
View type: Diagram
Included concepts:
Activity Action ControlNode ObjectNode ActivityPartition

Communication Diagram

Shows message exchanges organized by object relationships rather than time ordering. Same information as Sequence Diagram, different layout.
Purpose: Designing
Concerns: BehaviorConcern, IntegrationConcern
View type: Diagram
Included concepts:
Interaction Lifeline Message

Interaction Overview Diagram

Shows high-level flow of control between interaction fragments. A variant of the Activity Diagram where nodes are Interactions or InteractionUses.
Purpose: Designing
Concerns: BehaviorConcern
View type: Diagram
Included concepts:
Interaction InteractionUse

Sequence Diagram

Shows time-ordered message exchanges between lifelines with activation bars, combined fragments (alt, loop, opt, par), and return messages. The richest UML behavioral diagram.
Purpose: Designing
Concerns: BehaviorConcern, IntegrationConcern
View type: Diagram
Included concepts:
Interaction Lifeline Message CombinedFragment ExecutionSpecification

State Machine Diagram

Shows states, transitions, events, and guards for a single object lifecycle. Used for protocol and lifecycle modeling.
Purpose: Designing
Concerns: BehaviorConcern
View type: Diagram
Included concepts:
StateMachine State Pseudostate Region Transition

Timing Diagram

Shows state changes over time with precise timing constraints. Used for real-time and embedded systems.
Purpose: Designing
Concerns: BehaviorConcern
View type: Diagram
Included concepts:
Interaction Lifeline State

StructureConcern

Class Diagram

Shows classes, interfaces, data types, enumerations, and their relationships (association, aggregation, composition, generalization, realization, dependency). The most commonly used UML diagram type.
Purpose: Designing
Concerns: StructureConcern
View type: Diagram
Included concepts:
Class Interface DataType Enumeration Property Operation

Component Diagram

Shows components, their provided and required interfaces, ports, connectors, and dependencies. Used for modular system design.
Purpose: Designing
Concerns: StructureConcern, DependencyConcern
View type: Diagram
Included concepts:
Component Interface Port Connector

Composite Structure Diagram

Shows the internal structure of a classifier, including parts, ports, and connectors. Used for detailed component design.
Purpose: Designing
Concerns: StructureConcern
View type: Diagram
Included concepts:
Class Port Connector Collaboration

Object Diagram

Shows instances of classes and their relationships at a specific point in time. A snapshot of the system state.
Purpose: Informing
Concerns: StructureConcern
View type: Diagram
Included concepts:
Class

Package Diagram

Shows packages, their contents, and dependencies (import, merge). Used for organizing large models.
Purpose: Designing
Concerns: StructureConcern, DependencyConcern
View type: Diagram
Included concepts:
Package Model

Profile Diagram

Shows stereotypes, profiles, and profile applications. Used for defining UML extensions for specific domains or platforms.
Purpose: Designing
Concerns: StructureConcern
View type: Diagram
Included concepts:
Profile Stereotype

DeploymentConcern

Deployment Diagram

Shows the mapping of software artifacts to infrastructure nodes, devices, and execution environments.
Purpose: Designing, Informing
Concerns: DeploymentConcern
View type: Diagram
Included concepts:
Node Device ExecutionEnvironment Artifact DeploymentSpecification

StakeholderConcern

Use Case Diagram

Shows actors, use cases, and their relationships (include, extend, generalization). Used for requirements capture and system scope definition.
Purpose: Informing
Concerns: StakeholderConcern, BehaviorConcern
View type: Diagram
Included concepts:
Actor UseCase
Source: linked-archi-meta • Linked.Archi