Use Case Statement

By Deb Sands

Name

New Request Information Section

Description

How and what information is required to create a New Request

Dependencies

Requester must be set up as a Requester in the system.

Request Business Logic Layer

Scope

To get enough information to submit work from and for various departments.

Primary Actors

· Requester

Secondary Actors

·

Pre Conditions

· The database must contain information for all dropdown lists.

· The requester information must be in the database.

Success End Conditions

· All information was provided in the dropdown lists and Requester has submitted all required fields.

Failure End Conditions

· Requester has not submitted all required fields and/or the dropdown lists could not be populated correctly.

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

 

 

UseCase

#

Action / Stimulus

Reaction

1

Requester has logged into system with valid User-ID.

Based on User-id, Machine, Requester, Department, Location, Division are populated. It is possible to change this information, example, entering for someone else, or a person works for multiple divisions, etc. This is controlled by roles or groups.

Non-required dropdown lists are Category, Action, Priority, Client, which will default to none on page load. Rank will default to 0 and Requested Completion Date will be Null. (*need to check on this).

2

User has provided all required information.

Required fields are, Subject, Description, Requester, Department, Location, and Division.

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: