XMI Export from Papyrus to Enterprise Architect: Do stereotypes and diagram layout survive round‑trip?

Goal

Validate that a UML model exported as XMI from Eclipse Papyrus can be imported into Sparx Enterprise Architect without losing applied stereotypes, tagged values, or diagram layout information.

Constraints & Uncertainty

• The XMI header specifies the UML metamodel version; a mismatch between Papyrus (e.g., UML 2.5) and Enterprise Architect may cause elements to be dropped or transformed.
• Diagram layout is not part of core UML semantics; it is typically carried by the UML Diagram Interchange (DI) extension, which Enterprise Architect may only partially support.
• Both tools may embed proprietary extensions or stereotypes that are not part of the standard XMI schema.

Specific Questions

1. Will Enterprise Architect import all stereotypes defined in the Papyrus model, or will they be omitted or converted to generic tags?
2. Is the diagram layout preserved when the XMI file is imported into Enterprise Architect, or are elements repositioned arbitrarily?
3. Does Enterprise Architect’s XMI importer recognize the UML metamodel version declared by Papyrus, and how does it handle any version discrepancies?