Manage Assignment

Use Case Statement

By Manuel Dennis III

Name	Manage Assignment
Description	An overview of the Manage Assignment page
Dependencies	An Assignment needs to be in the database The business logic layer must exist to retrieve assignment and associated data
Scope	To modify and maintain assignments
Primary Actors	· Assigner, Worker
Secondary Actors	· Administrator, Approver
Pre Conditions	· All fields must be set based on the AssignmentID that comes in through a Request.Params collection
Success End Conditions	· The user can modify assignment information
Failure End Conditions	· Assignment information is not updated

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

Use Case

#	Action / Stimulus	Reaction
1	User makes changes to an assignment	System notes changes. Actual steps are noted in other Use Case statements
2	User presses Submit button	System saves changes
3

Alternative / Additional Scenario:

#	Action / Stimulus	Reaction
A1	User presses Cancel button	System does not save changes
A2
A3

Alternative / Additional Scenario:

#	Action / Stimulus	Reaction
B1	Toggle Visibility buttons	Many of the sections visibility can be toggled to allow the user to print assignments and only displaying the information they require on the report. Attachments, Comments, and Work Time are all good candidates since they may grow excessively over the life of an assignment.
B2
B3

Alternative / Additional Scenario: Cancel

#	Action / Stimulus	Reaction
C1

Notes:

Issues: