25.2 Use Cases

• A use case should have:
  • Descriptive name
  • Main sequence of actions
  • Variants
    • Description of possible failures
• Can be made simple or formal

---

prev |top |next