New Request Page

Use Case Statement

By Deb Sands

Name	New Request Page
Description	An attempt to define the New Request Page
Dependencies	Information Section Machine Section Optional Section Attachments Section
Scope	Overview of the New Request Page features
Primary Actors	· Requester
Secondary Actors	·
Pre Conditions	· The requester must be set up in the database tables with personal info, example: User-id, password, department, title, etc. · Based on User-id, Machine, Requester, Department, Location, and Division will be populated on Load of Page.
Success End Conditions	· The Request information was successful in being created in the databases with any potential attachments.
Failure End Conditions	· The Request 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 RequestList.aspx page via a direct URL link	The system should prompt the requester 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 User-Id, ddl for Machine, Requester, Department, Location, Division should be filled in. Priority & Client will be none, Rank will be 0 and Requested Completion Date will be null (*need to check on this).
4	A User has hit Submit	Required fields are Subject, Description, Requester, Department, Location and Division. Any errors in storing the Request 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: