Use Case Statement

By Manuel Dennis III

Name

New Assignment Page

Description

An attempt to define the New Assignment Page

Dependencies

Identification, Info, Optional, Machine, Estimate, and
Attachment Sections

Scope

Overview of the New Assignment Page features

Primary Actors

· Assigner

Secondary Actors

· Administrator

Pre Conditions

· The Assigner must be set up in the database

· A Request must exist

· Based on Personid, Machine, Assigner, Department, Location, and Division will be populated on Load of Page.

Success End Conditions

· The Assignment information was successful in being created in the databases with any potential attachments.

Failure End Conditions

· The Assignment information was not successful in being created in the databases.

· Required fields were missing.

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

 

 

Use Case

#

Action / Stimulus

Reaction

1

A User visits the AssignmentList.aspx page via a direct URL link

The system should prompt the Assigner for valid authorization and authentication.

2

The User could hit Cancel

The system should clear all textbox values and reset dropdown lists to initial values based on page load.

3

A User has logged on using log in screen

Based on PersonId, Check Box List for Machine, Assigner, Department, Location, Division should be filled in. Priority & Client will be none, Rank will be 0 and Assignment Completion Date will be null (*need to check on this).

4

A User has hit Submit

Required fields are Subject, Description, Assigner, Department, Location and Division. Any errors in storing the Assignment information will be reported back to the page in the ErrorMsg field.

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: