1. Copyright © Craig Larman. 2000 All Rights Reserved Use Cases

2. Copyright © Craig Larman. 2000 All Rights Reserved 2 Introduction n Types: – business use cases – system use cases (our focus) n Use cases tell a story of actors using a system. n They illustrate functional requirements, by the stories they tell. n Complementary with a function requirement list.

3. Copyright © Craig Larman. 2000 All Rights Reserved 3 Identifying Use Cases n Major distinct, complete, end-to-end processes of using a system. n Not usually one step, but a complete story. – Common “mistake”! n Examples – Rent Videos – Return Videos – Pay Fines

4. Copyright © Craig Larman. 2000 All Rights Reserved 4 Use Case Diagram n A way to conceive and illustrate the use cases. n Usually created during the initial use case analysis.

5. Copyright © Craig Larman. 2000 All Rights Reserved 5 A Sample Detailed Use Case

6. Copyright © Craig Larman. 2000 All Rights Reserved 6 A Sample Summary Use Case n Same principles a detailed use case, but simplifies steps and details, as a low-fidelity incomplete first draft. – Useful during early requirements and scope analysis System Responsibilities 3. Remember rented items. 4. Calculate and present price. 6. Authorize and record payment. Actor Intentions 1.Customer presents items to rent. 2.Clerk records items. 5. Customer pays.

7. Copyright © Craig Larman. 2000 All Rights Reserved 7 Use Case Forms n Short, “high-level”, summary form. – Write most of them in this form during Inception. – Write a few keys ones in the detailed form. n Long, “expanded”, detailed form. – Write them this way during Elaboration.

8. Copyright © Craig Larman. 2000 All Rights Reserved 8 Use Miscellany n Simple “CRUD” use cases can be combined into one “Maintain ”. – Maintain Inventory n Start name with a verb. n Start with sentence 1 with “ does ” n All systems have a Start Up and Shut Down use case (perhaps trivial).

9. Copyright © Craig Larman. 2000 All Rights Reserved 9 Essential and Concrete Use Cases n Essential use cases defer the details of the UI, and focus on the intentions of the actors, and responsibilities of the system. – Concrete (AKA Real) do not. n Essential: “The AccountHolder identifies themselves to the ATM” n Real: “The AccountHolder inserts their card in the reader. Window A is displayed. They enter their PIN on the numeric keypad, …” n As we move from analysis to design, we are more inclined to move from essential to concrete use case descriptions.

10. Copyright © Craig Larman. 2000 All Rights Reserved 10 Relating Use Cases n When creating the use case diagram, it can be useful (in terms of comprehension and simplification) to: – factor out shared sub-processes use the > relationship – show precedence order use the > relationship

11. Copyright © Craig Larman. 2000 All Rights Reserved 11