Functional and Non-Functional Requirements of Warehouse Management System

This document discusses the functional and non-functional requirements of a warehouse management system. It covers topics such as usability, reliability, performance, supportability, packaging, and implementation. The document also includes a use case diagram, domain model class diagram, and event-partitioned diagram.

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 of Warehouse Management System..........2
Functional Requirements:................................................................................................2
Non-functional requirements:..........................................................................................2
Use Case Diagram...............................................................................................................5
Domain Model Class Diagram............................................................................................6
Event- Partitioned Diagram.................................................................................................7
References............................................................................................................................8

2SYSTEM ANALYSIS
Functional and Non-Functional Requirements of Warehouse Management
System
Functional Requirements:
Warehouse Management System aims in giving an effective interface for users which is
required for managing warehouse. It will provide the user with list of option which is required
for managing the inventory by making use of a different function (Atieh et al., 2016). The
provided ingredients are monitored on regular basis for its usage and analyzed for threshold
values in inventory. The design has been done in such a way that user does not require manually
update the warehouse system every time. In addition, the system calculates and analyses the
amount of specific set days which is set by admin (Madurapperuma et al., 2018). Simple
interface of the system comes up with a list of function like removing, updating and recipe. Also,
it has certain function for removing the vendor, threshold value and lastly processing of orders.
Non-functional requirements:
There is list of function for understanding the non-functional requirements of the system
like
Usability
 System should be very much convenient to be used by both managers and accountant so
that they do not require any extra manual for it.
 The system should be simple in such a way that it can deliver all the required data and
relationship.

3SYSTEM ANALYSIS
 Menu on the system should be easily navigable by user and buttons that are very much
easy to understand.
Reliability
 System requires to be accurate for providing inventory status to user on continuous basis.
 System should provide the option of password based login where user can avoid any kind
of changes in foreign entity in data system.
 System should not process any kind of data for failed processes in the database
Performance
 The proposed warehouse management system should not lag as the workers do not have
the time for completing the action.
 There is need of complete updating of database, ingredients, occasions and vendors in
successful way for user (Lee et al., 2018). This is to be done for each and every time for
user request for each process.
 All the required calculation is done by system which should be comply as per the norms
of the system.
Supportability
 The proposed system required to be designed in such a way so that it can work on system
that have even minimum configuration.
 Data can be easily exported to managers so that it can make the system much more
portable.
Packaging

4SYSTEM ANALYSIS
 Software needs to be have certain number of license which is required for key
authentication process (Goudarzi, Malazi & Ahmadi, 2016).
 Packaging should come up with manual that has all the detail of system and instruction of
the program.
Implementation
 The proposed system is completely build on Microsoft Visual Studio 2010.
 All the required programing is done in it.
 Implementation of database is done in Microsoft access
 Connection in between two that is database and system is done by making use of ODBC
connection in the hands of visual studio.

5SYSTEM ANALYSIS
Use Case Diagram
Fig 1: USE case diagram of Warehouse Management System
(Source: Created by Author)

6SYSTEM ANALYSIS
Domain Model Class Diagram
Fig 2: Domain Class Diagram for Warehouse Management System
(Source: Created by Author)

7SYSTEM ANALYSIS
Event- Partitioned Diagram
Fig 3: Data Flow Diagram for Warehouse Management System
(Source : Created by Author)

8SYSTEM ANALYSIS
References
Atieh, A. M., Kaylani, H., Al-abdallat, Y., Qaderi, A., Ghoul, L., Jaradat, L., & Hdairis, I.
(2016). Performance improvement of inventory management system processes by an automated
warehouse management system. Procedia Cirp, 41, 568-572.
Goudarzi, P., Malazi, H. T., & Ahmadi, M. (2016). Khorramshahr: A scalable peer to peer
architecture for port warehouse management system. Journal of Network and Computer
Applications, 76, 49-59.
Lee, C. K. M., Lv, Y., Ng, K. K. H., Ho, W., & Choy, K. L. (2018). Design and application of
Internet of things-based warehouse management system for smart logistics. International
Journal of Production Research, 56(8), 2753-2768.
Madurapperuma, S., Ebert, L. J., Gamage, S., & Kuruppuarachchi, D. (2018, February). In-house
development & implementation of ‘corebrain’warehouse management system: a case study.
In About the 2nd International Conference in Technology Management, iNCOTeM 2018 (p. 67).