Assignment 2: Requirements Gathering AssignmentTutorOnline | Good Grade Guarantee!
SCHOOL OF COMPUTING AND MATHS, CHARLES STURT UNIVERSITY
Assignment 2: Requirements Gathering
Auto-Parts Warehouse Management System
1.1 Functional Requirements
1.1.1 Order Receiving–The Order Receiving subsystem will allow the ability for customers and sales representatives to search for items in the product catalogue and place orders. Additionally, product comments and ratings will be available to be viewed for each product item. Finally, managers can use historic order details to generate useful reports such as order summaries and trends.
1.1.2Inventory Management–The Inventory Management subsystem will allow warehouse staff to search, update and adjustinventory item details and stock quantities. Additionally, warehouse staff can use stationary and handheld RFID scanners and printers to manage inventory items. Lastly, managers can add new items to the inventory, re-order low stock and generate reporting data. These re-order processes willautomatically notify suppliers for efficient re-stocking processes.
1.1.3 Order Processing–TheOrder Processing subsystem willinclude the automatic generation and allocation of invoices and receipts, as well as providing customers the abilityto payfor items using recurring transactions. Banks and Credit Bureaus will also be notified when orders are updated, and transactions are processed. Finally, accountants and managers will be able to generatetransaction and order summary reports.
1.1.4Item Picking –ThePicking subsystem will automatically allocate resources, such as robotic or staff pickers, to process item picking requests. Picking processes will be integrated with stationary and handheld RFID printers and scanners, as well as Pick-to-Voice and Pick-to-light systems to further facilitateefficient picking processes.
1.1.5 Order Load Management – The Order Load Management subsystem will provide functions to automatically plan, manageand optimise freighttransportation routes. Automatic calculation of load weight, volume and expected fuel cost will also be provided.
1.1.6 Outbound Documentation – Outbound Documentationwill be provided to streamline order dispatch processes. Automated electronic dispatch notes will be generatedand includesubmission workflows and user allocation. Customers will also be notified when order items are dispatched and will receive electronic Proof Of Delivery receipts when fulfilment is complete.
1.1.7Order Packing Subsystem – The Packing subsystemwill automatically allocatepacking resources, include staff and robotic packers, to item packing worklists. Packing processes will also include Kit packing functionality, which will group and pack multiple inventory items together for as a single order item.Finally, customers will be automatically notified once their order has completed packing and is ready for delivery.
1.1.8 System Notifications – The Warehouse Management System will provide automated and event driven system notifications to alert when specified conditions are triggered. Once triggered, notifications are allocated to designated staff for resolutions, and can be assigned to different staff as required.
1.1.9 Crystal Reports – The Reporting Subsystem will utilise Crystal Reports to allow both manual and scheduled report generation. Staff will be notified when reports are available for viewing and can send them to other users in the system.
1.2 Non-Functional Requirements
1.2.1 Usability – Firstly, the Warehouse Management System must not be difficult to learn or operate[ CITATION Cal l 3081 ]. User processes such as manual data entry, record accessing and navigation should be completedas quickly as possiblewith little or no user errors[ CITATION Usa l 3081 ]. The success of this requirement will be measured by survey responses from key stakeholders regarding their average time spend learning the system [ CITATION Cal l 3081 ].
1.2.2 Reliability – The system reliability, including both hardware and software components, must meet an acceptable ‘mean time to failure’ rate as defined by the relevant system testing stakeholders.These benchmarks will be defined using IEEE Reliability Society guidelines and recommendations.
1.2.3 Performance – System performance will be measured byresponse time, transaction rates and throughput[ CITATION Cal l 3081 ]. Response time must meet acceptable benchmarks as defined by stakeholders during User Acceptance Testing. Transaction rates and system throughput will be measured asthe total amount of items processed by the system over a 24 hour period[ CITATION Thr19 l 3081 ].
1.2.4 Security –To ensure secure safe and secure data, the system must provide layered protectionincludinguser level access controls, authorisation and encryption[ CITATION Sma19 l 3081 ]. Additionally, the system must meet industry and compliance auditing standards [ CITATION Boo16 l 3081 ], provideMultifactor and Single Sign-Onauthentication anduse ‘Least Privilege’authorisation practices[ CITATION Hac17 l 3081 ].
1.2.5 Interface Requirements – The systemmust provide full integration withthe identified sub-systems, the ERP finance system and Transport Management System. Additionally, hardware integration with devices such as stationary and handheld RFID printers and scanners, Proof of Delivery (POD) devices, and automated picking and packing robotics must be provided.
1.2.6 Design Constraints – The Warehouse Management system should operate in a cloud environment accessed via standard web browsers such as Microsoft Edge and Google Chrome. Physical hardware requirements should not exceed a 2.5GHz processor, 16gb of local hard drive storage and 8gb RAM.
1.2.7 Effectiveness–The system must includefeatures to help the business improve theiroverall efficiency[ CITATION Tra l 3081 ]. This functionality should include automated processessuch as the prioritisation and sequencing of item picking, the planning and organisations of transportation routes, and the calculation ofexpected load weight, volume and fuel cost. Additionally, the system should enforce rigorous data integrity processes, while maintaining high item processing throughput levels.
2. Use Case Diagrams
Figure 2.1. Use Case Diagram of the Order Receiving Subsystem
Figure 2.2. Use Case Diagram of the Inventory ManagementSubsystem
Figure 2.3. Use Case Diagram of the Order Processing Subsystem
Figure 2.4. Use Case Diagram of the Order Picking Subsystem
Figure 2.5. Use Case Diagram of the Order Load Management Subsystem
Figure 2.6. Use Case Diagram of theOutbound Documentation Subsystem
Figure 2.7. Use Case Diagram of theNotification Subsystem
Figure 2.8. Use Case Diagram of thePacking Subsystem
Figure 2.9. Use Case Diagram of theReporting Subsystem
3. Domain Model Class Diagrams
Figure 3.1.Domain Model Class Diagram of theOrder Receiving Subsystem
Figure 3.2.Domain Model Class Diagram of theInventory Management Subsystem
Figure 3.3.Domain Model Class Diagram of theOrder Processing Subsystem
Figure 3.4.Domain Model Class Diagram of thePicking Subsystem
Figure 3.5.Domain Model Class Diagram of theOrder Load Management Subsystem
Figure 3.6.Domain Model Class Diagram of theOutbound Documentation Subsystem
Figure 3.7.Domain Model Class Diagram of the Notification Subsystem
Figure 3.8.Domain Model Class Diagram of thePacking Subsystem
Figure 3.9.Domain Model Class Diagram of theReporting Subsystem
4. Event-Partitioned System Models
Figure 4.1.Event-partitioned system model diagram of theOrder Processingsubsystem
Figure 4.2.Event-partitioned system model diagram of theInventory Managementsubsystem
Figure 4.3.Event-partitioned system model diagram of theOrder Processing subsystem
Figure 4.4.Event-partitioned system model diagram of thePicking subsystem
Figure 4.5.Event-partitioned system model diagram of theOrder Load Management subsystem
Figure 4.6.Event-partitioned system model diagram of theOutbound Documentation subsystem
Figure 4.7.Event-partitioned system model diagram of theNotification subsystem
Figure 4.8.Event-partitioned system model diagram of thePacking subsystem
Figure 4.9.Event-partitioned system model diagram of theReporting subsystem
Boote, J. (2016, June 6). Are you making software security a requirement? Retrieved from Synopsys: https://www.synopsys.com/blogs/software-security/software-security-requirements/
California Polytechnic State university. (n.d.). Non-functional Requirements. Retrieved from Department of Computer Sceience and Software Engineering: http://users.csc.calpoly.edu/~jdalbey/SWE/QA/nonfunctional.html
Hack2Secure. (2017, March 03). Security Requirement CheckList Considerations in Application Development. Retrieved from Hack2Secure: https://www.hack2secure.com/blogs/security-requirement-checklist-considerations-in-application-development
Smart by GEP. (2019, April 22). The Inventory Management Software Checklist: 9 Must-Have Features. Retrieved from Smart by GEP: https://www.smartbygep.com/blog/inventory-management-software-features-checklist
TradeGecko. (n.d.). Why use order processing software? Retrieved from TradeGecko: https://www.tradegecko.com/blog/inventory-management/why-use-order-processing-software
Usability First. (n.d.). Requirements Specification. Retrieved from Usability First: http://www.usabilityfirst.com/about-usability/requirements-specification/
Weibull. (2019). Throughput Analysis (Part I). Retrieved from Weibull: https://www.weibull.com/hotwire/issue27/relbasics27.htm
QUALITY: 100% ORIGINAL – NO PLAGIARISM.
- **REMEMBER TO PRECISE PAGE NUMBER**
- Hit The Order Button To Order A **Custom Paper**