XMI import

Bring existing SysML models into traceunified from Cameo, MagicDraw, Rhapsody, Enterprise Architect, or Papyrus via XMI — through Import Center’s Architecture Import wizard.

Most regulated programs already have a model somewhere — often in Cameo, MagicDraw, IBM Rhapsody, Enterprise Architect, or Papyrus. XMI import is how that model becomes first-class architecture in the same database as your requirements and tests, instead of a file you keep reconciling.

What XMI import does

XMI (XML Metadata Interchange) is the OMG standard for exchanging UML/SysML models between tools. Importing an XMI file creates model elements in your project — blocks, parts, and related constructs your configuration recognizes — so they participate in versioning, linking, and baselining like any other governed record, and in suspect flagging according to your trace rules.

Compatible sources include Cameo, MagicDraw, Rhapsody, Enterprise Architect, and Papyrus. Exact element coverage depends on what the export contains and how source types resolve against your model configuration. Some diagrams cannot be imported, or are imported in a degraded form, so review each imported diagram against the source.

Type mapping

Source tools and traceunified do not always share stereotype or type names 1:1. On parse, Architecture Import builds type mappings automatically against your project’s configured element, relationship, stereotype, and diagram types — the same idea as ReqIF type mapping for requirements.

You do not walk a separate Mapping step in the wizard. Preview validates the plan and surfaces mapping issues (for example unmapped element types) before you commit, so unexpected types are fixed up front rather than cleaned up later.

Traceability after import

Import brings structure into the Architecture module. It does not automatically invent satisfy/verify links to requirements that still live only in another ALM. After import:

  1. Bring requirements via ReqIF / CSV / Excel / Word if they are not already in the project.
  2. Link architecture to requirements so the model sits on the thread.
  3. Confirm impact with impact analysis before you change an element or requirement. Editing an architecture block’s content does not flag linked items suspect automatically.

How to import a model

Before you start Export XMI (.xmi or .xml) from your modeling tool for one subsystem or package first — not the entire enterprise model on day one. Open Import Center in the target project (Architecture module licensed and writable).

  1. Format — Choose an import mode (Create New, Update Existing, or Smart Mode), then select source format XMI (OMG Standard). That opens the Architecture Import wizard at Upload.
  2. Upload — Drop or browse to the .xmi / .xml file and wait for parse to finish.
  3. Selection — On Select Items to Import, choose which packages, elements, and diagrams to include. Deselected items are skipped.
  4. Destination — On Import Destination, pick the target package (or leave Model Root).
  5. Preview — Review Import Preview counts and validation. Optionally run Dry Run (nothing is written). Resolve any mapping or validation errors before continuing.
  6. Import — Confirm and run the import. Progress covers elements, relationships, and diagrams.
  7. Results — Confirm Import Complete, download the Architecture Import Report if you need an audit artifact, then open the model on the canvas.

Result Model elements appear in the containment tree as first-class records. Some diagrams may be missing or degraded, so check them against the source. Continue modeling natively and link them to requirements.

Note Deep simulation or code generation may still belong in a specialist MBSE tool. Hybrid is normal: govern the regulated architecture baseline here; keep Cameo/Rhapsody for fidelity work when you need it. See Migrate from Cameo or Rhapsody.

Where to go next

Was this helpful?