Other non-functional requirements Superordinates UC4 Developer GB, FL, CS Creation date / 6/1/2010; 6/7/2010 Last modified date Comments Note 1: allocator can view can see other statistics that would be helpful to view an allocation. The view would be similar to diagram DUC3 except the allocation’ values would be left to fill in by the allocator. This ‘proposed allows allocators to store and item performance (feature 13) ‘rank’ USE CASE UC6 USE CASE Name Delete allocation Relating Feature 16 ACTOR(s) Allocator Description Displays the process the allocator goes through to delete an allocation Preconditions Allocator is logged into the system Allocator has had his view filters set up Postconditions An allocation has been deleted The PO(s) or PO’s line status has been changed to ‘unallocated’ The PO or PO’s line(s) appear from the allocations’ page ‘open The PO or PO’s disappear from the POs’ page ‘allocated The ERP system has been updated: items are unallocated Data is sent to distribution center spelling out the PO’s are no longer assigned to any store A store’s merchandise for that product is updated to reflect “need” product is no longer assigned Trigger Allocator selects allocation’ from main portal page and upon viewing ‘manage the PO’s’ list, he/she changes the view to PO’s’ via a ‘unallocated ‘allocated drop down menu Included Use Cases NA Extending Use Cases NA MAIN SUCCESSFUL Actor Action System Action SCENARIO 1.) Based on allocator’s view filters, a list of allocations are listed along with the date the allocation was made, the relating PO’s, the relating products. Next to each allocation is an update button and a delete button. (see diagram DUC5)
Other non-functional requirements Superordinates UC4 Developer GB, FL, CS Creation date / Last modified date 6/1/2010; 6/7/2010 Comments Note 1: allocator can view can see other statistics that would be helpful to view an allocation. The view would be similar to diagram DUC3 except the ‘proposed allocation’ values would be left to fill in by the allocator. This allows allocators to ‘rank’ store and item performance (feature 13) USE CASE UC6 USE CASE Name Delete allocation Relating Feature 16 ACTOR(s) Allocator Description Displays the process the allocator goes through to delete an allocation Preconditions Allocator is logged into the system Allocator has had his view filters set up Postconditions An allocation has been deleted The PO(s) or PO’s line status has been changed to ‘unallocated’ The PO or PO’s line(s) appear from the ‘open allocations’ page The PO or PO’s disappear from the ‘allocated POs’ page The ERP system has been updated: items are unallocated Data is sent to distribution center spelling out the PO’s are no longer assigned to any store A store’s merchandise “need” for that product is updated to reflect product is no longer assigned Trigger Allocator selects ‘manage allocation’ from main portal page and upon viewing the ‘unallocated PO’s’ list, he/she changes the view to ‘allocated PO’s’ via a drop down menu Included Use Cases NA Extending Use Cases NA MAIN SUCCESSFUL SCENARIO Actor Action System Action 1.) Based on allocator’s view filters, a list of allocations are listed along with the date the allocation was made, the relating PO’s, the relating products. Next to each allocation is an update button and a delete button. (see diagram DUC5)