Finishing Touch Furniture Store
Monique BrownReginald Campbell
Michael CosbyJa’Derekica Graham
Richard Luker
Warehouse Systems Analysis
May 3, 2011CS470-Systems AnalysisDr. D. Yessick
Analysis Content
ᴥ Use Cases ᴥ Use Case Narrativesᴥ Class Diagramsᴥ Prototype•HTML
RECEIVING SUBSYSTEM
Key In Received Inventory
Prompt Storage Locations for
Received Items
Confirm Invoice from Purchasing
Confirm Transfer
Prompt Items for Transfer
Load items for Transfer/Remove from
Inventory
TRANSFER SUBSYSTEM
DELIVERY SUBSYSTEM
Request Item Delivery
Load Items for DeliveryRemove
Items from Inventory
Prompt Items for Delivery
Warehouse Manager
Store Manager
Warehousing Staff
Warehouse Staff
Warehousing Staff
Confirm Delivery
Warehouse Manager
Request Transfer
(Requesting) Warehous e Manager
Receiving Subsystem
Key In Received Inventory
Prompt Storage Locations for
Received Items
Confirm Invoice from Purchasing
Warehouse Manager
RECEIVING SUBSYSTEM
Warehouse Staff
Use Case Name Key In Received Inventory USE CASE TYPE
Primary Business Actor Warehouse StaffBusiness Requirements: Systems Analysis: X
Primary System Actor Warehouse Staff
Other Participating Actors Warehouse ManagerDescription This use case describes the event of a warehouse employee
keying in received inventory ultimately updating the overall inventory within the warehouse.
Precondition
The warehouse employee must enter ID number to access area of the warehouse system.
Trigger
Inititated once the warehouse manager has confirmed item accceptance to warehouse.
Typical Course of EventsActor Action System Response
Step 1: Warehouse staff keys in new inventory. Step 3: Warehouse staff updates inventory.
Step 2: System assigns ID numbers for items. Step 4: System prompts stroage locations.
Conclusion
This use case concludes once item are designated to storage locations.
Use Case Name Prompt Storage Locations for Received ItemsUSE CASE TYPE
Primary Business Actor Warehouse StaffBusiness Requirements: Systems Analysis: X
Primary System Actor Warehouse Staff
Other Participating ActorsDescription This use case describes the event of a warehouse employee
checking storage locations for items to be placed.
Precondition
The warehouse employee must enter ID number to access area of the warehouse system.
Trigger
Initiated once the items have been confirmed of acceptance by the warehouse manager.
Typical Course of EventsActor Action System Response
Step 1: Warehouse employee keys in new inventory. Step 3: Warehouse employees checks for storage locations.
Step 2: System updates inventory. Step 4: System checks for available storage.
Conclusion
This use case concludes once items have been stored.
Use Case Name Confirm Invoice from Purchasing
USE CASE TYPE
Primary Business Actor Warehouse ManagerBusiness Requirements: Systems Analysis: X
Primary System Actor Warehouse Manager
Other Participating Actors Purchasing Description This use case describes the event of the warehouse receiving and
confirming the invoice sent by purchasing in order to pass into inventory.
Precondition
The warehouse manager must provide vendor ID number.Trigger
Initiated once invoice has been recevived by the warehouse manager.
Typical Course of EventsActor Action System Response
Step 1: Purchasing sends invoice to warehouse manager. Step 3: Manager confirms invoice.
Step 2: System prompts manager confirmation. Step 4: System prompts items to be keyed into inventory.
Conclusion
This use case concludes once the warehouse manager instructs warehouse staff to start locating items for loading.
Transfer Subsystem
Confirm Transfer
Prompt Items for Transfer
Load items for Transfer/Remove from Inventory
Warehouse Manager
TRANSFER SUBSYSTEM
Warehousing Staff
(Requesting) Warehouse Manager
Request Transfer
Use Case NamePrompt Items For Transfer USE CASE TYPE
Primary Business ActorWarehouse Staff
Business Requirements: Systems Analysis: X
Primary System ActorWarehouse Staff
Other Participating Actors
Warehouse Manager (Requesting) Warehouse Manager
Description This use case describes the event of a neighboring warehouse manager requesting the transfer of item from our warehouse.
Precondition
The warehouse employee must enter ID number to access area of the warehouse system.
Trigger
Initiated once neighboring warehouse manager requests transfer. Typical Course of Events
Actor Action System ResponseStep 1: Neighboring Warehouse requests transfer of items. Step 3: Warehouse employees prompt items for transfer. Step 5: Warehouse manager confirms transfer.
Step 2: System updates transfer inquiries. Step 4: System displays storage locations. Step 6: System removes items from inventory.
Conclusion
This use case concludes once the storage locations have been located and removed from inventory.
Use Case Name Load Items for Transfer/Remove from Inventory
USE CASE TYPE
Primary Business Actor Warehouse StaffBusiness Requirements: Systems Analysis: X
Primary System Actor Warehouse Staff
Other Participating Actors Description This use case describes the event of the warehouse staff
removing the items for transfer and updating the overall inventory.
Precondition
The warehouse employee must enter ID number to access area of the warehouse system.
Trigger
Initiated once items have been prompted and located in storage. Typical Course of Events
Actor Action System ResponseStep 1: Warhouse staff prompts items for transfer. Step 3: Warehouse staff updates inventory.
Step 2: System gathers item ID's and storage information. Step 4: System removes items and updates inventory.
Conclusion
This use case concludes once the items are removed from inventory.
Use Case Name Confirm Transfer USE CASE TYPE
Primary Business Actor Warehouse ManagerBusiness Requirements: Systems Analysis: X
Primary System Actor Warehouse Manager
Other Participating Actors (Requesting) Warehouse ManagerDescription This use case describes the event of the Finishing Touch
warehouse manager and the neighboring warehouse manager confirming the requested transfer of items.
Precondition
The warehouse employee must enter ID number to access area of the warehouse system.
Trigger
Initiated when order arrives and invoice from purchasing is confirmed by warehouse manager.
Typical Course of EventsActor Action System Response
Step 1: Warehouse staff removes items and updates inventory. Step 3: Both managers confirm by providing IDs.
Step 2: System updates inventory/prompts confirmation. Step 4: System receives confirmation and completes tranfer log.
Conclusion
This use case concludes once requesting warehouse manager receives transfer confirmation.
Use Case Name Request Transfer USE CASE TYPE
Primary Business Actor (Requesting) Warehouse Manager
Business Requirements: Systems Analysis: X
Primary System Actor (Requesting) Warehouse Manager
Other Participating ActorsDescription This use case describes the event of a neighboring warehouse
manager requesting items for transfer from our warehouse.
Precondition
The warehouse employee must enter ID number to access area of the warehouse system.
Trigger
Initiated when neighboring warehouse manager requests transfer.
Typical Course of EventsActor Action System Response
Step 1: Neighboring warehouse manager requests transfer. Step 3:Both managers confirm transfer.
Step 2: System updates transfer inquiries. Step 4: System sends transfer confirmation to neighboring warehouse manager.
Conclusion
The use case concludes once transfer confirmation is sent to neighboring warehouse manager.
Delivery Subsystem
DELIVERY SUBSYSTEM
Request Item Delivery
Remove Items from Inventory
Prompt Selected Items
for Delivery
Store Manager
Warehousing Staff
Confirm Delivery
Warehouse Manager
Use Case Name Request Item DeliveryUSE CASE TYPE
Primary Business Actor Store Manager
Business Requirements: Systems Analysis: X
Primary System Actor Store Manager
Other Participating ActorsDescription This use case describes the event of a store manager requesting items for
delivery to his store location.
Precondition
The warehouse employee must enter ID number to access area of the warehouse system.
Trigger initiated when store manager requests items for delivery. Typical Course of Events
Actor Action System ResponseStep 1: Store manager requests delivery of items. Step 3: Warehouse manager confirms delivery.
Step 2: System updates delivery inquiries. Step 4: System sends delivery confirmation.
Conclusion
This use case concludes when store manager receives delivery confirmation.
Use Case Name Load Items for Delivery/Remove from Inventory
USE CASE TYPE
Primary Business Actor Warehouse StaffBusiness Requirements: Systems Analysis: X
Primary System Actor Warehouse Staff
Other Participating ActorsDescription This use case describes the event of the warehousing staff
removing items from inventory and loading them for delivery.
Precondition
The warehouse employee must enter ID number to access area of the warehouse system.
Trigger Initiated once items have been requested for delivery. Typical Course of Events
Actor Action System ResponseStep 1: Warehouse staff prompts items for delivery. Step 3: Warehouse staff updates inventory.
Step 2: System gathers item ID's and storage information. Step 4: System removes items and updates inventory.
Conclusion
The use case concludes once inventory has been updated and items are loaded for delivery.
Use Case Name Prompt Items for Delivery USE CASE TYPE
Primary Business Actor Warehouse StaffBusiness Requirements: Systems Analysis: X
Primary System Actor Warehouse Staff
Other Participating Actors Warehouse ManagerDescription This use case describes the event of items within the warehouse
inventory being prompted for delivery to a store.
Precondition
The warehouse employee must enter ID number to access area of the warehouse system.
Trigger
Initiated once the request from the stroe manager has been received.
Typical Course of EventsActor Action System Response
Step 1: Request from store manager gets to warehouse. Step 3: Warehouse staff checks for items andthier sotrage areas.
Step 2: System updates delivery inquiries. Step 4: System provides storage areas and item IDs.
Conclusion
This use case concludes once system has given item IDs and displayed the locations of the items.
Use Case Name Confirm Delivery USE CASE TYPE
Primary Business Actor Warehouse StaffBusiness Requirements: Systems Analysis: X
Primary System Actor Warehouse StaffOther Participating Actors Store Manager
Warehouse Manager
Description This use describes the event of a delivery being confirmed by the store manager and the warehouse manager of Finishing Touch.
System ResponsePrecondition
The warehouse employee must enter ID number to access area of the warehouse system.
Step 2: System updates delivery inquiries. Step 4: System checks ID numbers. Step 6: Inventory is updated.
Trigger
Initiated when store manager requests delivery of items from the warehouse.
Typical Course of EventsActor Action
Step 1: Store manager requests delivery. Step 3: Items are prompted for delivery. Step 5: Warehouse manager confirms delivery.
Conclusion
This use case is concluded once the store manager receives a delivery confirmation.