How ArchiMate Elements are mapped to the UAF 1.2 elements after the import and the mapping rules are described in the following table:
# | ArchiMate 3.1 element | UAF 1.2 | Mapping Rule | |
---|---|---|---|---|
Name | Type | |||
1 | Application Collaboration | Resource Architecture | Common Rule | |
2 | Application Component | Software | Common Rule | |
3 | Application Event | Resource Signal | Common Rule is applied if the element has no relations. The Send Signal Action is created additionally if the ArchiMate Application Event is related to Resource Process or Resource Function. Also, see Mapping issues. | |
State | The Resource State Description is created additionally if the ArchiMate Application Event is related to another Application Event and/or Junction using the Triggering relation. | |||
4 | Application Function | Function | The ArchiMate Application Function is mapped to Function if the ArchiMate Application Function is NOT related to an element that maps to UAF Resource Performer one of the following:
| |
Function + Function Action | The ArchiMate Application Function is mapped to Function + Function Action if the ArchiMate Application Function is related to an element that maps to UAF Resource Performer using one of the following:
| |||
5 | Application Interaction | Resource Architecture | Common Rule | |
6 | Application Interface | Resource Interface | Common Rule | |
7 | Application Process | Function | The ArchiMate Application Process is mapped to Function if the ArchiMate Application Function is NOT related to an element that maps to UAF Resource Performer using one of the following:
| |
Function + Function Action | The ArchiMate Application Process is mapped to Function + Function Action if the ArchiMate Application Function is related to an element that maps to UAF Resource Performer using one of the following:
| |||
8 | Application Service | Resource Artifact | Common Rule | |
9 | Artifact | Resource Information | Common Rule | |
10 | Assessment | Measurement | The ArchiMate Assessment is mapped to Measurement for Property Set if the ArchiMate Assessment element is related to the element which maps to UAF Property Set using the Association relation. | |
Measurement Set + Measurement | The ArchiMate Assessment is mapped to Measurement Set with Measurement if the ArchiMate Assessment element IS NOT related to the element which maps to UAF Property Set using the Association relation. Note. UAF Measurement Set and Measurement has the same name as the ArchiMate Assessment element. | |||
11 | Business Actor | Organization | Common Rule | |
12 | Business Collaboration | Capability Configuration | Common Rule | |
13 | Business Event | Operational Signal | Common Rule if has no relations. The Send Signal Action is created additionally if the ArchiMate Business Event is related to Business Process. Also, see Mapping issues. | |
State | The ArchiMate Business Event is mapped to State if the ArchiMate Business Event is related to another Business Event and/or Junction using the Triggering relation. Additionally:
| |||
14 | Business Function | Function | The ArchiMate Business Function is mapped to Function if the ArchiMate Business Function is NOT related to Business Service | |
Function + Function Action | The ArchiMate Business Function is mapped to Function + Function Action if the ArchiMate Business Function is NOT related to Business Service and is related to an element that maps to UAF Resource Performer using one of the following:
| |||
Service Function | The ArchiMate Business Function is mapped to Service Function if the ArchiMate Business Function is related to Business Service. | |||
Service Function + Service Function Action | The ArchiMate Business Function is mapped to Service Function + Service Function Action if the ArchiMate Business Function is related to Business Service and is related to Business Interface using Association relation. | |||
15 | Business Interaction | CapabilityConfiguration | Common Rule | |
16 | Business Interface | Service Interface | Common Rule | |
17 | Business Object | Operational Information | Common Rule | |
18 | Business Process | Operational Activity | The ArchiMate Business Process is mapped to Operational Activity if ArchiMate Business Process is NOT related to:
| |
Operational Activity + Operational Activity Action | The ArchiMate Business Process is mapped to Operational Activity + Operational Activity Action if the ArchiMate Business Process is related to:
| |||
19 | Business Role | OperationalPerformer | Common Rule | |
20 | Business Service | Service | Common Rule | |
21 | Capability | Capability | Common Rule | |
22 | Communication Network | Standard | Common Rule | |
23 | Constraint | Constraint | If ArchiMate Constraint has no relations to other elements or has any relation to Grouping, Notes, or another relation. | |
Resource Constraint | The ArchiMate Constraint is mapped to Resource Constraint if the ArchiMate Constraint has any relation to the element which maps to UAF Resource Performer, Resource Information, Actual Resource, or Function. | |||
Operational Constraint | The ArchiMate Constraint is mapped to Operational Constraint if the ArchiMate Constraint has any relation to the element which maps to UAF Operational Information, Operational Activity, Operational Exchange, Operational Performer, or Operational Signal. | |||
Strategic Constraint | The ArchiMate Constraint is mapped to Strategic Constraint if the ArchiMate Constraint has any relation to the Capability element. | |||
Service Policy | The ArchiMate Constraint is mapped to Service Policy if the ArchiMate Constraint has any relation to the Business Service element. | |||
24 | Contract | Resource Information | Common Rule | |
25 | Course Of Action | Operational Activity | Common Rule | |
26 | Data Object | Resource Information | Common Rule | |
27 | Deliverable | Actual Project Milestone | Common Rule Also, see Mapping issues. | |
28 | Device | Resource Artifact | Common Rule | |
29 | Distribution Network | System | Common Rule | |
30 | Driver | Measurement | The ArchiMate Driver is mapped to Measurement for Property Set if the ArchiMate Driver element is related to the element which maps to UAF Property Set using the Association relation. | |
Measurement Set + Measurement | The ArchiMate Driver element map to Measurement Set with Measurement if the ArchiMate Driver element IS NOT related to the element which maps to UAF Property Set using association relation. Note. UAF Measurement Set and Measurement has the same name as the ArchiMate Driver element. | |||
31 | Equipment | Resource Artifact | Common Rule | |
32 | Facility | Resource Artifact | Common Rule | |
33 | Gap | Risk | Common Rule | |
34 | Goal | Enterprise Goal | Common Rule | |
35 | Grouping | Element Group | Common Rule Note. All ArchiMate elements related to the Grouping element after importing to UAF are added as Annotated Elements for Element Group [Comment] regardless of the relations' type (ArchiMate relations are not mapped to the real UAF relations). | |
36 | Implementation Event | Actual Project Milestone | Common Rule Also, see Mapping issues. | |
37 | Junction | And Junction | Fork Node | If incoming 0 or 1 control/object flow. Shall be imported with Operational Activity. |
Join Node | If incoming 0 or 1 control/object flow. Shall be imported with Operational Activity. | |||
Pseudostate | The ArchiMate Junction is mapped to Pseudostate if the ArchiMate Junction is related to States and Transitions. The Pseudostate kind will be:
| |||
Or Junction | Decision Node | If incoming 0 or 1 control/object flow. Shall be imported with OperationalActivity. | ||
Merge Node | If incoming >1 control/object flow. Shall be imported with OperationalActivity. | |||
Pseudostate | The ArchiMate Junction is mapped to Pseudostate if the ArchiMate Junction is related to States and Transitions. The Pseudostate kind will be:
| |||
38 | Location | Actual Location | Common Rule Also, see Mapping issues. | |
39 | Material | Natural Resource | Common Rule | |
40 | Meaning | Concern | Common Rule | |
41 | Node | ResourceArtifact | Common Rule | |
42 | Note | Information | Common Rule Note. All ArchiMate elements are related to Note using Connection/Line. After import to UAF, related elements are added as Annotated Elements for the Information [Comment] element. | |
43 | Outcome | Actual Measurement Set | Common Rule Also, see Mapping issues. | |
44 | Path | Protocol | Common Rule | |
45 | Plateau | Capability Configuration | The ArchiMate Plateau is mapped to Capability Configuration if ArchiMate Plateau is NOT related to Goal using Realization relation. | |
Actual Enterprise Phase | The ArchiMate Plateau is mapped to Actual Enterprise Phase if the ArchiMate Plateau is related to Goal using Realization relation. Also, see Mapping issues. | |||
46 | Principle | Requirement | Common Rule | |
47 | Product | Resource Architecture | The ArchiMate Product is mapped to Resource Architecture if the ArchiMate Product is NOT related to Business Service. | |
Service | The ArchiMate Product is mapped to Service if ArchiMate Product is related to Business Service. | |||
48 | Representation | Resource Information | Common Rule | |
49 | Requirement | Requirement | Common Rule | |
50 | Resource | Operational Performer | Common Rule | |
51 | Stakeholder | Actual Organization | Common Rule Also, see Mapping issues. | |
52 | System Software | Software | Common Rule | |
53 | Technology Collaboration | Resource Architecture | Common Rule | |
54 | Technology Event | Resource Signal | Common Rule is applied if the ArchiMate Technology Event has no relations. The Send Signal Action is created additionally if the ArchiMate Technology Event is related to Resource Process or Resource Function. Also, see Mapping issues. | |
State | The Technology Event is mapped to State if the ArchiMate Technology Event is related to another Technology Event and/or Junction using Triggering relation. Additionally, the Resource State Description is created. | |||
55 | Technology Function | Function | The ArchiMate Technology Function is mapped to Function if the ArchiMate Technology Function is NOT related to an element that maps to UAF Resource Performer using:
| |
Function + Function Action | The ArchiMate Technology Function is mapped to Function + Function Action if the ArchiMate Technology Function is related to an element that maps to UAF Resource Performer using:
| |||
56 | Technology Interaction | Resource Architecture | Common Rule | |
57 | Technology Interface | Resource Interface | Common Rule | |
58 | Technology Process | Function | The ArchiMate Technology Process is mapped to Function if the ArchiMate Technology Process is NOT related to an element that maps to UAF Resource Performer using:
| |
Function + Function Action | The ArchiMate Technology Process is mapped to Function + Function Action if the ArchiMate Technology Process is related to an element that maps to UAF Resource Performer using:
| |||
59 | Technology Service | Resource Artifact | Common Rule Also, see Mapping issues. | |
60 | Value | Measurement | The ArchiMate Value element map to Measurement for Property Set if the ArchiMate Value element is related to the element which maps to UAF Property Set using Association relation. | |
Measurement Set + Measurement | The ArchiMate Value element map to Measurement Set with Measurement if the ArchiMate Value element IS NOT related to the element which maps to UAF Property Set using Association relation. (UAF Measurement Set and Measurement has the same name as the ArchiMate Value element). | |||
61 | Value Stream | Operational Activity | Common Rule | |
62 | Work Package | ActualProject | Common Rule Also, see Mapping issues. | |
ActualProject + ActualProjectMilestone | The ArchiMate Work Package is mapped to ActualProject + ActualProjectMilestone if the ArchiMate Work Package is related to the ArchiMate Implementation Event or Deliverable using the Triggering relationship. |
Related pages