Use Case Statement
By
Manuel Dennis III
Name |
Manage Assignment Status Section |
Description |
Display a panel of status information related to an assignment |
Dependencies |
An assignment must exist |
Scope |
Display a panel which contains the current assignment status Also display a grid of previous assignment states |
Primary Actors |
|
Secondary Actors |
|
Pre Conditions |
|
Success End Conditions |
|
Failure End Conditions |
Document Revision # |
Action Taken, Notes |
When? |
By Whom? |
0.1 |
|
|
|
Use Case
# |
Action / Stimulus |
Reaction |
1 |
The user navigates to the assignment |
The system displays a panel specifically for Tracked Assignment Status |
2 |
The current state should be displayed predominately |
|
3 |
A grid of previous assignment states should be displayed. The grid should have the following fields: Status, Who (Person who created the Status), When (Date the status was changed), and a comment about the change if one is necessary |
|
4 |
User can change the assignment state by pressing a particular button |
The system reacts to these button presses to add the appropriate assignment status and any supporting information related to the state change |
Alternative / Additional Scenario:
# |
Action / Stimulus |
Reaction |
A1 |
User presses Assign button |
An assigner can press the Assign button and a Worker who realizes that an Assignment should actually be assigned to them or a different Worker. A means of entering a comment and a person to assign the assignment to. Simple grid edit may suffice. The date should not be editable since the assignment is taking place at the time the assign button is pressed. Assignments may be assigned to a department and an individual worker may choose to accept the assignment. |
A2 |
Worker presses Hold button |
A worker presses this to indicate to other users that the assignment is on hold. On hold implies that the assignment is pending additional tasks or waiting for further input. |
A3 |
Worker presses Review button |
A worker presses this to indicate that she is currently reviewing the assignment, but has not actually begun any of the necessary work required to complete the task. |
A4 |
Worker presses In Process button |
A worker presses this to indicate that she is currently working on the task |
A5 |
Assigner presses Cancel button |
Only an assigner should cancel a task. Cancel doesn’t delete the task; it simply cancels the task. Other users may need to be notified, especially the assigned worker. |
A6 |
Assigner or Worker presses the Completed button |
A worker should press the complete button to indicate that they believe the task to be completed. An assigner can also press the completed button on an assignment if they believe the task to be completed as well. |
Alternative / Additional Scenario:
# |
Action / Stimulus |
Reaction |
B1 |
User Presses the Status History button |
This can toggle the visibility of the buttons related to the status history including the grid. This can allow someone to print an assignment from the browser with just including the current status. |
B2 |
||
B3 |
Alternative / Additional Scenario: Cancel
# |
Action / Stimulus |
Reaction |
C1 |
||
Notes:
Issues: