Use Case Statement
By
Manuel Dennis III|
Name |
Manage Request Machine Section |
|
Description |
Displays a list of machines that the Request affects |
|
Dependencies |
An Request and a list of machines must exist |
|
Scope |
To signify to a worker what machines the Request is for |
|
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 |
User views the machine section |
The system presents the user with a checkbox list of machines that the Request is related to |
|
2 |
The machine button is pressed |
The machine section visibility is toggled to help minimize information displayed when machine may not be relevant. |
|
3 |
Machine checkbox list population |
The list should be populated based on the users criteria as well as the requests list of checked machines. |
Alternative / Additional Scenario:
|
# |
Action / Stimulus |
Reaction |
|
A0 |
An all machines should be visible in the list |
To indicate that a particular Request effects all machines. |
|
A1 |
||
|
A2 |
||
|
A3 |
Alternative / Additional Scenario:
|
# |
Action / Stimulus |
Reaction |
|
B1 |
||
|
B2 |
||
|
B3 |
Alternative / Additional Scenario: Cancel
|
# |
Action / Stimulus |
Reaction |
|
C1 |
||
Notes:
Issues:
Future Enhancements:
o
Machine list will eventually be listed as a tree view. Example: All computers for Shared, would be a group listed under Covington, Telemarketing, Shared. Or it could be Covington, TAS, Covington, or Covington, TAS, Metairie.o
Be able to break out machines by assignment. Example: Request is to update all machines to Windows XP. One person could be assigned all machines in the Administration Building. Another person could be assigned all machines in the Operations Building.o
Be able for the Worker to check off in the Machine section, the machines that have been completed.