Use Case diagram model element mappings

You can use the mapping table for Use Case diagram model elements to understand the differences in metamodel implementation and the differences in UML notation between Rational Rose® and the Rational® modeling products in the Software Development Platform—Rational Software Modeler and Rational Software Architect.

Rational Rose (UML 1.4) Software Architect and Software Modeler (UML 2.0)
Actor (A Class stereotyped as Actor) Actor

If an actor owns attributes or operations, it will remain a Class stereotyped as Actor.

Association relationship to (or from) a Use Case Association
Note: A navigable association relationship pointing to a use case end imports without the arrowhead. A use case cannot own properties so the association end that typically defines the association cannot be navigable.
Dependency Relationships UML 2.0 Dependency (except for extend and include dependencies)
Extend (Dependency stereotyped as Extend) Extend relationship
Generalizations (invalid ones, such as a class that specializes a signal) Dependency relationship (with a corresponding keyword)
Include (Dependency stereotyped as Include) Include relationship
Use Cases (that own multiple interactions) Collaboration (only one), reference by the Use Case as a subject.
Use Case Realization (or a stereotyped use case realization) Collaboration (only one)
Related reference
Activity diagram model element mappings
Class diagram model element mappings
Collaboration diagram model element mappings
Component diagram model element mappings
Deployment diagram model element mappings
Sequence diagram model element mappings
Statechart diagram model element mappings
Notational differences in expressing multiplicity
Terms of use | Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.