Use Case Statement

By Manuel Dennis III

Name

Manage Request Info Section

Description

To display relevant information about an Request so a user can easily tell what the Request’s purpose it

Dependencies

An existing Request should exist in the database

Scope

Display information describing an Request

Primary Actors

· Requester, Worker, Assigner, Approver

Secondary Actors

· Administrator

Pre Conditions

· An Request must exist

Success End Conditions

· Request information is displayed correctly to the corresponding user

Failure End Conditions

· Request info is display incorrectly, or to the wrong user

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

Use Case

#

Action / Stimulus

Reaction

1

User requests an Request

Request information is displayed dealing with the category, action required, subject line, and description. The description should be the first comment from the related comments for this Request.

2

    

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: