The following table summarizes the limitations of importing Rational® System Architect data into Rational modeling products:
| Limitation | Description |
|---|---|
| Class diagrams | In Rational modeling products,
UML class diagrams contain an invalid symbol. This problem might
occur for either of the following reasons:
To resolve the problem, in Rational modeling products, delete the symbol from the diagram. |
| Diagram appearance | When importing class diagrams and use-case diagrams, Rational modeling products ignore
UML positional attributes from Rational System Architect. After you import the diagrams into Rational modeling products, the other symbol attributes, such as size, color, and font, default to UML values from Rational modeling products. |
| Diagram notation | In Rational modeling products,
UML activity, sequence, and communication diagrams do not contain
the same elements as the diagram that you import from Rational System Architect. By default, UML activity, sequence, and communication diagrams are canonical. The import functionality creates empty diagrams that are populated the first time that you open the diagram. Therefore, the default diagram layout might not match the layout of the diagram in Rational System Architect; also, all Rational System Architect diagram notations, such as notes, are missing. |
| Lifelines | In Rational modeling products,
the UML focus of control for a lifeline does not match the Rational System Architect focus
of control for a lifeline. In Rational modeling products, the focus of control for lifelines are semantic elements owned by the corresponding interaction, and are used in the algorithm that calculates sequence numbers. In Rational System Architect, the focus of control symbols are simply notations that you can add to diagrams. |
| Merge issues | When you import Rational System Architect class
diagrams or use-case diagrams into Rational modeling products,
you might receive errors. In the Merge window, review the proposed
changes and consider how you will use a specific diagram in the model,
and what information the diagram illustrates. These factors determine
which of the following approaches you should use when you import class
diagrams or use-case diagrams from Rational System Architect:
Check the Problems view for more information. |
| Messages | In Rational modeling products,
message sequence numbers do not match sequence numbers from Rational System Architect. This mismatch occurs because the algorithms that calculate sequence numbers are different: In Rational modeling products, sequence numbers can only be calculated by using the semantic elements that the interaction owns. In Rational System Architect, sequence numbers can be calculated, or you can set them explicitly. |
| Nested diagrams | Nested diagrams do not always export from Rational System Architect. To resolve this problem, in Rational System Architect, open an Explorer tab and select multiple elements to export, such as the root package and the missing diagram. |
| Operations | All parameters in UML operations specify the
"in" direction type. Rational System Architect uses language-specific qualifiers such as &, *, and const, which are not interpreted when the data is imported into Rational modeling products. To resolve this problem, in Rational modeling products, in the Properties view, select the direction parameter and change it to the correct direction. |
| Ports | Some ports and port links are not imported into
UML models in Rational modeling products. In Rational System Architect, you can create ports on classes that have the «actor» and «interface» stereotypes applied; however, in Rational modeling products, actor and interface elements cannot own ports so the associated port links are not imported. |
| Sequence Diagrams | In sequence diagrams, positional data from Rational System Architect is
ignored. The Rational modeling products ignore positional data from Rational System Architect sequence diagrams. In Rational modeling products, the diagrams are automatically populated to reflect the semantic elements that the underlying UML interaction contains. To adjust the layout, right-click an empty spot in the diagram; then click Arrange All. You can also arrange the diagram elements manually. |
| XML files | When you import data into Rational modeling products,
you might receive a prompt to place a temporary XML file under version
control if the original XML file exists in a project that is under
version control. The file for which you receive this prompt is a temporary, modified version of the original XML file, which is created during the import process. This file is deleted when the import process is complete. If you receive this prompt, in the "Add to source control" window, click Cancel. To prevent this window from opening, move the exported file into a workspace project that is under not version control. |
The following table summarizes the limitations of exporting data from Rational modeling products:
| Limitation | Description |
|---|---|
| Dependencies | UML dependencies appear as if they did not export Rational System Architect. In Rational System Architect, each dependency has a definition, or semantic element, but the client and supplier of the dependency are defined only in a diagram on which the dependency is drawn. You cannot export diagrams from Rational modeling products. In Rational System Architect, existing dependencies should not be affected when you import any changes made in Rational modeling products. For dependencies that were created in Rational modeling products, you must manually add these dependencies to the corresponding diagrams in Rational System Architect. |
| Diagrams | Diagrams created or modified in Rational modeling products are
not exported. The export functionality in Rational modeling products does not support diagrams. When you import the data into Rational System Architect, you must add or update the diagrams, including activity and sequence diagrams, manually. |
| Port links | When you import UML data back into Rational System Architect,
port links are not displayed when the classes that own the associated
ports are added to a diagram. This is a known problem in Rational System Architect. |