Detailed System Modelling Report: Auto-Parts Warehouse Management

This report presents a detailed system modelling analysis for an auto-parts warehouse management system. It begins by outlining the functional and non-functional requirements, crucial for the system's operation and performance. The report then proceeds to illustrate the system's architecture through a use case diagram, depicting the interactions between actors and the system's functionalities. A domain model class diagram is included to represent the system's data structure and relationships. Finally, an event-partitioned system model is developed to capture the dynamic behavior of the system, encompassing all identified use cases and their interactions. The report concludes with a bibliography of cited sources.

Running head: SYSTEM MODELLING
SYSTEM MODELLING
Name of student
Name of university
Author’s note:

1
SYSTEM MODELLING
Table of Contents
Functional and non-functional requirements.................................................................2
Functional requirements.............................................................................................2
Non-functional requirements.....................................................................................3
Use case diagram............................................................................................................4
Domain model class diagram.........................................................................................5
Event partitioned system model.....................................................................................6
Bibliography...................................................................................................................7

2
SYSTEM MODELLING
Functional and non-functional requirements
Functional requirements
The functional requirements of the Autoparts warehouse management system could
be listed as:
 The software provides the simplification of order processing and warehouse
management. The managers could login into the system for accessing the data and the
employees could also login into the system for gaining the location about the storage
location in the warehouse. The new employees are required to be registered in the
system before they could access the system.
 The data of the warehouses are managed in the database of the software that provides
the access to the appropriate users whenever it is required. The data handling would
be increased significantly.
 Only the manager level employees have the access to the warehouse data and they
could access this data for making better informed decisions.
 The software should be integrated with all the warehouses of the organisation for
accessing the data regarding any free spaces in the warehouses. It would help in
syncing all the warehouses using a common platform.
 It is required from the system that is passes the section 508 accessibility requirement.
 The data that is to be maintained in the system is the warehouse data that provides the
idea about the present storages spaces in all the warehouses of the organisation.
 The employee prompts the system for login and the system displays the login screen.
If the employee is new, then it is required that the employee is first registered in the
system.

3
SYSTEM MODELLING
 When the employee is logged in into the system, they could view the data of the
inventory of their respective department and if the inventory of the product is low,
then the request for re-stocking could be entered in the system.
 The output of the system is required to be the data about the inventory in the
warehouse, the storage spaces within the overall warehouse and data of the employees
who are working in the warehouses.
Non-functional requirements
 The users are required to change the default password instantly afterwards the
successful first login.
 The initial username and the password provided should never be reused in the future
for login into the system.
 The employees are never allowed to update the information regarding their salary.
These kinds of attempts must be reported instantly to any of the security
administrator.
 Each unsuccessful attempt by any user for accessing any item of data is required to be
recorded on the audit trail.
 The system should be allow the synchronisation with other warehouse software of the
organisation for handling the data regarding all the warehouse storage space available.
 Only the authorised users of the manager data can access the system for viewing the
reports.
 The main access permissions for the system data might solely be changed by the data
administration of the system.
 When any modification is done in the profile of the employees, then they would
receive a message in their mobiles regarding the details of the changes that are made.

4
SYSTEM MODELLING
Use case diagram

5
SYSTEM MODELLING
Domain model class diagram
Event partitioned system model

6
SYSTEM MODELLING

7
SYSTEM MODELLING
Bibliography
Hernández-Rodríguez, S., Hernández-Lira, C. A., Aguilar-Rico, A., Flores-Becerra, G.,
Flores-Méndez, J., & Vázquez-Cuchillo, O. (2016). A recommender system applied to
the indirect materials selection process (RS-IMSP) for producing automobile spare
parts. Computers in Industry, 82, 233-244.
Jayanth, S., Poorvi, M. B., & Sunil, M. P. (2017). Inventory management system using IoT.
In Proceedings of the First International Conference on Computational Intelligence
and Informatics (pp. 201-210). Springer, Singapore.
Safa, M., Shahi, A., Haas, C. T., & Hipel, K. W. (2014). Supplier selection process in an
integrated construction materials management model. Automation in
Construction, 48, 64-73.
Zhai, Y. (2017). 3. The Establishment of ERP System to Support Management and Control
Mode of the Group. Revista de la Facultad de Ingeniería, 32(8).