XMI is the XML-based model interchange format you use when you need to move a UML model between MDriven Designer and another tool that supports the same XMI version.

Supported XMI version

MDriven Designer supports XMI 2.4.2 for XMI import and export.

When another tool offers several UML or XMI export formats, configure it to export:

Setting	Required value
UML version	UML 2.4.1
XMI version	XMI 2.4.2

Do not use another XMI version for interchange with MDriven Designer. An XMI file that is valid for a different XMI version is not necessarily importable by MDriven Designer.

Use XMI to exchange a model

Use XMI when you want to exchange model structure with another modeling tool. A typical workflow is:

1. Create or obtain the model in the external tool.
2. Clean up the model so that it contains the UML classes you intend to use in MDriven Designer.
3. Export the model as XML using UML 2.4.1 and XMI 2.4.2.
4. Import the XMI file into MDriven Designer.
5. Review the imported classes and continue modeling in MDriven Designer.

For example, you can use Sparx to import a schema into a UML model, remove imported elements that you do not need, export the remaining classes as XMI 2.4.2, and then import that file into MDriven Designer.

Prepare the model before export

External tools can create intermediary or tool-specific elements during an import. Review the model before you export it to XMI.

• Keep the classes that represent the model you want to work with.
• Remove unwanted elements introduced by the external tool.
• Confirm that the external tool exports using UML 2.4.1 and XMI 2.4.2.

Cleaning the model before interchange makes the imported MDriven model easier to understand and work with.

Importing a web-service or REST interface

MDriven Designer cannot import an XSD or WSDL directly. If your starting point is a web-service or REST interface definition, use a tool such as Sparx to import the schema and export the resulting UML model as XMI 2.4.2. You can then import that XMI into MDriven Designer.

See Documentation:Importing web service interface as model for this workflow and its preparation guidance.

Scope of XMI interchange

XMI is for exchanging a model with another modeling tool. It is not the format described for publishing model documentation, exporting model metadata, or exporting data from a ViewModel.

Need	Use
Exchange a UML model with another modeling tool	XMI 2.4.2
Publish model documentation as a FlowDocument or XPS file	Documentation:Documtr and XPS
Export information exposed through a model extension ViewModel	Documentation:MDriven Designer and Modlr extensions–exporting data

See also

• Documentation:Importing web service interface as model
• Documentation:Documtr and XPS
• Documentation:MDriven Designer and Modlr extensions–exporting data