Introduction to Rational Rose

1. Introduction to Rational Rose General guidelines and Class diagrams

2. Rational Rose • A specialized tool for drawing UML diagrams and managing a project’s design. • Considered industry standard. • Has many specialized modules and editions. • Code generation • Real-time analysis • … • In this course it will serve mainly as a specialized drawing tool

3. Rose workspace Main toolbar Diagram Project tree view Documentation Dynamic toolbar

4. The project tree • Use case view • Used for analysis • Contains UC diag., actors. • Logical view • Used for design • Contains packages, classes, assoc. • Class, sequence and similar diag. • Component & Deployment view • Used for components design and final deployment diagrams

5. The project tree - usage • Double-click on an item to open its specification. • Right-click on an item to add a diagram or sub-items. • Most items can be dragged and dropped into a diagram to create an instance. • If an item is modified, the change is reflected in the entire project.

6. The logical view • Contains the project’s packages, classes, interfaces and associations. • Classes and interfaces contains their fields and methods. • Classes are drag-and-drop-able into diagrams to create instances. • If a class is modified in one place, the change is reflected to the whole project.

7. The class diagram

8. Class diagram toolbar • Select items • Add text • Add note • Bind note to item • Create new class • Create new interface • Draw new association • Association class • Create new package • Draw dependency • Class inheritance • Interface implementation

9. The class diagram • Standard UML class diagram • Distinguishes between class inheritance (plain) and interface implementation (dotted). • Classes, interfaces and associations are items. • Right-click on an item to: • Change appearance options • Add attributes and operations • Open spec. • Anything else…

10. Class diagram pitfalls (1) • Pitfall 1: when adding attr. and operations, pressing enter start a new item. • Click outside the class to exit. • Pitfall 2: when using delete to delete an item, it is removed only from the diagram, not from the model. • The shortcut to remove an item from the model is ctrl-D, or use right-click.

11. Class diagram pitfalls (2) • Pitfall 3: Rose uses Pascal notation for attributes and operation types. • The type follows the identifier, using ‘:’. • The return type of a function follows the function. • For example: • attr : type (like name : String) • func (arg : type) : type (like round(f : float) : int)

12. Class specifications (1)

13. Class specification (2)

14. Class specification explained • The “general” and “details” tabs control various parameters of the class itself • The “attributes” and “operations” tabs allows inserting, editing or deleting attributes and operations using right-click. • The “relations” tab shows the class relations. • Ignore other tabs, for now.

15. Association specification (1)

16. Association specification (2)

17. Association spec. explained • The “general” tab allows naming the assoc. and the participating classes. • Side A is the pointed side. Side B is the pointing. • “Role general” tab allows controlling the role’s name and visibility. • “Role details” controls the important things: • Multiplicity • Navigable • Aggregation / containment (e.g. “by value”) • Qualifiers and constraints