Use case templates have several fields, including the use cases name, descriptions, list of actors, assumptions, steps, variations, and non-functional requirements.
The name and description give the reader a quick understanding of what the use case is trying to depict. The list of actors identifies the human users and other systems involved, while the assumptions detail the conditions .
that must be true for the use case to run successfully.
Steps outline each individual action that the system must achieve, while the variations list potential optional steps. For example, the system may be designed to ask a user about their satisfaction level. If the user selects "dissatisfied," the system may have a variation to prompt the user for more details about why he is dissatisfied.
The non-functional requirements identify additional details that must be meant. Some of the most common non-functional requirements deal with system performance, reliability, and fault tolerance.
More Reference Links: http://www.bredemeyer.com/pdf_files/use_case.pdf http://www.csci.csusb.edu/dick/samples/usecases.html
