When you import data from Rational System Architect, the other Rational modeling products support a subset of UML 2.1 elements.
The following table summarizes how UML elements from Rational System Architect map to UML elements in other Rational modeling products.
When you export data from other Rational modeling products, Rational System Architect supports a subset of UML 2.1 elements.
The following table summarizes how UML elements from other Rational modeling products map to UML elements in Rational System Architect.
| UML 2.1 element in other Rational modeling products | UML element in Rational System Architect |
|---|---|
| Actor | Actor (a class with the «actor» stereotype applied) |
| Association between classes and interfaces of the following kinds: none, aggregation, or composition | Association of the corresponding kind |
| Association where one end involves a use case | Use-case association |
| Association property owned by a class (navigable end), or a property owned by an association (non-navigable) | Association end |
| Class | Class with no stereotype applied |
| Connector between ports (either owned by a collaboration or a class) | Port link The export functionality in other Rational modeling products detects connectors between ports that are defined in collaboration elements or in classes, and creates corresponding port link definitions in the exported XML data. In version 11.2 and later of Rational System Architect, when you reconcile the data that you export from Rational modeling products, even though the semantic definitions for these port links exist in the Rational System Architect data encyclopedia, the exported port links are not displayed in class diagrams. |
| Extends relationship | Extends relationship (between use cases) |
| Generalization relationship (between use cases) | Generalization relationship (between use cases) |
| Generalization relationship (between classes or interfaces) | Inherits from relationship (between classes) |
| Includes relationship | Includes relationship (between use cases) |
| Interface | Interface (a class with the «interface» stereotype applied) |
| Operation owned by a class or interface | Method |
| Package | Package (hierarchy maintained) |
| Parameter (owned by the operation) | Formal parameter |
| Port (owned by class) | Port |
| Property owned by a class or interface (a non-association property) | Class attribute |
| Realization relationship | Realizes relationship |
| Interface realization relationship | Realizes relationship (with a target interface) |
| Stereotypes and keywords applied to an element | Stereotype property If only one stereotype or keyword was applied in the other Rational modeling products, the stereotype property, which is a string, contains the name of the stereotype or property. If multiple stereotypes or keywords are applied, the stereotype property is a comma-separated list that contains the corresponding names. For actor and interface objects, the corresponding stereotype name is always at the beginning of this list. |
| Use case | Use case |