1. Tell a Story

2. Use Case

3. Function and Form

4. First Form: A Narrative Make a Payment

5. Narrative Form

6. Second Form: A Scenario Register Customer With Automatic Activation

7. Scenario Form

8. Third Form: A Conversation Make A Payment - General Flow

9. Conversation Form

10. Comparing the Three Forms

11. The Benefits of Use Cases

12. Use Cases Aid Understanding

13. Use Cases Vary by Abstraction Level

14. Use Cases Vary in Scope

15. Use Cases Vary in Detail

16. What Use Cases Cannot Do

17. Finding Use Cases

19. Naming Use Cases

20. Primary and Secondary Actors

21. Naming Actors l Group individuals according to their common use of the system. Identify the roles they take on when they use or are used by the system l Each role is a potential actor l Name each role and define its distinguishing characteristics. Add these definitions to your glossary l Don’t waste time debating actor names

22. Actor and Use Case Checklist

23. Glossary

24. Glossaries

25. Build Consensus

26. Defining Concepts l Identify a concept and its distinguishing characteristics l More than a synonym for a word l Identifies a way of mentally dividing reality for purpose of talking or thinking

27. Writing Glossary Entries l Why this concept is important l Typical sizes or values l Clarify likely misunderstandings l Show an example l Explain graphical symbols l Relate entries

28. A Good Form for Definitions

29. Improving Glossary Definitions

30. Relating Definitions

31. Define Acronyms and Their Concepts

32. Avoid Using “Is When” or “Is Where”

33. Explain What Is Unclear

34. Setting the Stage for the Use Case l Level—summary, core, supporting, or internal use case? l Actor(s)—role names of people, objects or external systems initiating this use case l Context—the current state of the system and actor l Preconditions—what must be true before a use case can begin

35. Completing The Picture l Variations— different ways to accomplish use case steps l Exceptions— errors that occur during the execution of a step l Policies— specific rules that must be enforced by the use case l Issues— questions about the use case l Design notes— hints to implementers l Post-conditions— what must be true about the system after a use case completes l Other requirements— what constraints must this use case conform to l Priority— how important is this use case? l Frequency— how often is this performed?

36. Make Clear What You Don’t Know

37. Avoid Vague Words

38. Write General and Specific Cases

39. Actor Actions

40. Include System Actions

41. Describing Actions

42. Condense Information Entry and/or Validation Actions

43. State System Actions at a Reasonably High Level

44. Showing Optional and Repeated Actions