Use Case Statement

By Manuel Dennis III

Name

Manage Request Identification Section

Description

This section corresponds with displaying the Request number and Request ID

Dependencies

An Request must exist in the database

Scope

To display a human readable and system requestid for a Request

Primary Actors

· Requester, Approver, Assigner

Secondary Actors

· Administrator, Worker

Pre Conditions

· A Request number is generated when an Request is created

Success End Conditions

· To allow the user to easily tell what Request number they are working with

Failure End Conditions

·

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

Use Case

#

Action / Stimulus

Reaction

1

User browses to the Manage Request Page either indirectly from a link on a grid or menu, or from a direct URL

The system will display the Request identification in the upper panel. Program support team will actually see the Request Number and Request ID, all others will see just the Request Number

2

  

The current status of the request should also appear here.

3

    

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

A1

    

A2

    

A3

    

 

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

B1

    

B2

    

B3

    

 

Alternative / Additional Scenario: Cancel

#

Action / Stimulus

Reaction

C1

    
     
     

Notes:

 

 

 

 

Issues: