Relations Matrix & ArchiMate Connectors
In enterprise architecture, relationships are not arbitrary visual lines; they are strongly-typed semantic connectors governing traceability between business strategy and physical IT infrastructure.
EasyEA guarantees complete adherence to the ArchiMate 3.x specification while providing the Relations Matrix (RelationsMatrix) to audit cross-layer dependencies at enterprise scale.
1. Supported ArchiMate 3.x Relationship Types
EasyEA natively implements The Open Groupโs formal relationship types:
| Category | Relationship Type | Visual Connector | Formal Semantic Purpose |
|---|---|---|---|
| Structural | Composition | Whole โโโโ Part | Strong ownership: an element consists entirely of constituent parts. |
| Structural | Aggregation | Whole โโโโ Part | Conceptually groups related architectural elements. |
| Structural | Assignment | Actor โโโ Role | Allocates an active structure to a behavioral role or function. |
| Structural | Realization | Component โโโท Service | Concrete physical or logical entities realize abstract services/capabilities. |
| Dependency | Serving | Service โโโท Process | A capability, application, or tech service serves an active consumer. |
| Dependency | Access | Process โโโ Data Object | Read, write, create, or delete operations on data or business objects. |
| Dependency | Influence | Requirement โโท Goal | Positive (+) or negative (-) impact on architectural drivers or goals. |
| Dynamic | Triggering | Step 1 โโโโท Step 2 | Temporal or sequential causal transition between behaviors. |
| Dynamic | Flow | System A โโท System B | Information, physical matter, or energy transfer between elements. |
| Other | Association | Asset A โโโ Asset B | Generic semantic connection without specific dependency semantics. |
2. Metamodel Semantic Validation Engine
Whenever an architect establishes a relationship (in the web modeler, via Schema-as-Code, or through desktop plugins), EasyEA checks the validity of the tuple (Source, Relationship, Target) against official ArchiMate 3.x derivation rules.
Connecting an unaligned physical node directly to a business process without intermediate layers is flagged, with EasyEA suggesting the canonical realization path:
Node โ SystemSoftware โ ApplicationComponent โ ApplicationService โ BusinessProcess
3. The Interactive Relations Matrix (RelationsMatrix)
The Relations Matrix allows teams to spot unserved processes or orphaned applications in seconds:
graph TD subgraph Setup["Matrix Axis Configuration"] R[Rows: BusinessProcess] C[Columns: ApplicationComponent] end Setup --> Grid["N x M Dynamic Matrix"] Grid --> Inspect["Direct In-Cell Inspection / Creation / Deletion"]- Configure Axes:
- Assign source element types to Rows (e.g.,
BusinessCapabilityorBusinessProcess). - Assign target element types to Columns (e.g.,
ApplicationComponent).
- Assign source element types to Rows (e.g.,
- Matrix Rendering:
- Populated cells display the relationship type icon (
Serving,Realization, etc.). - Empty cells highlight gaps where no integration or alignment exists.
- Populated cells display the relationship type icon (
- 1-Click In-Grid Editing:
- Click any empty cell to create a validated relationship instantly.
- Click any active relationship cell to inspect properties, reverse directions, or delete the link.