Case Study: Auto-Parts Warehouse Management System Analysis

This case study presents a system analysis of an auto-parts warehouse management system. It begins with an introduction to the business scenario, outlining the need for a new warehouse management system to improve efficiency and competitiveness. The analysis details both functional and non-functional requirements, covering aspects such as inventory management, order processing, security, and documentation. The document includes a use case diagram, a model diagram, and an event-partitioned system model to visually represent the system's components and processes. The system aims to handle various warehouse operations like receiving orders, inventory control, order processing, and report generation. The analysis considers the integration of wireless communication devices for real-time operations. The document concludes with a list of references to support the analysis and findings. This assignment is designed to provide a comprehensive overview of the system analysis process in a real-world business context.

Running head: SYSTEM ANALYSIS
SYSTEM ANALYSIS
Name of the Student:
Name of the University:
Author Note:

1SYSTEM ANALYSIS
Table of Contents
Functional and Non-functional requirements.............................................................................2
Functional requirements.........................................................................................................2
Non-Functional Requirements...............................................................................................3
Use Case Diagram......................................................................................................................4
Model Diagram..........................................................................................................................4
Event-partitioned system model.................................................................................................5
References..................................................................................................................................6

2SYSTEM ANALYSIS
Functional and Non-functional requirements
Functional requirements
The functional requirements of the proposed system refer to the working functions of
this particular proposed system, which will have a beneficial helping hand towards the
specific success of the system meant for the upgrade of the warehouse.
As proposed by Jack Greig along with that of Daniel Cox have been under the
experience of the supplying the major city of Australia with all of the existing automobile
parts as a part of their business (Brückmann et al., 2019). However, referring to the current
existing system of management for the warehouse has not been completely up to the mark to
boost their ongoing business, hence a new system has been proposed by both of the owners to
compete within the same field of business with the other existing competitors in the market.
The new system related to the management of the warehouse system will have the
sole responsibility to manage the automobile parts present within the warehouse. This newly
proposed system will maintain as well as manage the stock of all the automobile parts kept
within the warehouse. This will put forward a great helping hand towards the improvement of
the functionality towards the existing business related to that of the automobile parts. The
new Warehouse Management System can be applied to keep a check as well as monitor all of
the automobile parts entering through the gate of the warehouse (Bjerkan & Øvstedal, 2018).
This new system will also maintain a separate database for the outgoing automobile parts, in
turn updating a separate record for the specific automobile parts, which have run out of stock
and need to be added back to the stock so that the demands of the retailers as well as the
customers are properly met.

3SYSTEM ANALYSIS
The new Warehouse Management system will also take into consideration the control
of the inventory, documentation related to the deliveries, packing of the orders as well as
reports related to that of the crystal.
Non-Functional Requirements
The Warehouse Management System that has been newly proposed has some of the
non-functional requirements that need to be taken into consideration as a measure of the
better working of the considered system.
The newly proposed system has the extra added features of security. Present at the
entrance as well as at the exit of the warehouse, is a sensor that will track as well as update
the records related to any of the automobile parts that is entering or exiting from the
warehouse (Afreen, Khatoon & Sadiq, 2016). This can provide a major part towards the
security of the warehouse.
The documentation has its existence related to all of the incoming along with the
outgoing automobile parts, which will help in keeping a track of all the parts that have run out
of stock and needs to be refilled (Ameller et al., 2019). This can play a major role in
maintaining the efficiency of the newly proposed system along with the increase of the
customer goodwill as well as the customer base.

4SYSTEM ANALYSIS
Use Case Diagram
Figure: 1- Use Case Diagram
(Source: Created By Author)

5SYSTEM ANALYSIS
Model Diagram
Figure: 2- Model Class Diagram
(Source: Created By Author)

6SYSTEM ANALYSIS
Event-partitioned system model
Figure: 3- Event Partitioned System Model Diagram
(Source: Created By Author)

7SYSTEM ANALYSIS
References
Afreen, N., Khatoon, A., & Sadiq, M. (2016). A taxonomy of software’s non-functional
requirements. In Proceedings of the second international conference on computer and
communication technologies (pp. 47-53). Springer, New Delhi.
Ameller, D., Franch, X., Gómez, C., Martínez-Fernández, S., Araujo, J., Biffl, S., ... &
Muccini, H. (2019). Dealing with Non-Functional Requirements in Model-Driven
Development: A Survey. IEEE Transactions on Software Engineering.
Bjerkan, K. Y., & Øvstedal, L. R. (2018). Functional requirements for inclusive
transport. Transportation, 1-22.
Brückmann, H., Waiss, A., Stix, M., & Matheis, I. (2019). Continuous, Platform-independent
Testing of Functional Requirements. ATZelectronics worldwide, 14(1-2), 34-37.