How ArchiMate relationships are mapped to the UAF 1.2 relationships or added to UAF element properties after the import and the mapping rules are described in the following table:
| # | ArchiMate 3.1 relation | UAF 1.2 | Mapping Rule | |
|---|---|---|---|---|
| Name | Type | |||
| 1 | Access | Read Write Access Read/Write | Flow Property | The ArchiMate Access is mapped to UAF Flow Property which is applied to Interface when the ArchiMate Access relation is used to relate the ArchiMate element to Business Interface/Technology Interface/Application Interface. Access Type is set as the direction for Flow Property: Read - in, Write - out, Access - inout, ReadWrite - inout. Also, see Mapping issues. |
| Dependency | The ArchiMate Access is mapped to UAF Dependency if no other ArchiMate Access relation import and mapping rule applies. | |||
| 2 | Aggregation | Association | Common Rule Common Rule - after the import to UAF maps to Aggregation (Association with Aggregation = Shared) | |
| Physical Location property | The Location information is added to the UAF Physical Location element property if the ArchiMate Aggregation relates the Actual Location to the Location Holder (i.e. Operational Performer, Resource Performer). No relation is created in UAF. | |||
| Link | The ArchiMate Aggregation is mapped to UAF Link [InstanceSpecification] if the ArchiMate Aggregation relates elements that map to the Instance Specifications with the same type. | |||
| Trace | The ArchiMate Aggregation is mapped to UAF Trace if the ArchiMate Aggregation relates ArchiMate elements (Goal, Requirement, Principle) which map to UAF Enterprise Goal or Requirement elements. | |||
| Dependency | The ArchiMate Aggregation is mapped to UAF Dependency if no other ArchiMate Aggregation relation import and mapping rule applies. | |||
| 3 | Assignment | Is Capable To Perform | The ArchiMate Assignment is mapped to UAF Is Capable To Perform if the ArchiMate Assignment relates the ArchiMate elements that map to UAF Operational Performer and Operational Activity or Resource Performer and Function. | |
| Resource Port | The ArchiMate Assignment is mapped to UAF Resource Port when Application Interface/Technology Interface is assigned to Application Service/Technology Interface. Also, see Mapping issues. | |||
| Service Port | The ArchiMate Assignment is mapped to UAF Service Port if Business Interface is assigned to Business Service. Also, see Mapping issues. | |||
| Dependency | The ArchiMate Assignment is mapped to UAF Dependency if no other ArchiMate Assignment relation import and mapping rule applies. | |||
| 4 | Association | isDirected=true | Association | The ArchiMate Association is mapped to the UAF Association with the navigable end (the source and target are the same as in ArchiMate) |
| isDirected=False | The ArchiMate Association is mapped to the UAF Association without the navigable end (the source and target are the same as in ArchiMate) | |||
| Is Capable To Perform | The ArchiMate Association is mapped to the UAF Is Capable To Perform relation if ArchiMate Resource is related to Business Process. | |||
| Link | The ArchiMate Association is mapped to UAF Link [InstanceSpecification] if the ArchiMate Association relates elements that map to the Instance Specifications with the same type. | |||
| Actual Project Milestone Role | The ArchiMate Association is mapped to the UAF Actual Project Milestone Role [Slot] when the ArchiMAte Association relates Workpackage to Deliverable/Implementation Event. | |||
| Trace | The ArchiMate Association is mapped to the UAF Trace if the ArchiMate Association relates ArchiMate elements (Goal, Requirement, Principle) which map to UAF Enterprise Goal or Requirement elements. | |||
| Dependency | The ArchiMate Association is mapped to UAF Dependency if no other ArchiMate Association relation import and mapping rule applies. | |||
| 5 | Composition | Association | Common Rule - after import to UAF maps to Composition (Association with Aggregation = Composite) | |
| Containment | The ArchiMate Composition is mapped to UAF Containment if the ArchiMate Composition relates ArchiMate elements (Goal, Requirement, Principle) which map to UAF Enterprise Goal or Requirement elements. Also, see Mapping issues. | |||
| Slot | If ArchiMate Composition relate elements that in UAF become Actual Measurement Sets, then in UAF Composition relation is not created, but "main" Actual Measurement Set is created as owner which owns "inner" Actual Measurement Sets (owner with slot subMeasurementType and values for this slot are created) | |||
| 6 | Connection (Line) | UAF Element onto Information → Annotated Element | The ArchiMate Connection/Line/Anchor information is added to the Annotated Element property of the UAF Information element. | |
| 7 | Flow | Operational Exchange | The ArchiMate Flow is mapped to UAF Operational Exchange if the ArchiMate Flow relates UAF elements from the Operational Domain. | |
| Resource Exchange | The ArchiMate Flow is mapped to UAF Resource Exchange if the ArchiMate Flow relates UAF elements from the Resource Domain. | |||
| Service Exchange | The ArchiMate Flow is mapped to UAF Service Exchange if the ArchiMate Flow relates UAF Service elements. | |||
| Operational Control Flow | The ArchiMate Flow is mapped to UAF Operational Control Flow if the ArchiMate Flow relates Business Processes that map to Operational Activity + Operational Activity Action. | |||
| Function Control Flow | The ArchiMate Flow is mapped to UAF Function Contro Flow if the ArchiMate Flow relates Technology Process, Technology Function, Application Process, Application Function, or Business Function that maps to Function + FunctionAction. | |||
Dependency | The ArchiMate Flow is mapped to UAF Dependency if the ArchiMate Flow relation does not map to Resource Exchange or Operational Exchange. | |||
| 8 | Influence | Dependency | Common rule, but ArchiMate name and strength map to UAF Dependency name ("name strength"). | |
| 9 | Realization | Phases | The ArchiMate Realization is mapped to UAF Phases if the ArchiMate Realization relates ArchiMate Plateau (which maps to UAF Actual Enterprise Phase) with Capability or Goal. | |
| Exhibits | The ArchiMate Realization is mapped to UAF Exhibits if the Archimate Realization relates ArchiMate Workpackage or BusinessService with Capability. | |||
| Maps To Capability | The ArchiMate Realization is mapped to UAF Maps To Capability if the ArchiMate Realization relates ArchiMate Business Process with Capability. | |||
| Is Capable To Perform | The ArchiMate Realization is mapped to UAF Is Capable To Perform if the ArchiMate Realization relates:
| |||
| Constrained Element | The ArchiMate Realization information is added into the Constrained Element property of the UAF Constraint if the ArchiMatre Realization relates ArchiMate Constraint with any other element. No relations are created. | |||
| Desires | The ArchiMate Realization is mapped to UAF Desires if the ArchiMate Realization relates ArchiMate Capability with Outcome. | |||
| Satisfy | The ArchiMate Realization is mapped to UAF Satisfy if the ArchiMate Realization relates ArchiMate Outcome with Goal. | |||
| Composition | The ArchiMate Realization is mapped to UAF Composition if the ArchiMate Realization relates:
| |||
| Implements | The ArchiMate Realization is mapped to UAF Implements if the ArchiMate Realization relates ArchiMate Business Actor, Equipment, Plateau to Resource or Business Role. | |||
| Version Released | The ArchiMate Realization information is added to UAF Version Released tag if the ArchiMate Realization relates ArchiMate Workpackage (which maps to UAF Actual Project and Actual Project Milestone) to Plateau (which maps to UAF Capability Configuration) or Business Service. No relationship is created. | |||
| Annotated Element | The ArchiMate Realization information is added to the UAF Annotated Element tag if the ArchiMate Realization relates ArchiMate Plateau (which maps to UAF Capability Configuration) to Grouping. No relationship is created. | |||
| Dependency | The ArchiMate Realization is mapped to UAF Dependency if no other ArchiMate Realization relation import and mapping rule applies. | |||
| 10 | Serving | Dependency | The ArchiMate Serving is mapped to UAF Dependency if no other ArchiMate Serving relation import and mapping rule applies. | |
| Supports | The ArchiMate Serving is mapped to UAF Supports if ArchiMate Business Service is related to Business Process using the ArchiMate Serving relation (UAF Service supports Operational Activity). | |||
| 11 | Specialization | Generalization | Common rule | |
| Containment | The ArchiMate Specialization is mapped to UAF Containment if the ArchiMate Specialization relation is between Requirements, Goals, and Principles. Also, see Mapping issues. | |||
| Dependency | The ArchiMate Specialization is mapped to UAF Dependency if no other ArchiMate Specialization relation import and mapping rule applies. | |||
| 12 | Triggering | Operational Exchange | The ArchiMate Triggering is mapped to UAF Operational Exchange when the ArchiMate Triggering is related to Operational Performers. | |
| Resource Exchange | The ArchiMate Triggering is mapped to UAF Resource Exchange when the ArchiMate Triggering is related to Resources. | |||
| Service Exchange | The ArchiMate Triggering is mapped to UAF Service Exchange when the Archimate Triggering is related to Services. | |||
| Operational Control Flow | The ArchiMate Triggering is mapped to UAF Operational Control Flow when the ArchiMate Triggering is related to Operational Activity Actions. | |||
| Function Control Flow | The ArchiMate Triggering is mapped to UAF Function Control Flow when the ArchiMate Triggering is related to Function Actions. | |||
| Service Control Flow | The ArchiMate Triggering is mapped to UAF Service Control Flow when the ArchiMate Triggering is related to Service Function Actions. | |||
| Project Sequence | The ArchiMate Triggering is mapped to UAF Project Sequence when the ArchiMate Triggering is related to Actual Projects. | |||
| Milestone Dependency | The ArchiMate Triggering is mapped to UAF Milestone Dependency when the ArchiMate Triggering is related to Actual Project Milestones. | |||
| Transition | The ArchiMate Triggering is mapped to UAF Transition when the ArchiMate Triggering is related to States. | |||
| Dependency | The ArchiMate Triggering is mapped to UAF Dependency if no other ArchiMate Triggering relation import and mapping rule applies. | |||
Related pages