Software Requirements 3rd Edition
Ch. 8 Understanding user requirements (Use Case Template in Downloads)
Use Cases for Cafeteria Ordering System in Downloads Appendix C
Discovering Requirements section 5.3.4
System Use Cases: An Agile Introduction agilemodeling
How to Write a Use Case video (13:10)
Rules of Writing Software Requirement Specifications (with a section on use case diagrams) - Zalewski
UML Use Case Diagrams uml-diagrams.org
UML 2 Use Case Diagrams: An Agile Introduction agilemodeling.com
Fill out the Use Case Template
Fill out the Use Case List table
Under Primary Actor, put each User or User Class from Activity 6.3.3.2 in a row.
Under Use Cases, in the cell next to the Primary Actor, put the goal/desire part of each of the user stories from Activity 6.3.3.2 that involved that user. There will be multiple use cases for each primary actor. The use case name should be concise and indicate the value the use case would provide to some user. Begin with an action verb, followed by an object. Give each use case a unique integer sequence number identifier.
Hopefully your user stories are comprehensive but you need to think about all of the different people who will use the software and how they will use it. You may need to elicit more user stories to make a complete set of use cases. Use cases could also originate from sources other than user stories.
Represent the primary actor from the use case as a stick figure.
The actions that the actors take and their goals are represented by ovals with a solid arrow pointing to them. Not all actions can be directly done by an actor – some are triggered by other actions (represented by dotted lines, with the arrow indicating which action triggers the other).