New Assignment Optional Section

Use Case Statement

By Deb Sands

Name	New Assignment Optional Section
Description	Information that is optional for the requester to either change or select.
Dependencies	Requester must be set up in database tables
Scope	Display optional Request information that a requester may or may not need to include in the request.
Primary Actors	· Requester
Secondary Actors	·
Pre Conditions	· Database tables must exist to populate optional dropdown lists. Other optional fields will be populated with default values.
Success End Conditions	· All dropdown lists are populated and other fields are populated with default values.
Failure End Conditions	· Error occurs in populating dropdown lists and/or other default values.

Document Revision #	Action Taken, Notes	When?	By Whom?
0.1

Use Case

#	Action / Stimulus	Reaction
1	Requester pulls up the New Request Page	Based on requester, Requester, Department, Location, and Division are populated. Priority and Client are defaulted as None. Rank is 0 and Requested Completion Date is none (need to check on this.)
2	The optional button is pressed	The optional section visibility is toggled to help minimize information displayed when optional information may not be relevant.
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: