On this page

In addition to UML data, each EA-exported XMI contains EA-specific information. The Enterprise Architect Import Plugin can transform this particular information into UML elements with the stereotypes applied if you include EA-specific data before importing the XMI file. This data includes:

  • Constraints: name, description, type, weight, and status.
  • Requirements: name, description, type, status, difficulty, priority, and last update.
  • Scenarios: name, description, type, and weight.
  • Files: file path type.
  • Requirements (External): type, status, difficulty, priority, last update, created, and note.
  • Changes: type, status, difficulty, priority, last update, created, and note.
  • Issues: type, status, difficulty, priority, last update, created, and note.

Note

You can access and specify the EA information in the Property dialog in EA.

           

To include EA-specific data in the transformation process, the plugin creates a set of stereotypes and tag definitions as the EA Profile.

The EA Profile in a treeview.

Constraints

Each EA constraint will be transformed into a UML constraint and <<EAConstraint>> will be applied to the constraint. The properties of an EA constraint will be mapped either to the properties of a UML constraint or to the tag values of <<EAConstraint>>. The following table shows the constraint mapping details.

EAMagicDraw
nameThe name property of a UML constraint.
descriptionEAConstraint::type tag value.
typeEAConstraint::weight tag value.
weightEAConstraint::status tag value.
constraint ownerConstrained Element property point to the constraint owner.

Requirements

Each EA Requirement will be transformed into a UML Class. Because a Requirement cannot be created in an element that is the owner of a Class in EA, the transformed Requirement will be kept in a separate Package, named EA Requirement. A Realization will then be created from the owner of the Requirement into a transformed Requirement. See the following table for details.

EAMagicDraw
nameEARequirement :: name tag value
descriptionEARequirement :: description tag value
typeEARequirement :: type tag value
statusEARequirement :: status tag value
difficultyEARequirement :: difficulty tag value
priorityEARequirement :: priority tag value
last updateEARequirement :: name update value

Scenarios

Each EA scenario will be transformed into a UML Comment and <<EAScenario>> will be applied to the comment. The properties of a scenario will be mapped either to the properties of each UML Comment or to the tag values of <<EAScenario>>. See the following table for details.

EAMagicDraw
nameEAScenario::name tag value
descriptionThe Body property of a UML Comment. 
typeEAScenario :: type tag value
weightEARequirement :: weight tag value
subjectAn annotated Element property pointing to an EA subject element.

Files

EA can add files to a UML element. The information will be transformed into a Hyperlink in MagicDraw.

EAMagicDraw
Local fileFile
Web addressWebpage. 

Requirements (external)

An EA-created Requirement differs from the one you create as an internal element for each element. EA Requirements will appear in the Project Browser and can be pasted on a diagram. Each EA Requirement will be transformed into a Class and <<EARequirement>> will be applied to the Requirement.

EAMagicDraw
typeEARequirement :: type tag value
statusEARequirement :: status tag value
difficultyEARequirement :: difficulty tag value
priorityEARequirement :: priority tag value
last updateEARequirement :: last update value
createdEARequirement :: created tag value
noteDocumentation

Changes

EA can create a Change and will export it as a Class. The Class information will be transformed into the <<EAChange>> tag values. See the following table for details.

EAMagicDraw
typeEAChange :: type tag value
statusEAChange :: status tag value
difficultyEAChange :: difficulty tag value
priorityEAChange :: priority tag value
last updateEAChange :: last update value
createdEAChange :: created tag value
noteDocumentation

Issues

EA can create an Issue and will export it as a Class. The Issue information will be transformed into the <<EAIssue>> tag values. See the following table for details.

EAMagicDraw
typeEAIssue :: type tag value
statusEAIssue :: status tag value
difficultyEAIssue :: difficulty tag value
priorityEAIssue :: priority tag value
last updateEAIssue :: last update value
createdEAIssue :: created tag value
noteDocumentation