Actors and Use Case Diagrams

1. Actors and Use Case Diagrams Month Day, Year

2. Agenda • Training Plan Overview • Review Detailing Requirements with Requisite Pro • Concepts • Setting Up • XDE Integration • Associating other requirements • Creating views • Actors • Use-Case Diagrams • Review Homework • Next Steps

3. Training Plan Overview • Introduction • Using Rational Administrator • Using ClearCase • Using ClearQuest • Using Rational Rose XDE • Identifying & Creating Use-Cases – Part 1 • Identifying & Creating Use-Cases – Part 2 • Detailing Requirements withRequisitePro • Actors and Use-Case Diagrams • Sequence and Statechart Diagrams • Collaboration and Class Diagrams • Integration and Development with the .NET Framework

4. Benefits Manage project requirements comprehensively Promotes communication and collaboration among team members Reduces project risk Features Tool combing power of a database and Microsoft Word. Powerful sort and query capabilities Requirements Organize Prioritize Trace relationships Manage requirement change Perform real-time impact analysis Informed decisions Scope management Resource allocation Review - ReqPro

5. Review - ReqPro • Requirements Management Plan • Guidelines for establishing the requirements • Requirement Types • Use-Case • Stakeholder Request • Feature • Supplementary • Glossary Item • Attribute Types • Risk • Priority

6. Review - ReqPro • Document Types • Vision • Use-Case Specification • Supplementary Requirement Specification • Test Plan • Views • Attribute Matrix • Traceability Matrix • Traceability Tree

7. Review - ReqPro • Requirement Types • Basic • Use-Case • Stakeholder Request • Feature • Supplementary Specifications • Glossary Item • Other • Business Goals • Business Rules • Interface • Test • Attribute Types

8. Review - ReqPro • Traceability • Between Two Requirements • Different • Can be same • To vs. From • Evolution • Realization • Requirement • Model

9. Review - ReqPro • View Types • Attribute Matrix • Requirement vs. Attribute • Illustrates the relationships between requirements and their attributes

10. Review - ReqPro • View Types • Traceability Matrix • Requirement vs. Requirement • Illustrates the relationships between requirements of the same or different types

11. Review - ReqPro • View Types • Traceability Tree • Requirement vs. Requirement • Displays all internal and external requirements traced to or from a requirement

12. Review - ReqPro • Folders • General Requirements • Models • Business Use-Case • Use-Case • Design • Reports • Views

13. Review - ReqPro • Views • Project Specific

14. Actors & Entities • Business Actor • Represents a role played in relation to the business by someone or something in the business environment • Business Worker • Represents an abstraction of a human that interacts within the system • Active • Business Entity • Represent an object that business workers access, inspect, manipulate, produce, … • Provide the basis for sharing • Passive • Actor • Represents someone in a role who interacts with the system • Interacts with but have no control over use-cases • Entity • Represents an object used to model information and associated behavior • May be persistent • May be active or passive

15. Actors • Actors represent system users • Interact with but have no control over use-cases • Create Actors at Model Level • Right click and select New UML, Package • Name Actors • Right click package and select New UML, Package • Name Contact Manager • Right click package and select New UML, Actor • Name Contact Manager

16. Use-Case Diagrams • Use-case diagrams • Graphically depict system behavior • Present a high level view of how the system is used as viewed from the actor’s perspective. • A use-case diagram may depict all or some of the use cases of a system • Select the use-case diagram • Drag the actor and use-case on to the diagram • Create an association between the actor and the use-case • Set line style to Oblique

17. Use-Case Diagrams • Label to clarify • Create alternative diagrams

18. Use-Case Diagrams • Complete Use-Case Detail diagrams • Illustrate other actors or use-cases used within the context of the incorporating use-case

19. Use-Case Diagrams • Define Associations • Includes • Used to partition out parts of a workflow for which the base use case only depends on the result, not the method for reaching the result. • Extends • Optionally, or conditionally, add a flow to a business use case that is already complete in itself • Generalizes • Specialization into one or more child use cases that represent more specific forms of the parent

20. Use-Case Diagrams • Complete other use-case diagrams of incorporated use-cases as needed • Select diagram • Drag and drop model elements from model tree • Add labels

21. Use-Case Diagrams • The Main diagram • Provides an quick overview of the model • Use grouping and labels to add context • Provides a navigation point for the model • Right click actor and use-case and select • Select in Browser

22. Use-Case Diagrams

23. Actors - Detail • Select View, Other Windows, Model Documentation

24. Actors - Detail • Right click and select Properties Window • Select UML section • Select Stereotype • Add business worker • Select Persistence • Select Transient

25. Actors - Detail

26. Actors - Detail • Select UML section • Select Multiplicity

27. Actors - Detail • Select a multiplicity

28. Actors - Detail • Attributes • Not typical of actors, but could be use for establishing role profile attributes • Select Attribute tab • Click Attribute Icon to add

29. Actors - Detail • Enter at least Name • Enter other attribute values • Repeat as necessary • Close

30. Actors - Detail • Components • Not typical of actors, but could be use for establishing role profile attributes • Defines attributes derived from other classes

31. Actors - Detail • Operations • Not typical of actors

32. Actors - Detail • Relationships • A relationship is a connection between model elements • Relationship types are: • Associations • Dependencies • Generalizations • Realizations • Transitions

33. Actors - Detail • Associations • An association is a structural relationship showing that objects of one classifier (actor, use case, class, interface, node, or component) are connected and can navigate to objects of another classifier • The are numerous association types

34. Uses Association • Uses Association shows which processes the actor is involved • Right cick and select Properties Window • Select UML section • Enter Name

35. Uses Association • Select End 1 Section • Enter Multiplicity • Select End 2 Section • Enter Multiplicity

36. Uses Association • Qualifiers • Acts as a constraint • Can be at either end of relationship • Aggregation • Persistence

37. Uses Association

38. Uses Association

39. Next Steps • Homework • Homework Model • Explode another top level use-case • Continue to concentrate on abstraction of detail • Use modeling elements • Business Use-Case Model Level • Add Use-Case Diagrams • Classes Ahead • Sequence and Statechart Diagrams • Collaboration and Class Diagrams • Integration and Development with the .NET Framework