To import models from Enterprise Architect (EA), you must have access to an EA project file. You do not need to have EA installed on your local computer to import or update models.
The imported EA project should contain only one model for import. If there are multiple models, medini analyze chooses one of them arbitrarily.
Only elements of structural models, such as class models or component models, can be imported into medini analyze. Any other elements in the source model are ignored. For more information, see Concepts Supported During Import.
Ansys medini analyze supports the following Enterprise Architect file formats:
EAP
EAPX
GEA
GEAX
Note: Model import is independent of the file format. If, for example, an EAPX file is converted to QEAX in a later version of EA, the imported result is the same.
To import a model from EA, complete these steps:
In medini analyze, in the model browser, navigate to your project and right-click a package that supports system design.
From the context menu, select > .
Complete the steps in the import wizard.
To import EA diagram images in addition to EA models, you must have EA installed on the same machine as medini analyze. If EA is not found on the system, the option to import diagrams is disabled.
If you are using a server license, you must start EA and connect to the license server before performing an import into medini analyze. Note that EA and Ansys medini analyze do not have to be running at the same time.
Diagram import capabilities depend on the EA tool installation. Beginning with EA version 16, the EAP/EAPX file format is no longer supported. The following table describes the limitations when importing diagrams for each supported EA version:
Table 15.4:
| Installed Version | Diagram Import |
|---|---|
| No EA installed | You cannot import diagrams. |
| EA prior to version 16 | You can only import diagrams from EAP/EAPX model files but not from QEA/QEAX files. A warning appears if you try to select a format that is not supported. |
| EA version 16 or later, 64-bit version | Since there is no support for EAP/EAPX in this version, diagram import is only supported for QEA/QEAX files. |
| EA version 16 or later, 32-bit version | For this version of EA, medini analyze supports diagram import from both EAP/EAPX and QEA/QEAX files. |
Below, we list some additional details about mapping Enterprise Architect.
Views
Views are mapped to a package in medini analyze. Notes of the views in EA are mapped to the description attribute in medini analyze.
Packages
Packages are imported and mapped to packages in medini analyze. Containment is preserved. Notes of the package in EA are mapped to the description attribute in medini analyze.
Classes/Components
Classes and components are mapped to types in medini analyze. The specific category, such as Sensor Type, Actuator Type, or Controller Type, is not set by the import. Notes in EA are mapped to the description attribute in medini analyze. Containment is set accordingly.
Parts/Objects
Parts and objects are mapped to instances in medini analyze. The specific category, such as Sensor, Actuator, or Controller, is not set by the import. Notes in EA are mapped to the description attribute in medini analyze. Containment is set accordingly. The relation to a type (if specified in EA) is set in medini analyze.
Ports
Ports of classes/components and parts/objects in EA are mapped to ports of types/instances in medini analyze. The default direction of the port in medini analyze is "inout". If SysML is used in EA, the native "Direction" property is used to import the direction of the port. Otherwise a tagged value with the name "direction" can be used. Valid values are "in", "inout" or "out". Notes in EA are mapped to the description attribute in medini analyze. Type information is provided as a string in the type property.
Connectors
Connectors between parts/objects and ports are imported into the medini analyze model and mapped to connectors. Notes in EA are mapped to the description attribute in medini analyze.
In addition to the mentioned concepts of structural models, elements of behavioral models (namely activities) are also imported from EA:
Activities
Activities in the EA model are imported and mapped to activities in the medini analyze model. Containment is set accordingly. Stereotype information is mapped. Notes in EA are mapped to the description attribute in medini analyze.
Structured Activities
Structured Activities in the EA model are imported and mapped to structured activities in the medini analyze model. Containment is set accordingly. Stereotype information is mapped. Notes in EA are mapped to the description attribute in medini analyze.
Actions
Actions in the EA model are imported and mapped to actions in the medini analyze model. The specific kind of an action is imported as a stereotype in medini analyze, for example, <<CallOperation>>. Containment is set accordingly. Stereotype information is mapped. Notes in EA are mapped to the description attribute in medini analyze.
Control/data flow
Control and data flow are imported to control and data flow in medini analyze. Furthermore, the concepts initial node, end nodes, decision/merge, fork/join as well as pins of structured activities and activities are imported to corresponding medini analyze concepts. Containment is set accordingly. Notes in EA are mapped to the description attribute in medini analyze. Type information is provided in the type property of the pins and objects as a string.
Note, there are some specifics in the mapping of activities:
Activity parameters and any relations among activities are not imported. Activities should be used as the top-level containers for a detailed behavior model using actions. If a relation among activities should be modeled, a new activity containing child activities with this relationship can be provided and imported.
In medini analyze, an activity itself must be the top-level concept. Activities can be shown on diagrams of the System/Function Model, which are also used to visualize structural elements such as types and instances. Other concepts of an activity model, such as actions, pins, control flows, or initial nodes, have to be contained in an activity to be shown on an activity details diagram of the containing activity.
Other structuring concepts, such as swimlanes, are mapped to structured activities in the medini analyze model.
Note the following constraints when importing models from EA.
Port may only have multiplicity "1"
Part must have a block as a type
Part must have a multiplicity "1"
Port Usage may only have one incoming or outgoing connector
Connector may only connect two port usages or two parts
Directions of two connected port usages must match
Connector ends must have multiplicity "1"
Names must be unique in same namespace