Auto Parts Warehouse Management System Development Project Report

This report provides a comprehensive analysis of an Auto Parts Warehouse Management System (WMS) development project. It begins by outlining the functional and non-functional requirements of the system, including user access levels, stock tracking, and reporting capabilities. The report then details the use cases for the system, such as login, stock management, and report generation, visualized through use case diagrams. A domain model class diagram is developed to analyze the objects required for system development. Finally, an event-partitioned system model is presented, encompassing all identified use cases. The project addresses the need for a more efficient WMS to handle dynamic procedures, inventory control, order processing, and real-time operations, transforming the warehouse into a competitive advantage for the auto-parts business.

Running head: AUTO PARTS WAREHOUSE MANAGEMENT SYSTEM DEVELOPMENT PROJECT
Auto Parts Warehouse Management System Development project
Name of the Student
Name of the University
Authors note

1AUTO PARTS WAREHOUSE MANAGEMENT SYSTEM DEVELOPMENT PROJECT
Functional requirements of the Warehouse management system
The system will be able to provide multiple access levels for the different users
working at the warehouse.
Only after the successful authentication process, the manager or the other employees
will be able to enter or modify the any stock details to the system.
The stock details in the proposed system must be updated accordingly whenever a
outward entry to the system is done.
In case of any return entry is to be entered in the system then the stocks should be
automatically updated whenever the reason is for the order is “cancelled order”.
The system must track the delivery of specific stock levels and respective reorder
level so that the system can generate an alert whenever some specific stock reaches the
lowest level.
The Admin or the managers who are using the system, must be able to generate
reports about the stock levels, every day delivery report for different stocks.
Non-Functional requirements of the Warehouse management
system
Reliability
The proposed system should be able to provide accurate stock status to the user who
is querying in a consistent manner. Any kind of inaccuracies or inconsistency in the data
must be taken car through the regular confirmation from the users so that the actual levels

2AUTO PARTS WAREHOUSE MANAGEMENT SYSTEM DEVELOPMENT PROJECT
match with the levels displayed by the system. The proposed system should enable the users
to successfully add any stock detail, pickup, or the stock return as provided by the user and
updated in accordance to the newly updated entities in the system.
Usability and Robustness
The proposed interface should have an interface that can be easily comprehended so
that the potential users can easily. The Users of the proposed system should not have to check
for the manual each time for using the system.
Security of data
With the growth of the internet, the vulnerability of the information system
connected to the internet becomes severe. Therefore, the system should ensure the security of
the data through some form of encryption through any type of breach.
Integrity
The system should be able to rollback any partially committed data to the system
whenever any kind of failure /system crash happens.
Use case for the warehouse management system
Login: The users of the system needs to login with correct credentials to use the
functionalities.
Track stock movement: The staff or the admin can manage the stocks that are
available in the warehouse.
Track stock status: The status of stocks if it has reached to the reordering level.

3AUTO PARTS WAREHOUSE MANAGEMENT SYSTEM DEVELOPMENT PROJECT
Update stock status: whenever the stock is replenished then the status of stock must be
changed by the warehouse staff.
Generate invoice and reports: The admin users of the system will be able to generate
the report related to the stock levels, delivery of the products and stock status.
Figure 1: Use cases for the proposed warehouse management system
Domain model class diagram
The following domain model is developed in order to analyse the required objects
while decompose the domain in multiple objects that are will be required for the development
of the system.

4AUTO PARTS WAREHOUSE MANAGEMENT SYSTEM DEVELOPMENT PROJECT

5AUTO PARTS WAREHOUSE MANAGEMENT SYSTEM DEVELOPMENT PROJECT
Event partitioned System model for the proposed system