The import from ArchiMate is a technology preview.

Introduction to ArchiMate

The ArchiMate language is an open and independent modeling language for Enterprise Architecture that enables Enterprise Architects to describe, analyze, and visualize the relationships among architecture domains in an unambiguous way. The ArchiMate supports an exchange format in XML which allows model and diagram exchange between tools.

Importing ArchiMate model from open exchange file

You can import ArchiMate model to your UAF project. The allowed file format for importing is ArchiMate .xml.


To import the model from ArchiMate .xml file


  1. In the main menu, click File > Import From > ArchiMate XML File.
  2. In the open dialog, choose the ArchiMate .xml file you want to import.
  3. Click Open.
  4. In the Select Owner dialog, choose or create the owner and click OK.


After the import is completed, the notification is displayed with the import results. The imported ArchiMate elements are mapped to the UAF elements and added to your model. You can find the imported elements in the Containment tree. In the following Element mapping section, learn how the ArchiMate element are mapped to the UAF elements. 

The ArchiMate model import is a technology preview, therefore the element mapping is implemented only partially.

Element mapping

The mapping of ArchiMate 3.1 to UAF 1.1 approach is based on NATO Architecture Framework.


#ArchiMate 3.1UAF 1.1Note
1ApplicationCollaborationResourceArchitecture 
2ApplicationComponentSoftware 
3ApplicationEventResourceSignal 
4ApplicationFunctionFunction 
5ApplicationInteractionResourceArchitecture 
6ApplicationProcessFunction 
7ArtifactDataElement 
8AssignmentIsCapableToPerform 
9BusinessActorOrganization 
10BusinessInterfaceServiceInterface 
11BusinessObjectInformationElementAdditional elements or properties may be created depending on related elements.
12BusinessRoleOperationalPerformer 
13BusinessServiceServiceSpecification 
14CapabilityCapabilityAdditional elements or properties may be created depending on related elements.
15CommunicationNetworkStandard 
16CourseOfActionOperationalActivity 
17DataObjectDataElement 
18DeviceResourceArtifact 
19DistributionNetworkSystem 
20EquipmentResourceArtifact 
21FacilityResourceArtifact 
22GapRisk 
23GoalEnterpriseGoal 
24MaterialNaturalResource 
25MeaningConcern 
26NodeResourceArtifact 
27NoteInformationAdditional elements or properties may be created depending on related elements.
28PathProtocol 
29PrincipleRequirement 
30RepresentationDataElement 
31RequirementRequirement 
32ResourceOperationalPerformer 
33SystemSoftwareSoftware 
34SpecializationGeneralization 
35TechnologyCollaborationResourceArchitecture 
36TechnologyEventResourceSignal 
37TechnologyFunctionFunction 
38TechnologyInteractionResourceArchitecture 
39TechnologyProcessFunction 
40ValueStreamOperationalActivity 
41AccessFlowPropertyAdditional elements or properties may be created depending on related elements.
43AssessmentMeasurementAdditional elements or properties may be created depending on related elements.
45AssociationAssociationAdditional elements or properties may be created depending on related elements.
46CompositionAssociationAdditional elements or properties may be created depending on related elements.
47ConnectionUAF Element onto Information ->AnnotatedElementAdditional elements or properties may be created depending on related elements.
48ConstraintConstraintAdditional elements or properties may be created depending on related elements.
49DriverMeasurementAdditional elements or properties may be created depending on related elements.
51LocationActualLocationAdditional elements or properties may be created depending on related elements.
52OutcomeActualMeasurementSetAdditional elements or properties may be created depending on related elements.
53StakeholderActualOrganizationAdditional elements or properties may be created depending on related elements.