Cameo Inter-Op provides the capability to exchange data between MagicDraw® and other tools. Using Cameo Inter-Op, you can exchange models between:
Cameo Inter-Op is a joint effort of No Magic (www.nomagic.com) and SODIUS (www.sodius.com).
Cameo Inter-Op enables to convert a MagicDraw model into a Rhapsody UML model, including diagram information. The Rhapsody XMI Toolkit is used to import UML data into Rhapsody.
To export MagicDraw data:
.mdxml
file, and click Finish.Note: The Rhapsody Installation Location is required to call in batch mode the Rhapsody XMI Toolkit.
Note : To export a SysML MagicDraw project to Rhapsody, it is necessary to create a SysML project into Rhapsody
Cameo Inter-Op enables to convert a Rhapsody UML model into a MagicDraw model, including diagram information. The Rhapsody XMI Toolkit is used to extract UML data from Rhapsody.
To import Rhapsody data:
.mdxml
file to create, where to write the converted data, and click Finish..mdxml
file into MagicDraw.Note: The Rhapsody Installation Location is required to call in batch mode the Rhapsody XMI Toolkit.
Cameo Inter-Op enables to convert a MagicDraw UPDM/DoDAF 2.0 model into a System Architect DoDAF 1.5 Encyclopedia, including diagram information.
To export MagicDraw DoDAF data:
.mdxml
file, containing a UPDM/DoDAF 2.0 model, and click Next.Here are the supported DoDAF views:
Diagrams are partially preserved during the export.
BPMN diagrams are also transformed to OV-5 views.
Cameo Inter-Op enables to convert a System Architect DoDAF 1.5 Encyclopedia into a MagicDraw UPDM 2.0 model, including diagram information. If there is a lot of diagrams in the System Architect model, it could take a long time to load the resulting MagicDraw model.
To import System Architect data:
.mdxml
file to create, where to write the converted data, and click Finish..mdxml
file into MagicDraw.Here are the supported DoDAF views:
Diagrams are preserved during the import. However, some waypoints issues can be observed.
BPMN diagrams are also transformed
It is possible to generate an html report listing the mapped and non-mapped elements - only available for System Architect to MagicDraw transformation.
Additional properties, on standard DoDAF elements, are ignored by default during the transformation. These custom properties can be added to corresponding MagicDraw elements using stereotypes - only available for System Architect to MagicDraw transformation.
Non-DoDAF Definitions are ignored by default during the transformation. These custom Definitions can be imported in MagicDraw using stereotyped classes - only available for System Architect to MagicDraw transformation.
Cameo Inter-Op enables to convert a MagicDraw UML model into a Cameo Data Modeler model, including diagram information. The transformation produces an Entity Relation (ER) diagram from a UML Class Diagram.
To export MagicDraw data:
.mdxml
file, and click Next..mdxml
file, and click Finish.A depth-first algorithm traverses the model structure from Model, Package to Class in order to create equivalent elements in the ER model. Models and packages are simply transferred into the new model whereas classes are turned into entities in their respective package. It is worth noting that both class names and property names are turned to title case during this process.
An integer primary key is also added if the entity is a direct sub-class of the root class InformationModelObject
.
This root class is considered the top hierarchical class from which all classese in the source model derived from.
If any class is derived into sub-classes, a discriminator is created, owned by the class, typed with an enumeration containing literals that represent the sub-classes. The discriminator is simply an attribute that specifies the entity type of the subtype being used for a particular instance.
Each association between classes creates a foreign key property in each owning class.
Those properties are stereotyped as <<FK>>
, standing for "Foreign Key"
.
Generalizations are transferred from the original model to the ER model,
linking entities in the same fashion original generalizations do.
For each class diagram in the original model, an ER diagram is created in the output model. Layout remains the same as entities are placed at the same location as their originated classes. Graphical edge creation allows the visualization of the links between elements of the model in the diagram. As for graphical nodes, graphical edges also keep the same location.
Cameo Inter-Op enables to convert a Cameo Data Modeler model to an IBM InfoSphere Data Architect model, including diagram information.
To export Cameo Data Modeler data:
.mdxml
file, and click Next..ldm
file, and click Finish.This section briefly outlines the rules to convert a Cameo Data Modeler (CDM) file to an InfoSphere Data Acrhitect (IDA) file.
Type | Description |
All Elements | Names and documentations are copied as is in the IDA model. |
Package |
Each CDM Package becomes an IDA Package. Note: if at the end of the transformation an IDA Package content is empty, this package is removed. |
Entity | Each CDM << Entity>> Class becomes an IDA Entity. |
Attribute |
Each CDM Property owned by an <<Entity>> Class becomes an Attribute in the corresponding IDA Entity.
|
Primary Key |
If a CDM Entity has at least one <<PrimaryKey>> Property,
an IDA PrimaryKey is created in the corresponding IDA Entity. Its name is fixed to "PrimaryKey". Each IDA Attribute corresponding to a <<PrimaryKey>> Property is marked as "required" and is referenced by the IDA PrimaryKey element. |
Enumeration |
Each CDM Enumeration becomes an IDA Enumeration. The IDA Enumeration will contain an EnumerationConstraint element. Its name is “EnumerationConstraint_” followed by the name of the CDM Enumeration. The EnumerationConstraint will contain a literal for each CDM enumeration literal. |
Generalization |
Each CDM Generalization becomes an IDA Generalization owned by the IDA subtype Entity. Each <<PrimaryKey>> Property defined in the super type is copied as an Attribute in the IDA subtype. |
Relation |
Each navigable CDM Role becomes an IDA Relation. A Foreign Key is created in the IDA owning Entity. |
DoDAF 2.0 |
The transformation creates DoDAF models v2.0 |
DoDAF ABM |
System Architect DoDAF ABM models are transformed to MagicDraw models Note: The ABM addons are not transformed to MagicDraw elements. |
BPMN |
System Architect BPMN diagrams are transformed to OV-5 diagrams. |
Traceability Report |
This functionnality allows the generation of a report on the transformed elements and how they have been transformed. Note: Available for System Architect to MagicDraw transformation. Note: Custom Elements are elements that have been added in the System Architect encyclopedia |
Custom Elements Traceability |
This post-process transformation creates in MagicDraw the elements that have been added by the user in the System Architect encyclopedia. Note: Available for System Architect to MagicDraw transformation. |
MagicDraw to Cameo Data Modeler |
Cameo Inter-Op enables to convert a MagicDraw UML model into a Cameo Data Modeler model, including diagram information. The transformation produces an Entity Relation (ER) diagram from a UML Class Diagram. |
Cameo Data Modeler to InfoSphere Data Architect |
Cameo Inter-Op enables to convert a Cameo Data Modeler model to an IBM InfoSphere Data Architect model, including diagram information. |