Introduction to Rational Rose 2000

1. Introduction to Rational Rose 2000 Create Use Case Model

2. Module Objectives • Define the elements of the use case model. • Use cases • Actors • Relationships • Use case diagrams • Add diagrams to the Use Case View. •  Create Packages and place ‘appropriate’ or ‘like’ use cases in same package. • Link Use Case narratives using Requisite Pro.

3. Where Are We? Use Cases and Actors are identified and briefly outlined during early stages of Inception. Some Architecturally-significant Use Cases are described in detail during Inception phase; About 80% of Use Cases are done by end of Elaboration. Construction addresses other scenarios/paths… In Analysis and Design Workflow, Use Case model is continuously updated and refined.

4. Key Concepts of Use Case Model: Is a model of application’s intended functions and its environment Is a contractbetween customer and developer Is essential to analysis, design, and test activities Includes Use Case Diagrams, Use Case flows of events, and supplementary documentation.

5. Key Concepts Illustrate relationships between use cases and actors and among related use cases to show the dynamic aspects of the system. A Use Case represents a major piece of functionality that is complete from beginning to end. Use Cases are a sequences of actions between the use case client and the application that yields an observable result and are of value to a particular actor. Use Cases are described textually in a document called the flow of events. (Used later in interaction diagrams) Actors: something or someone outside system that interacts with the system either by giving or receiving information – or both. Relationships are connections between model elements.

6. Relationships • Two kinds: • Generalization and association • Generalizationscan be used between use cases and between actors. (Be very careful!!!!) • The generalization icon is used between actors to indicate child/parent relationship. • Associationsconnect actors to use cases and use cases to use cases. • Remember, ‘includes’ and ‘extends’ are modeled as associations not via generalization… • An association is the most general relationship. • It indicates communication only. • These relationships can be stereotyped as communicates, extends, includes, realizes, and subscribe. (Several other stereotypes exist…)

7. Previews of Coming Distractions…. • Objectives • Name the model and set up stereotype icons. • Create a use case model. • Actors • Use cases • Relationships • Supplemental documentation • Flow of events • Do these on your own… See slides ahead. These come directly from text…

8. Add Use Case Diagram to Model In Browser, click Use Case View; double click Main; (may select and delete symobls…) May expand Diagram window) In Diagram Toolbar, double click actor, click inside diagram, leave as new actor for now. Note: new actor is added to browser. Make five actors. OR Right click Use Case View; Select New; Select Actor; Put name directly into browser; drag icon onto diagram window. Can ‘name’ actor by: Right click actor in diagram window; Open Spec; give name. OR Right click on new actor in browser, Rename, give name. OR Right click new actor in browser, Open Spec, give name. OR Can shift-click actor icon in toolbox: Click icon in toolbox, then merely hold shift key down and just click mouse in diagram window for additional actors….release shift for last icon. Then, name as above… Actors added to diagram Adding actors to diagram…

9. Use cases added to diagram Add Use Case Diagram to Model Same techniques to add the Use Cases to Model Use toolbar or right click from New from Use Case View Name as usual. But: When you right click the icon in the diagram window and select Open Specification, you could provide the Basic Flow of Events in the window… OR Right click on icon in diagram window and type text into the Documentation Window (lower left of screen). (However, we want Use Cases documented separately.) Change color? Shift click all use cases to be colored. Go to Format, Fill Color; Select use cases will be changed.

10. Unidirectional associations added to diagram Add Associations to Model Add unidirectional associations (no shift click available) An association provides a pathway between actors and the application. Allows communications to flow in one direction. From the diagram toolbar, click Unidirectional Association icon. Drag your mouse from the Student actor to the View Report Card use case. Be certain tip of arrow extends INTO the receiving model element! Repeat step 1 for all remaining associations. Although not always possible, try to design your use case diagram without crossing relationships.

11. Main use case diagram Actor Associations Use Cases Add Use Case Diagram to Model Check out your Browser! Remember, only elements that appear in the browser are part of the model. n the browser, check your use case model to ensure all actors, use cases, and relationships are accurate. Are all your elements represented? Are there elements in the browser that should not be included? Now, let’s link each flow of events to its use case.

12. Flow of events added to use case model Add Use Case Flow of Events To add link to flow of events: Right click Use Case in browser (or model element in the diagram.) So, Right click on selected Use Case; Select Open Specification; Select Files tab; right click inside pane; Select Insert file. Browser window will appear, and you can select desired file by selecting Open; Flow of Events is now linked to Use Case. I want .html files, though…as discussed.

13. Supplemental documents added to use case model Add Supplemental Documentation Link documents to model… In browser, select Use Case View, New, File, control-click to select Problem Statement, Supplemental Specifications, and Glossary. Note: if diagram looks too compressed, can use Format, Autosize, ALL

14. Preferred Practices • Create in Use Case View. • Use packages to organize the model. • Represent each use case on at least one use case diagram. • Show interactions between actors and use cases. • Show relationships between use cases, if applicable.