This skill should be used when the user asks about "ArchiMate relationships", "composition vs aggregation", "realization relationship", "serving relationship", "assignment relationship", "triggering", "flow relationship", "access relationship", "influence", "specialization", "cross-layer relationships", or needs help connecting ArchiMate elements correctly.
From archimatenpx claudepluginhub thomasrohde/marketplace --plugin archimateThis skill uses the workspace's default tool permissions.
references/relationship-patterns.mdDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
ArchiMate defines 11 core relationships organized into four categories. Understanding proper relationship usage is critical for model quality and analysis.
| Relationship | Notation | Usage |
|---|---|---|
| Composition | Solid line + filled diamond | Strong whole-part; parts cannot exist independently |
| Aggregation | Solid line + hollow diamond | Weak whole-part; parts may belong to multiple aggregations |
| Assignment | Solid line + circle at source | Who/what performs behavior; links actors to roles, components to functions |
| Realization | Dashed line + hollow triangle | Logical-to-physical mapping; cross-layer implementation |
| Relationship | Notation | Usage |
|---|---|---|
| Serving | Solid line + open arrowhead | Service delivery; arrow points toward consumer |
| Access | Dotted line + optional arrowhead | Data access; use mode indicators (r, w, rw) |
| Influence | Dashed line + open arrowhead | Affects motivation elements; can include +/- strength |
| Association | Solid line (undirected/directed) | Generic relationship; use when no specific type applies |
| Relationship | Notation | Usage |
|---|---|---|
| Triggering | Solid line + filled arrowhead | Temporal/causal precedence between behaviors |
| Flow | Dashed line + filled arrowhead | Transfer of objects between behaviors; label what flows |
| Relationship | Notation | Usage |
|---|---|---|
| Specialization | Solid line + hollow triangle | Type hierarchies; same-type elements only |
ArchiMate relationships consistently point toward enterprise goals and results:
Supporting:
[Application Service] → [serves] → [Business Process/Function]
[Application Interface] → [serves] → [Business Role]
Realizing:
[Application Process/Function] → [realizes] → [Business Process/Function]
[Data Object] → [realizes] → [Business Object]
Supporting:
[Technology Service] → [serves] → [Application Component/Function]
Realizing:
[Artifact] → [realizes] → [Application Component]
[Artifact] → [realizes] → [Data Object]
The canonical layered view shows service chains connecting layers:
[Business Actor: Customer]
↓ served by
[Business Service]
↓ realized by
[Business Process]
↓ served by
[Application Service]
↓ realized by
[Application Component]
↓ served by
[Technology Service]
↓ realized by
[Node: Device + System Software]
[Business Actor] → [assignment] → [Business Role] → [assignment] → [Business Process/Function]
[Business Role] → [assignment] → [Business Process] → [realization] → [Business Service]
[Business Interface] → [assignment] → [Business Service]
[Application Component] ← [realized by] ← [Artifact] → [assigned to] → [Node/System Software]
| Want to show... | Use |
|---|---|
| What performs behavior | Assignment |
| What implements/realizes something | Realization |
| What provides service to whom | Serving |
| What reads/writes data | Access (with r/w/rw) |
| What causes what to happen | Triggering |
| What passes between behaviors | Flow (label it) |
| Part-whole (dependent) | Composition |
| Part-whole (independent) | Aggregation |
| Type hierarchy | Specialization |
| Motivation impact | Influence (+/-) |
| Generic connection | Association (last resort) |
[Source Element] → [relationship type] → [Target Element]
[Application Function: Process Order] → [access (rw)] → [Data Object: Order Record]
[Business Process: Receive Order] → [flow: Order Data] → [Business Process: Validate Order]
For detailed relationship patterns and advanced cross-layer guidance:
references/relationship-patterns.md - Complete relationship pattern catalog with examples