Use Case Statement
By Manuel Dennis III
Document Revision # |
Action Taken, Notes |
When? |
By Whom? |
0.1 |
|
|
|
Use Case
# |
Action / Stimulus |
Reaction |
1 |
User enters some keywords |
The keywords are parsed using a simple split function to create a list to construct a where clause that can be used to interrogate the Subject and all comment fields for Assignments. The Assignments should be scoped to the users role prior to the Query criteria. |
2 |
User selects a checkbox indicating what type of keyword search is to be performed. |
If the subject checkbox is selected, then the search will include the subject lines of each Assignment. If the comments checkbox is selected, then all of the Assignments comments will also be searched. The request subject line, and request comments should also have checkboxes to allow the user to search for assignments by finding information found in requests as well. |
3 |
User selects from the list of drop down lists which items they would additionally like to place into a query |
The system should construct targeted queries that check the ids for the specific tables that are related to the Assignment. The drop down lists should include: Requester, Department, Division, Category, Action, Machine, Status, Project, Location, Priority, Client, and Worker. |
4 |
User enters a date range by entering dates into two drop down lists that should check the Assignment change dates |
The system should construct a date range clause that can be used to narrow the returned Assignments based on the status change date. |
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: