A successful software product can be measured in many different ways (accuracy, speed, etc) however user satisfaction is often at the top of the list.
A use case should properly describe how a user is going to use the system, so that it can be easily modeled and built – so that the users are happy with their software.
The inception and elicitation phases should provide you with the info you need to build your use cases.
Use cases are normally written in an informal narrative format. Some people may write them as a sequential set of steps to accomplish a task.
Refining the preliminary use case often means asking questions like:
- Can the user take any other action at this point?
- What errors might the user encounter, and how should they handle them?
- What other behaviors can the user encounter? (i.e. something outside of their choosing and control)
Pg 178 has a formal use case sample showing the actors, preconditions, goals/expected outcome, steps taken, possible issues encountered, priority, frequency, as well as open issues and questions.
Scenario Based Modeling was originally found on Access 2 Learn
