System Analysis

This document provides an analysis of a warehouse management system, including its functional and non-functional requirements. It also includes use case diagrams, domain model class diagrams, and event-partition diagrams. The document discusses the main user of the system, the functions it provides, and the security, performance, and availability requirements. References are provided for further reading.

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 Requirement of the System..............................................2
Use cases Diagram...............................................................................................................4
Domain Model class Diagram.............................................................................................5
Event- Partition Diagram.....................................................................................................6
References............................................................................................................................7

2SYSTEM ANALYSIS
Functional and Non-Functional Requirement of the System
Warehouse management system (WMS) is defined as a software application which helps
in easy control and managing day to day operations in the warehouse. The software will help in
guiding inventory and putting (Eckhardt, Vogelsang & Fernández, 2016). In addition, it helps in
optimizing picking, shipping of different products. It is a standalone application which is a part
of an ERP system.
The main user of this warehouse management system is warehouse manager,
administrator. By the help of this system, user can have easy access to tracking goods,
information to managers. Warehouse Management System will provide some of the function like
online sales and key requirements for updating item details and price form (Khan et al., 2016).
Warehouse Manager can have a receipt and print the bill like a reference for a purchased item.
Warehouse manager can easily have report from different salesperson about the particular item
not available in the warehouse. In addition, administrator can easily add new user into the
system.
Functional requirements: It merely highlights a specific kind of function which the
system and its components can perform a range of function. The main goal of this particular
system is all about increasing the sales by creating a record of stock, details, sellers and
department store.
Requirement Name Requirement Description
Log In This particular function will help the
salesperson, warehouse manager and
administrator to easily log into the system

3SYSTEM ANALYSIS
(Kurtanović & Maalej, 2017).
Change in Password This particular function will help the
salesperson and warehouse manager for
changing the password.
View Status This function will help the salesperson to
track the current status of the order.
Receipt Cancellation This particular function will help the sales to
keep a track of receipt.
Search Item It will help the salesperson for searching any
particular item
Check Stock It will help the stockperson for checking
stock in the warehouse.
Validating Report This function will help the warehouse
manager to easily validate a report
Generating Report This function will help warehouse manager
to easily generate trends.
Nonfunctional Requirements: Both inventory and administrator can easily access the
account on any instance that is 24 hours of day (Khan et al., 2016). The non-functional
requirement of a warehouse management system is given below like
Security: The system needs to be protected from the unauthorized user which is achieved
by the help of username and password. In addition, the system will highlight any error if the

4SYSTEM ANALYSIS
provided user and password is incorrect (Mahmoud & Williams, 2016). For using the system,
each and every user needs to have a login key for username and password.
Performance: The time required for process and response for the key user which is
needed for identification of username and password (Eckhardt, Vogelsang & Fernández, 2016).
It is expected that project provides response in an interval less than 2 seconds.
Availability: Warehouse management system is stand-alone system that comes up with
four to five user. With the operating hours, the user can use the warehouse management system.
Use cases Diagram

5SYSTEM ANALYSIS
Fig 1: Use Case Diagram
(Source: Created by Author)
Domain Model class Diagram
Fig 2: Domain Model Class Diagram of Warehouse Management System

6SYSTEM ANALYSIS
(Source: Created by Author)
Event- Partition Diagram
Fig 3: Data Flow Diagram of Warehouse Management System
(Source: Created by Author)

7SYSTEM ANALYSIS
References
Eckhardt, J., Vogelsang, A., & Fernández, D. M. (2016, May). Are" non-functional"
requirements really non-functional? an investigation of non-functional requirements in practice.
In 2016 IEEE/ACM 38th International Conference on Software Engineering (ICSE) (pp. 832-
842). IEEE.
Khan, F., Jan, S. R., Tahir, M., Khan, S., & Ullah, F. (2016). Survey: dealing non-functional
requirements at architecture level. VFAST Transactions on Software Engineering, 9(2), 7-13.
Kurtanović, Z., & Maalej, W. (2017, September). Automatically classifying functional and non-
functional requirements using supervised machine learning. In 2017 IEEE 25th International
Requirements Engineering Conference (RE) (pp. 490-495). IEEE.
Mahmoud, A., & Williams, G. (2016). Detecting, classifying, and tracing non-functional
software requirements. Requirements Engineering, 21(3), 357-381.