Use Case Statement

By Manuel Dennis III

Name

Manage Request

Description

An overview of the Manage Request page

Dependencies

A request needs to be in the database

The business logic layer must exist to retrieve requests and associated data

Scope

To modify and maintain requests

Primary Actors

· Assigner, Approver, Worker, Requester

Secondary Actors

· Administrator

Pre Conditions

· All fields must be set based on the RequestID that comes in through a Request.Params collection

Success End Conditions

· The user can modify request information

Failure End Conditions

· Request information is not updated

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

Use Case

#

Action / Stimulus

Reaction

1

User makes changes to a request

System notes changes. Actual steps are noted in other Use Case statements

2

User presses Submit button

System saves changes

3

    

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

A1

User presses Cancel button

System does not save changes

A2

    

A3

    

 

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

B1

    

B2

    

B3

    

 

Alternative / Additional Scenario: Cancel

#

Action / Stimulus

Reaction

C1

    
     
     

Notes:

 

 

 

 

Issues: