archimate-relationships

Clarify ArchiMate structural, dependency, and dynamic relationships across layers.

10|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/ThomasRohde/archi-server --skill archimate-relationships
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archimate-relationships
Source: https://github.com/ThomasRohde/archi-server/tree/main/.claude/skills/archimate-relationships
Command: npx skills add https://github.com/ThomasRohde/archi-server --skill archimate-relationships

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill clarifies ArchiMate relationships to improve modelling accuracy and consistency across diagrams, ensuring correct interpretation of relationships and patterns.

Core Features & Use Cases

  • 11 core relationships covered: structural, dependency, and dynamic categories with guidance on correct notation and usage.
  • Cross-layer patterns: practical guidance for how relationships map across business, application, and technology layers.
  • Reference materials: includes curated patterns in the references/relationship-patterns.md for deeper exploration and examples.

Quick Start

Open the references/relationship-patterns.md to explore recommended relationship patterns and examples.

Frequently Asked Questions about archimate-relationships

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the core ArchiMate relationships for enterprise architecture modeling?

The core ArchiMate relationships include 11 distinct types divided into structural, dependency, and dynamic categories to ensure accurate notation and consistent diagram interpretation across architecture layers.

How do I map cross-layer relationships between business, application, and technology layers in ArchiMate?

Cross-layer relationships in ArchiMate are mapped using specific structural and dependency connections that translate business requirements down to application services and technology infrastructure, maintaining consistency across architectural models.

When should I use structural versus dependency relationships in ArchiMate diagrams?

Structural relationships in ArchiMate model the static composition and aggregation of elements, while dependency relationships model how elements rely on each other for functionality, ensuring correct semantic interpretation of the diagram.

Do I need external modeling tools to use ArchiMate relationship patterns?

No external tooling is required to apply these ArchiMate relationship patterns; the skill provides a standalone reference file containing curated patterns and examples for direct implementation in your modeling environment.

What is the best way to ensure consistency when applying ArchiMate cross-layer patterns?

The best way to ensure consistency is by referencing curated relationship patterns that standardize how connections map across business, application, and technology layers, preventing notation errors and improving model accuracy.