Cameo Inter-Op

Overview

Exporting to Rhapsody

Importing a Rhapsody UML Model

Exporting to System Architect

Importing a System Architect Encyclopedia

Importin a System Architect DoDAF2 Encyclopedia

Exporting to Cameo Data Modeler

Exporting to InfoSphere Data Architect

Exporting to ERwin

Overview

Cameo Inter-Op provides the capability to exchange data between MagicDraw® and other tools. Using Cameo Inter-Op, you can exchange models between:

MagicDraw and IBM Rational® Rhapsody®
MagicDraw and IBM Rational® System Architect®

Cameo Inter-Op is a joint effort of No Magic (www.nomagic.com) and SODIUS (www.sodius.com).

System Requirements

Java 6 or higher
Windows Operating System, Apple Mac OS X or Linux
MagicDraw 17.0.5
MagicDraw UPDM plugin, if you intend to exchange data with System Architect.
IBM Rational Rhapsody 7.6.1 or higher
IBM Rational System Architect 10.4 or higher

Exporting to Rhapsody

Overview

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.

Execution

To export MagicDraw data:

Open a UML Project in Rhapsody. This project is assumed to be empty by the time you run the export.
In the Cameo Inter-Op Services view, select the service Export from MagicDraw > MagicDraw to Rhapsody.
Right-click Run...
In the Service wizard dialog, select the Rhapsody Installation Location, and click Next.
Select the source MagicDraw .mdxml file, and click Finish.

Note: The Rhapsody Installation Location is required to call in batch mode the Rhapsody XMI Toolkit.

Scope

The semantic data handled by the export is what is covered by the Rhapsody XMI Toolkit.
MagicDraw SysML profile is mapped to Rhapsody one
Diagrams are partially preserved during the export.

Note : To export a SysML MagicDraw project to Rhapsody, it is necessary to create a SysML project into Rhapsody

Known limitations

Refer to the Rhapsody XMI Toolkit user manual for known limitations of the toolkit.
Other MagicDraw profiles (than the SysML one) are imported as is in Rhapsody. There is for example no specific conversion from MagicDraw UPDM profile to Rhapsody UPDM profile.

Importing a Rhapsody UML Model

Overview

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.

System Requirements

Windows Operating System

Execution

To import Rhapsody data:

Open a UML Project in Rhapsody.
In the Cameo Inter-Op Services view, select the service Import into MagicDraw > Rhapsody to MagicDraw.
Right-click Run...
In the Service wizard dialog, select the Rhapsody Installation Location, and click Next.
Select the target MagicDraw .mdxml file to create, where to write the converted data, and click Finish.
Open the created .mdxml file into MagicDraw.

Note: The Rhapsody Installation Location is required to call in batch mode the Rhapsody XMI Toolkit.

Scope

All semantic data covered by the Rhapsody XMI Toolkit is imported into MagicDraw.
Rhapsody SysML profile is mapped to MagicDraw one.
Diagrams are preserved during the import.

Known limitations

Refer to the Rhapsody XMI Toolkit user manual for known limitations of the toolkit.
Rhapsody profiles are imported as is in MagicDraw. There is for example no specific conversion from Rhapsody UPDM profile to MagicDraw UPDM profile. The only exception is SysML, for which a mapping has been implemented.

Exporting to System Architect

Overview

Cameo Inter-Op enables to convert a MagicDraw UPDM/DoDAF 2.0 model into a System Architect DoDAF 1.5 Encyclopedia, including diagram information.

System Requirements

Windows Operating System

Execution

To export MagicDraw DoDAF data:

In the Cameo Inter-Op Services view, select the service Export from MagicDraw > MagicDraw to System Architect.
Right-click Run...
In the Service wizard dialog, select the source MagicDraw .mdxml file, containing a UPDM/DoDAF 2.0 model, and click Next.
Select the System Architect Encyclopedia you want to update.
There are two possible connections to update an Encyclopedia:
- Current Encyclopedia
  The current Encyclopedia in the running System Architect application will be used.
  This Encyclopedia is assumed to be empty by the time you run the export.
  This is the recommended and most intuitive choice.
- XML File
  You can reference an XML file, where to write Encyclopedia data.
  This XML file can then be manually imported into System Architect.
  This enables a disconnected export, that doesn't require System Architect to be installed on the same desktop where Cameo Inter-Op is executed.

Scope

Here are the supported DoDAF views graphically:

Capability Views

CV-2
CV-4

Operational Views:
- OV-2
- OV-3 Report
- OV-4
- OV-5
- OV-6a (mapped to a MagicDraw OV-6b)
- OV-6b
- OV-6c
- OV-7
System Views:
- SV-1
- SV-2
- SV-4
- SV-5 Report
- SV-10b
- SV-10c
- SV-11

Diagrams are partially preserved during the export.

BPMN diagrams are also transformed to OV-5 views.

All the elements in the System Architect model are mapped to a corresponding element in MagicDraw.

Known limitations

MagicDraw UPDM/MoDAF is not supported.

Importing a System Architect Encyclopedia

Overview

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.

System Requirements

Windows Operating System

Execution

To import System Architect data:

In the Cameo Inter-Op Services view, select the service Import into MagicDraw > System Architect to MagicDraw.
Right-click Run...
In the Service wizard dialog, select the System Architect Encyclopedia you want to import, and click Next.
There are two possible connections to import an Encyclopedia:
- Current Encyclopedia
  The current Encyclopedia in the running System Architect application will be used.
  This is the recommended and most intuitive choice.
- XML File
  You can reference an Encyclopedia exported into an XML file from System Architect.
  This enables a disconnected import, that doesn't require System Architect to be installed on the same desktop where Cameo Inter-Op is executed.
Select Import all diagrams and click Next.
Select the target MagicDraw .mdxml file to create, where to write the converted data, and click Finish.
Open the created .mdxml file into MagicDraw.

Scope

Here are the supported DoDAF views:

Operational Views:
- OV-2
- OV-3 (without diagram layout)
- OV-4
- OV-5
- OV-6a
- OV-6b
- OV-6c
- OV-7
System Views:
- SV-1
- SV-2
- SV-4
- SV-5 Report
- SV-10b
- SV-10c
- SV-11

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.

Importing a System Architect DoDAF 2.0 Encyclopedia

Overview

Cameo Inter-Op enables to convert a System Architect DoDAF 2.0 Encyclopedia into a MagicDraw UPDM model, including diagram information.

System Requirements

Windows Operating System

Execution

To import System Architect data:

In the Cameo Inter-Op Services view, select the service Import into MagicDraw > System Architect DoDAF 2 to MagicDraw (UPDM 2) - SV-1.
Right-click Run...
In the Service wizard dialog, select the System Architect Encyclopedia you want to import, and click Next.
There are two possible connections to import an Encyclopedia:
- Current Encyclopedia
  The current Encyclopedia in the running System Architect application will be used.
  This is the recommended and most intuitive choice.
- XML File
  You can reference an Encyclopedia exported into an XML file from System Architect.
  This enables a disconnected import, that doesn't require System Architect to be installed on the same desktop where Cameo Inter-Op is executed.
Select the target MagicDraw .mdxml or .mdzip file to create, where to write the converted data.
Open the created .mdxml/.mdzip file into MagicDraw.

Scope

Here are the supported DoDAF views:

System Views:
- SV-1

All the elements in the System Architect model are mapped to a corresponding element in MagicDraw.

Diagrams are preserved during the import. However, some waypoints issues can be observed.

Exporting to Cameo Data Modeler

Overview

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.

Execution

To export MagicDraw data:

In the Cameo Inter-Op Services view, select the service Export from MagicDraw > MagicDraw to Cameo Data Modeler.
Right-click Run...
Select the source MagicDraw .mdxml file, and click Next.
Select the target Cameo Data Modeler .mdxml file, and click Finish.

Scope

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.

Exporting to InfoSphere Data Architect

Overview

Cameo Inter-Op enables to convert a Cameo Data Modeler model to an IBM InfoSphere Data Architect model, including diagram information.

Execution

To export Cameo Data Modeler data:

In the Cameo Inter-Op Services view, select the service Export from MagicDraw > Cameo Data Modeler to InfoSphere Data Architect.
Right-click Run...
Select the source Cameo Data Modeler .mdxml file, and click Next.
Select the target InfoSphere Data Architect .ldm file, and click Finish.

Scope

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. If the Property type is a DataType (primitive or enumeration), the type name is copied as is in the IDA model. If the Property type is an <<Entity>> Class, the IDA type name is the one of the referenced Entity primary key attribute.
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. Its name is fixed to "Generalization". The Generalization "Transform As" value is left untouched to its default value, i.e. "Separate Table". Each <<PrimaryKey>> Property defined in the super type is copied as an Attribute in the IDA subtype. These attributes are referenced by a ForeignKey created in the IDA subtype.
Relation	Each navigable CDM Role becomes an IDA Relation. Its name is the name of the CDM Association The relation type is always set to "Non-Identiying" and "Optional". The Relation Parent references the PrimaryKey of the CDM role type. A Foreign Key is created in the IDA owning Entity. Its name is fixed to "ForeignKey" followed by an int counter to ensure name uniqueness in the scope of the owning Entity. This Foreign Key is used as the Child of the Relation. The Foreign Key references the IDA Attribute corresponding to the CDM Role.

Exporting to ERwin

Overview

Cameo Inter-Op enables the conversion of a Cameo Data Modeler model to an ERwin model, including diagram information. The exported file is compatible with the ERwin XML format.

Execution

To export Cameo Data Modeler data:

In the Cameo Inter-Op Services view, select the service Export from MagicDraw > Cameo Data Modeler to ERwin.
Right-click Run...
Select the source Cameo Data Modeler .mdxml file, and click Next.
Select the target ERwin .xml file, and click Finish.

Scope

This section briefly outlines the rules to convert a Cameo Data Modeler (CDM) file to a ERwin xml file.

Type	Description
All Elements	Names and documentation are copied as is in the Cameo Data Modeler model.
Package	Each CDM Package becomes an ERwin Subject Area.
Entity	Each CDM << Entity>> Class becomes an ERwin Entity.
Attribute	Each CDM Property owned by an <<Entity>> Class becomes an Attribute in the corresponding ERwin Entity. If the Property type is a DataType (primitive or enumeration), the type name is copied as is in the ERwin model. If the Property type is an <<Entity>> Class, the ERwin type name is the one of the referenced Entity primary key attribute.
Primary Key	If a CDM Entity has at least one <<PrimaryKey>> Property, the corresponding ERwin attribute is set as a PrimaryKey.
Enumeration	Each CDM Enumeration becomes an ERwin Domain. The ERwin Domain will contain an Constraint that bounds the values to the EnumerationLiterals.
Generalization	Each CDM Generalization becomes an ERwin subtype relation with the Parent set to the supertype, and Child set to the subtype Entity. Each <<PrimaryKey>> Property defined in the super type is copied as an Attribute in the ERwin subtype. These attributes are referenced by a ForeignKey created in the ERwin subtype.
Relation	Each CDM Role becomes an ERwin Relation. Its name is the name of the CDM Association. The relation type is always set to "Non-Identiying".