Use Case Reference Template (Page 3 of 5) in pdf

Use Case Reference

3.3.

Preconditions

List any activities that must take place, or any conditions that must be true, before the use case can be started.

Number each precondition. Examples:

User’s identity has been authenticated.

User’s computer has sufficient free memory available to launch task.

3.4.

Postconditions

Describe the state of the system at the conclusion of the use case execution. Number each postcondition. Examples:

Document contains only valid SGML tags.

Price of item in database has been updated with new value.

3.5.

Normal Flow

Provide a detailed description of the user actions and system responses that will take place during execution of the

use case under normal, expected conditions. This dialog sequence will ultimately lead to accomplishing the goal

stated in the use case name and description. This description may be written as an answer to the hypothetical

question, “How do I <accomplish the task stated in the use case name>?” This is best done as a numbered list of

actions performed by the actor, alternating with responses provided by the system. The normal flow is numbered

“X.0”, where “X” is the Use Case ID.

3.6.

Alternative Flows

Document other, legitimate usage scenarios that can take place within this use case separately in this section. State

the alternative flow, and describe any differences in the sequence of steps that take place. Number each alternative

flow in the form “X.Y”, where “X” is the Use Case ID and Y is a sequence number for the alternative flow. For

example, “5.3” would indicate the third alternative flow for use case number 5.

3.7.

Exceptions

Describe any anticipated error conditions that could occur during execution of the use case, and define how the

system is to respond to those conditions. Also, describe how the system is to respond if the use case execution fails

for some unanticipated reason. If the use case results in a durable state change in a database or the outside world,

state whether the change is rolled back, completed correctly, partially completed with a known state, or left in an

undetermined state as a result of the exception. Number each alternative flow in the form “X.Y.E.Z”, where “X” is

the Use Case ID, Y indicates the normal (0) or alternative (>0) flow during which this exception could take place,

“E” indicates an exception, and “Z” is a sequence number for the exceptions. For example “5.0.E.2” would indicate

the second exception for the normal flow for use case number 5.

3.8.

Includes

List any other use cases that are included (“called”) by this use case. Common functionality that appears in multiple

common functionality.

use cases can be split out into a separate use case that is included by the ones that need that

3.9.

Priority

Indicate the relative priority of implementing the functionality required to allow this use case to be executed. The

specification.

priority scheme used must be the same as that used in the software requirements

3.10. Frequency of Use

Estimate the number of times this use case will be performed by the actors per some appropriate unit of time.

Use Case Reference Template Page 3

Related Articles

Related forms

Related Categories