The following are frequently asked questions and answers for XMI Add-In.
There are two possible reasons why the menu does not show up. One is that XMI Add-In is not installed in StarUML(tm) or related files are damaged. To correct this, run the installation program to reinstall StarUML(tm) or select to reinstall XMI Add-In only. If you are familiar with the structure of StarUML(tm) Add-Ins, you may examine the registry or menu files to check for damage in the Add-In and correct the problem. Another possible reason for the problem is that XMI Add-In is disabled by Add-In Manager. If so, go to Add-In Manager and enable XMI Add-In. For the procedure to enable XMI Add-In, see the section on XMI Add-In Configurations.
XMI Add-In supports XMI 1.1, which is the most widely used version in the market today, and Unisys XMI 1.1, which is extended to include diagram information in XMI. In other words, XMI Add-In can be used to read and write XMI 1.1 (Unisys XMI 1.1) format files.
In order to use the XMI functions in IBM Rational Rose, you need to have an Add-In called "Unisys XML Tools" installed. For details on installing and using the Add-In, please refer to the technical documentation or support provided by the tool vendor.
If you want to use "Unisys XML Tools" in IBM Rational Rose to save an XMI format file for use by StarUML(tm) XMI Add-In, save the file as an "XMI 1.1" file.
If you want to save an XMI file in Borland Together for use by StarUML(tm) XMI Add-In, it is recommended to save the file as "XMI 1.1 for UML 1.3 (Unisys Extension)" or "XMI 1.1 for UML 1.3 (Unisys Extension, Recommended for Rose)".
This problem occurs because IBM Rational Rose's "Unisys XML Tools" only supports "ISO-8859-1" encoding (English only). To resolve this, please direct inquiries to IBM Rational customer support or the Unisys XML Tools vendor.
This problem occurs because Rational Rose omits information for the Dependency/Extend/Include elements of Use Case Diagram when saving XMI files.
This problem occurs because Rational Rose omits information for Association (connection) elements of Deployment Diagram when saving XMI files.
This problem occurs because Rational Rose omits information for some stereotypes such as "business use case", "use-case realization" and "ClassUtility" when saving XMI files.
While Rational Rose is capable of generating Statechart/Activity Diagram under State or Activity elements, this information is omitted when saving XMI files because it is conceptually incorrect for UML. This information cannot be restored.
While Rational Rose is capable of expressing Destruction Mark in Sequence Diagram, this information is omitted when saving XMI files because there is no appropriate modeling element that corresponds to it under the UML standard. This information cannot be restored.
This problem occurs because when saving XMI files Rational Rose omits information for Sequence Diagram that does not contain any message elements.
Borland Together incorrectly writes XML file encoding values when saving XMI files. For instance, hyphens ("-") in values such as "ISO8859_1" and "EUC_KR" are incorrectly replaced by underscores "_". Appropriate corrections must be made to the XMI files saved by Together before importing them into StarUML(tm).
If either the 'XMI 1.1 for UML 1.3 (Unisys Extension)' or 'XMI 1.1 for UML 1.3 (Unisys Extension, Recommended for Rose)' option is selected, Borland Together expresses Extend/Include elements of Use Case Diagram as Association elements.
Object elements generated from Sequence/Collaboration Diagrams in IBM Rational Rose or Borland Together are converted as ClassifierRole elements. This is because Rose and Together internally treat these object elements as ClassifierRole elements and express them as ClassifierRole elements when saving XMI files. Even if the user may not intend object elements to be converted as ClassifierRole elements, this is conceptually correct.
This problem occurs because information for diagram view elements is simplified when saving XMI files. Some UML modeling tools also omit some
of the information for view elements when saving XMI files. This varies slightly from one modeling tool to another.