Software Analysis

This document provides an analysis of the functional and non-functional requirements of an auto-parts warehouse management system. It includes a discussion of the proposed system, use case diagram, domain model class diagrams, and event partition system model.

Running head: SOFTWARE ANALYSIS
Software Analysis
Name of the Student:
Name of the University:

1SOFTWARE ANALYSIS
Table of Contents
Functional and non-functional requirements of auto-parts warehouse management system....2
Functional requirements:........................................................................................................2
Non-functional requitements:.................................................................................................3
Use Case Diagram......................................................................................................................4
Domain model class diagrams...................................................................................................5
Event Partition System Model...................................................................................................5

2SOFTWARE ANALYSIS
Functional and non-functional requirements of auto-parts warehouse
management system
Functional requirements:
The functional requirements of this particularly proposed system specifically refers to
the functions related to that of the working within this particular system that has been
proposed. All of these functional requirements provide with a specific helping hand towards
the specific success of the system specifically carrying the aim of upgrading the warehouse
management system.
As placed forward by Jack Greig as well as Daniel Cox, relating to their experience
over a long period of time, have been supplying the whole region of Australia with all of the
parts that have been related to that of the automobile along with that of the parts related to
this particular field. However, in reference to the prevalent system managing the whole of
activity taking place within this particular warehouse has not been up to the mark in
accordance to the boosting of the system (Bąk et al., 2016). As a result, a new system for the
management of the warehouse has been proposed to compete will all of the existing
businesses within this same field of automobile.
The new system related to that of the management system that has been proposed
consists of the prime responsibility to carry out with the management of the parts related to
that of the automobile present with the warehouse of the company. This updated warehouse
management system will have the responsibility of maintaining along with that of managing
the stock related to that of the automobile parts stocked inside the warehouse (Culler & Long,
2016). This will act as a prime helping hand towards the specific functionality of the business
dealing with that of the parts related specifically to the automobiles. The newly proposed

3SOFTWARE ANALYSIS
Warehouse Management System shall be applied to keep a constant monitoring upon all of
the parts present within the warehouse having the entry through the entrance of this particular
warehouse. Referring to this newly proposed system, there will also be a present maintenance
of a dedicated database consisting of all the information related to that of the outgoing as well
as the incoming parts related to that of the automobile (Sousa et al., 2017). In addition to this,
there will also be the maintenance of a separate database to keep a check upon the stock of
the automobile parts present within the warehouse, and sending notifications when some of
the parts run out of stock for the refilling.
Non-functional requitements:
Non-Functional
Requirements Description Example
Performance Define capacity, reliability
and speed of the proposed
system
 The system should be
highly responsive to
allow monitoring of
information repeatedly
(Sun, Wu & Chen, 2018).
 User interface must be
responsive that report
within 5 seconds.
Operational Define technical and
physical environments
 The proposed system
must ensure the working
of Microsoft
Accessibility.
Security Access permission to the
system
 Technicians can be able
to see their work
assignments itself.
 The system have all
available safeguards

4SOFTWARE ANALYSIS
from Trojan horses,
Worms, etc.
Use Case Diagram
Figure: 1- Use Case Diagram
(Source- Created By Author)

5SOFTWARE ANALYSIS
Domain model class diagrams
Figure: 2- Model Class Diagram
(Source- Created By Author)

6SOFTWARE ANALYSIS
Event Partition System Model
Figure: 3- Event-partitioned system model diagram
(Source- Created By Author)

7SOFTWARE ANALYSIS
References:
Bąk, K., Diskin, Z., Antkiewicz, M., Czarnecki, K., & Wąsowski, A. (2016). Clafer: unifying
class and feature modeling. Software & Systems Modeling, 15(3), 811-845.
Culler, D., & Long, J. (2016). A prototype smart materials warehouse application
implemented using custom mobile robots and open source vision technology
developed using emgucv. Procedia Manufacturing, 5, 1092-1106.
Sousa, T. C., Kelvin, L., Neto, C. D., & de Carvalho, C. G. N. (2017). A Formal Semantics
for Use Case Diagram Via Event-B. JSW, 12(3), 189-200.
Sun, X., Wu, C. C., & Chen, L. R. (2018, May). An Automated Warehouse Sorting System
for Small Manufacturing Enterprise Applying Discrete Event Simulation. In 2018 2nd
IEEE Advanced Information Management, Communicates, Electronic and
Automation Control Conference (IMCEC) (pp. 1597-1601). IEEE.