Use case diagram to class diagram mappings (Connector for IBM Rational Rose)
Each Use Case Diagram is created as a Use Case Diagram or Class Diagram in Modeler. You choose whether to import Use Case diagrams as Use Case Diagrams or Class Diagrams on the Set Import Options page of Connector for IBM Rational Rose.
This topic documents Use Case Diagram to Class Diagram mappings. For information about Use Case Diagram to Use Case Diagram mappings, see
The name of the Use Case Diagram or Class Diagram is derived from the diagram Name and its Package:
<package name>::<diagram name>
The items on a Use Case Diagram are imported to a Class Diagram as follows.
Actor
Each Actor is created as an Actor in Modeler.
If the Actor is stereotyped by the Business Actor stereotype in the Rose model, the imported Actor is stereotyped by the «Business Actor» stereotype in Modeler. The «Business Actor» stereotype makes the Actor look similar to a Business Actor in Rose.
The following properties are imported.
Rose Property | Modeler Property |
|---|---|
Documentation | Description |
Name | Name |
Dependencies and Instantiates
Dependency and Instantiates links may be created as a Dependency, a Dependees link, or it may not be imported.
Rose Source Item | Rose Destination Item | Modeler Item |
|---|---|---|
Actor | Package or Use Case | Dependency |
Actor | Actor | Dependency |
Package | Actor or Package | Dependency |
Package | Use Case | Dependency |
Use Case | Actor or Package | Dependency |
Use Case | Use Case | Dependency |
Generalize Relationship
Each Generalize relationship is created as a Generalization in Modeler. The following properties are imported.
Rose Property | Modeler Property |
|---|---|
Documentation | Description |
Name | Name |
Note (on diagram)
Each Note is created as a Note in Modeler. Note Links are not imported.
Package
Each Package is created as a Package in Modeler. The following properties are imported.
Rose Property | Modeler Property |
|---|---|
Documentation | Description |
Name | Name |
Text Box
Each Text Box is created as a Note in Modeler.
Unidirectional Association
Each Unidirectional Association is created as an Interaction, Extends Flow, or Includes Flow in Modeler. Note that Extend Flows and Includes Flows have no properties in Modeler.
Rose Source Item | Rose Destination Item | Modeler Property |
|---|---|---|
Actor | Actor | Association |
Actor | Use Case | Not imported |
Use Case | Actor | Not imported |
Use Case | Use Case | If Stereotype is Extend, creates an Extends Flow. If Stereotype is not Extend, creates an Includes Flow. |
Use Case
Each Use Case is created as a Use Case in Modeler.
If the Use Case is stereotyped by the Business Use Case stereotype in the Rose model, the imported Use Case is stereotyped by the «Business Use Case» stereotype in Modeler. The «Business Use Case» stereotype makes the Use Case look similar to a Business Use Case in Rose.
The following properties are imported.
Rose Property | Modeler Property |
|---|---|
Documentation | Description |
Name | Name |