Use case diagram to use case diagram mappings (Connector for IBM Rational Rose)

Integrations (PTC products, 3rd party products and code) > 3rd party product integrations (CM, DOORS, Rose, Simulink and XML) > Connector for IBM Rational Rose > Items and diagram mappings > Use case diagram to use case 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 Use Case Diagram mappings. For information about Use Case Diagram to Class Diagram mappings, see Use case diagram to class diagram mappings (Connector for IBM Rational Rose)

The name of the Use Case Diagram or Class Diagram is derived from the diagram Name and its Package:

The items on a Use Case Diagram are imported to a Use Case 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 an Interaction, Extends Flow, or Includes Flow in Modeler; a Dependees link in Modeler; or it may not be imported.

Rose Source Item	Rose Destination Item	Modeler Item
Actor	Use Case	Dependency
Actor	Actor or Package	Dependency
Package	Actor or Use Case	Dependency
Package	Package	Dependency
Use Case	Actor	Dependency
Use Case	Package	Dependency
Use Case	Use Case	If Stereotyped by the Extend stereotype, creates an Extends Flow. If not Stereotype by the Extend stereotype, creates an Includes Flow.

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. Although the Package is created in Modeler, the Package is not shown on the Use Case Diagram, because Modeler Use Case Diagrams do not support Packages.

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 Item
Actor	Actor	Not imported
Actor	Use Case	Interaction
Use Case	Actor	Interaction
Use Case	Use Case	If Stereotyped by the Extend stereotype, creates an Extends Flow. If not Stereotype by the Extend stereotype, 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