Skip to main content

ArchiMate: Possible relationship types between elements

This is not an official list but in absence of official list of relationship between elements, this is an attempt to bring a base list that can be validated and updated. Following list is outcome of feedbacks from some community members and any more suggestions are most welcome:


Business Layer Relationships

ElementPossible RelationshipTarget Element
Business ActorAssignmentBusiness Role, Business Collaboration, Business Interface
Business RoleAssignmentBusiness Process, Business Function, Business Interaction, Business Event, Business Service
Business CollaborationAssignmentBusiness Interaction
Business InterfaceAssignmentBusiness Service
Business ProcessFlowBusiness Process, Business Function, Business Interaction, Business Event
TriggeringBusiness Process, Business Function, Business Interaction, Business Event
AccessBusiness Object, Contract, Representation
Business FunctionFlowBusiness Process, Business Function, Business Interaction, Business Event
TriggeringBusiness Process, Business Function, Business Interaction, Business Event
AccessBusiness Object, Contract, Representation
Business InteractionFlowBusiness Process, Business Function, Business Interaction, Business Event
TriggeringBusiness Process, Business Function, Business Interaction, Business Event
AccessBusiness Object, Contract, Representation
Business EventTriggeringBusiness Process, Business Function, Business Interaction, Business Event
Business ServiceServingBusiness Process, Business Function, Business Interaction, Business Role, Application Component
ProductAggregation/CompositionBusiness Service, Contract, Representation
ContractAssociationBusiness Object
RepresentationAssociationBusiness Object
Business ObjectAssociationBusiness Object

Application Layer Relationships

ElementPossible RelationshipTarget Element
Application ComponentAssignmentApplication Function, Application Interaction, Application Service
Aggregation/CompositionApplication Interface, Data Object
Application CollaborationAssignmentApplication Interaction
Aggregation/CompositionApplication Component, Application Interface
Application InterfaceAssignmentApplication Service
Application FunctionFlowApplication Function, Application Interaction, Application Event
TriggeringApplication Function, Application Interaction, Application Event
AccessData Object
Application InteractionFlowApplication Function, Application Interaction, Application Event
TriggeringApplication Function, Application Interaction, Application Event
AccessData Object
Application EventTriggeringApplication Function, Application Interaction, Application Event
Application ServiceServingApplication Function, Application Component, Business Role, Business Process, Business Function, Business Interaction
Data ObjectAssociationData Object

Technology Layer Relationships

ElementPossible RelationshipTarget Element
NodeAssignmentTechnology Function, Technology Process, Technology Interaction, Technology Service
Aggregation/CompositionDevice, System Software, Technology Interface
DeviceAssignmentTechnology Function, Technology Process, Technology Interaction, Technology Service
Aggregation/CompositionTechnology Interface
System SoftwareAssignmentTechnology Function, Technology Process, Technology Interaction, Technology Service
Aggregation/CompositionTechnology Interface
Technology CollaborationAssignmentTechnology Interaction
Aggregation/CompositionNode, Device, System Software, Technology Interface
Technology InterfaceAssignmentTechnology Service
Technology FunctionFlowTechnology Function, Technology Process, Technology Interaction, Technology Event
TriggeringTechnology Function, Technology Process, Technology Interaction, Technology Event
AccessArtifact
Technology ProcessFlowTechnology Function, Technology Process, Technology Interaction, Technology Event
TriggeringTechnology Function, Technology Process, Technology Interaction, Technology Event
AccessArtifact
Technology InteractionFlowTechnology Function, Technology Process, Technology Interaction, Technology Event
TriggeringTechnology Function, Technology Process, Technology Interaction, Technology Event
AccessArtifact
Technology EventTriggeringTechnology Function, Technology Process, Technology Interaction, Technology Event
Technology ServiceServingTechnology Function, Technology Process, Technology Interaction, Node, Device, System Software, Application Component, Application Function, Application Process, Application Interaction
ArtifactAssociationArtifact
Communication NetworkAggregation/CompositionPath
PathAssociationNode, Device, System Software

Cross-Layer Relationships

Source LayerPossible RelationshipTarget Layer/Element
Business LayerServingApplication Service serves Business Process, Business Function, Business Interaction, Business Role
Application LayerServingTechnology Service serves Application Component, Application Function, Application Process, Application Interaction
Technology LayerServingTechnology Service serves Application Component, Application Function, Application Process, Application Interaction

Labels:

Comments

Post a Comment

Popular posts from this blog

Example 1: ArchiMate relationship in PlantUML code to demonstrate 15 relationship types

 Following section presents 15 types of relationships in ArchiMate and PlantUML to generate the diagram. Since this code is generated by GEN-AI it may require precision on aspects other than PlantUML syntax: Diagram Plant UML Code:  @startuml '!includeurl https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/Archimate.puml ' Another way of including Archimate Library (above is commented for following) !include <archimate/Archimate> !theme archimate-standard from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes title ArchiMate Relationships Overview <style> element{     HorizontalAlignment: left;     MinimumWidth : 180;     Padding: 25; } </style> left to right direction rectangle Other {     Business_Role(Role_SeniorManager, "Senior Manager")     Business_Role(Role_Manager, "Manager") } rectangle Dynamic {     Business_Event(Event_CustomerReques...
Post a Comment
Read more

Mastering Trade-Off Analysis in System Architecture: A Strategic Guide for Architects

 In system architecture and design, balancing conflicting system qualities is both an art and a science. Trade-off analysis is a strategic evaluation process that enables architects to make informed decisions that align with business goals and technical constraints. By prioritizing essential system attributes while acknowledging inevitable compromises, architects can craft resilient and efficient solutions. This enhanced guide provides actionable insights and recommendations for architects aiming to master trade-off analysis for impactful architectural decisions. 1. Understanding Trade-Off Analysis Trade-off analysis involves identifying and evaluating the conflicting requirements and design decisions within a system. Architects must balance critical aspects like performance, scalability, cost, security, and maintainability. Since no system can be optimized for every quality simultaneously, prioritization based on project goals is essential. Actionable Insights: Define key quality ...
Post a Comment
Read more

Virtual environments in python

 Creating virtual environments is essential for isolating dependencies and ensuring consistency across different projects. Here are the main methods and tools available, along with their pros, cons, and recommendations : 1. venv (Built-in Python Virtual Environment) Overview: venv is a lightweight virtual environment module included in Python (since Python 3.3). It allows you to create isolated environments without additional dependencies. How to Use: python -m venv myenv source myenv/bin/activate # On macOS/Linux myenv\Scripts\activate # On Windows Pros: ✅ Built-in – No need to install anything extra. ✅ Lightweight – Minimal overhead compared to other tools. ✅ Works across all platforms . ✅ Good for simple projects . Cons: ❌ No dependency management – You still need pip and requirements.txt . ❌ Not as feature-rich as other tools . ❌ No package isolation per project directory (requires manual activation). Recommendation: Use venv if you need a simple, lightweight solut...
Post a Comment
Read more