Use Case Template (Page 6 of 7) in pdf

5. System prompts user to select transaction type

6. Customer selects Withdrawal From Checking

7. System prompts user to enter withdrawal amount

8. …

9. System ejects ATM card]

Alternative Flows:

[Document legitimate branches from the main flow to handle special

[Alternative Flow 1 – Not

conditions (also known as extensions). For each alternative flow reference the

branching step number of the normal flow and the condition which must be

in Network]

true in order for this extension to be executed. e.g. Alternative flows in the

Withdraw Cash transaction:

4a. In step 4 of the normal flow, if the customer is not in the bank network

System will prompt customer to accept network fee

Customer accepts

Use Case resumes on step 5

4b. In step 4 of the normal flow, if the customer is not in the bank network

System will prompt customer to accept network fee

Customer declines

Transaction is terminated

Use Case resumes on step 9 of normal flow

Note: Insert a new row for each distinctive alternative flow. ]

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.

e.g. Exceptions to the Withdraw Case transaction

2a. In step 2 of the normal flow, if the customer enters and invalid PIN

1. Transaction is disapproved

2. Message to customer to re-enter PIN

3. Customer enters correct PIN

4. Use Case resumes on step 3 of normal flow]

[List any other use cases that are included (“called”) by this use case.

Includes:

Common functionality that appears in multiple use cases can be split out into

a separate use case that is included by the ones that need that common

functionality. e.g. steps 1-4 in the normal flow would be required for all types

of ATM transactions- a Use Case could be written for these steps and

“included” in all ATM Use Cases.]

[How often will this Use Case be executed. This information is primarily useful

Frequency of Use:

for designers. e.g. enter values such as 50 per hour, 200 per day, once a

week, once a year, on demand etc.]

Special Requirements:

[Identify any additional requirements, such as nonfunctional requirements, for

the use case that may need to be addressed during design or

implementation. These may include performance requirements or other

quality attributes.]

Assumptions:

[List any assumptions that were made in the analysis that led to accepting this

use case into the product description and writing the use case description.

e.g. For the Withdraw Cash Use Case, an assumption could be:

The Bank Customer understands either English or Spanish language.]

Notes and Issues:

[List any additional comments about this use case or any remaining open

issues or TBDs (To Be Determined) that must be resolved. e.g.

1. What is the maximum size of the PIN that a use can have?]

Page 6

7/23/2015

Use Case Template Page 6

Related Articles

Related forms

Related Categories