archimate relationships
4
总安装量
0
周安装量
#51303
全站排名
安装命令
npx skills add https://github.com/thomasrohde/marketplace --skill 'ArchiMate Relationships'
Skill 文档
ArchiMate Relationships
ArchiMate defines 11 core relationships organized into four categories. Understanding proper relationship usage is critical for model quality and analysis.
Relationship Categories
Structural Relationships (Static Construction)
| 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 |
Dependency Relationships (Support/Usage)
| 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 |
Dynamic Relationships (Temporal/Flow)
| 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 |
Other
| Relationship | Notation | Usage |
|---|---|---|
| Specialization | Solid line + hollow triangle | Type hierarchies; same-type elements only |
Key Direction Principle
ArchiMate relationships consistently point toward enterprise goals and results:
- From Technology â Application â Business
- From Active Structure â Behavior â Passive Structure
Cross-Layer Relationship Patterns
Business â Application
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]
Application â Technology
Supporting:
[Technology Service] â [serves] â [Application Component/Function]
Realizing:
[Artifact] â [realizes] â [Application Component]
[Artifact] â [realizes] â [Data Object]
Service-Driven Architecture Pattern
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]
Common Relationship Patterns
Actor-Role-Function Pattern
[Business Actor] â [assignment] â [Business Role] â [assignment] â [Business Process/Function]
Service Realization Pattern
[Business Role] â [assignment] â [Business Process] â [realization] â [Business Service]
[Business Interface] â [assignment] â [Business Service]
Deployment Pattern
[Application Component] â [realized by] â [Artifact] â [assigned to] â [Node/System Software]
Relationship Selection Guide
| 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) |
Output Format for Relationships
Notation Format
[Source Element] â [relationship type] â [Target Element]
With Access Modes
[Application Function: Process Order] â [access (rw)] â [Data Object: Order Record]
With Flow Labels
[Business Process: Receive Order] â [flow: Order Data] â [Business Process: Validate Order]
Additional Resources
Reference Files
For detailed relationship patterns and advanced cross-layer guidance:
references/relationship-patterns.md– Complete relationship pattern catalog with examples