Use Case Statement

By Manuel Dennis III

Name

Manage Request Optional Section

Description

The optional section displays information relevant to a Request, but not necessary for every Request

Dependencies

A Request must exist

Scope

Display optional Request information that may help a worker complete a task

Primary Actors

· Requester, Worker, Assigner, Approver

Secondary Actors

· Administrator

Pre Conditions

· Request must exist

Success End Conditions

· All optional fields are displayed properly related to the Request

Failure End Conditions

·

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

Use Case

#

Action / Stimulus

Reaction

1

User navigates to a Request.

Optional drop down lists are populated with data that corresponds to the current Request. The drop down lists should be for Department, Division, Priority, Client, and Location.

Rank and Requested Completion date should be populated as text boxes or date combo.

2

    

3

    

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

A1

    

A2

    

A3

    

 

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

B1

User Presses the Optional button

This can toggle the visibility of the buttons related to the optional section. This can allow someone to print an Request from the browser with just including the relevant information, perhaps no optional info is necessary for the report.

B2

    

B3

    

 

Alternative / Additional Scenario: Cancel

#

Action / Stimulus

Reaction

C1

    
     
     

Notes:

 

 

 

 

Issues: