Use Case Statement
By
Manuel Dennis III
Name |
Manage Assignment Estimate Section |
Description |
A section to display the Estimates for when the Assignment is to be completed |
Dependencies |
A request and assignment must exist |
Scope |
To keep track and display estimate information related to an assignment |
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 |
Assigner, Approver, or Worker enters their estimate |
The system simply tracks estimates to help managers adjust estimates for future assignments |
2 |
Assigner enters a expected completion date and estimated hours |
This date is a pie in the sky estimate, and they should enter a numeric value indicating the number of hours they feel the task should be accomplished in |
3 |
Approver enters her own estimate |
This value should be more meaningful and have some sort of historical track record. |
4 |
Worker enters her estimate |
The worker should enter this estimate before beginning any work. The estimate should not change after the user changes the state to in process. The recommended procedure would be for the worker to estimate, set the Assignment status to Review, re-estimate after getting further information about the assignment, then enter the new estimate if different, then set the status to In Process. |
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: