Use case documentation records how users achieve goals through an application. It combines UML use case diagrams with written descriptions, connecting requirements to runtime behavior. section 3.6
A written use case description typically records:
- Name, goal, summary, actors, preconditions, and trigger. section 3.6.2
- A primary action sequence of about ten steps or fewer, plus alternate sequences for failures. section 3.6.2
- Postconditions, applicable nonfunctional requirements, references to other use cases, and a glossary. section 3.6.2
Search Catalogue
A customer-triggered use case describes searching a book catalogue with target book attributes and receiving matching books. Writing the steps from the actor’s viewpoint keeps the goal and interaction explicit. section 3.6.2
