Warehouse Management System Analysis: PG Assessment Item 2

Desklib provides solved assignments and past papers to help students succeed.

SYSTEM ANALYSIS PG ASSESSMENT ITEM 2

Table of Contents
Introduction......................................................................................................................................3
Architecture and Design of Warehouse Management System........................................................4
Functional Requirements.............................................................................................................4
Non-Functional Requirement.......................................................................................................5
Use case Diagram.........................................................................................................................7
Domain Model Class Diagram.....................................................................................................8
Event-partitioned System Model.................................................................................................9
ER diagram................................................................................................................................10
Conclusion.....................................................................................................................................11
References......................................................................................................................................12
List of Figure
Figure 1: Use Case Diagram for Warehouse Management /system of Auto Parts Organization....7
Figure 2: Domain Model Class Diagram for System for Auto parts Organization.........................8
Figure 3: Event-partitioned System Model diagram of Warehouse Management System for Auto
parts Organization............................................................................................................................9
Figure 4: ER Diagram for Auto parts Organization......................................................................10

Introduction
Warehouse Management System is used for managing all the operation related to the warehouse
and responsible for the delivery of the orders to customers. According to Zhao, Fang, Huang &
Zhang. (2017) and Zhou & Fei. (2016), the warehouse management system optimized the whole
process of ordering products from online organization to delivery of the product to the
customers. The Auto parts organization process the request and from a user which is given on
system and then deliver that particular product to the customer. The whole process helps in
expanding the business and make the costumers order the product online in an easy manner.

Architecture and Design of Warehouse Management System
The Warehouse system is a system which manages the warehouse and all operation related to it.
The system provides the feature for accepting the request and delivering the requested product.
Depending on the requirements, the system provides a different feature and perform different
functions. The proposed is developed for the Auto parts organization for expanding their
business. Users are allowed to access the system for ordering the product online. The system
provides live tracking and all the other details related to the orders. The system manages all the
function of the warehouse and gives the best output. The automated system helps in increasing
the productivity for the organization and provide all useful facility to make the business
successful.
The functional and non-functional requirements show the basic operation performed by the
particular system and the function should be provided by the system.
Functional Requirements
Functional requirement shows the basic feature or the task need to be provided by any system.
This shows the behavior of the system. The functional requirements are based on what users
want from the system. The functional requirements of the proposed system revolved around the
ordering of the auto parts online. The functional requirements can be categorized according to
the requirements of the users and the organization (Lam, Choy, Ho, Cheng & Lee. 2015).
Inventory live Tracking
The system must provide live tracking of the orders or product so that progress can be check.
The order must be delivered before or on the expected date. The inventory tracking provides all
the information related to the movement of the order from the starting point to the delivery point.
The system provides detail about the person carrying the product.
Warehouse Design
As per Lee, Lv, Ng, Ho & Choy. (2018), the design of the warehouse should be effective so that
all the required task should be performed appropriately. The design of the warehouse makes the
workflow effective and the picking of the order fast. The designing of the warehouse can
optimize the completed process. The storage capacity must be expanded as per the requirements.
Packing and picking of the goods
The system must support the optimized way for picking and packing of the product so that the
delay in the delivery not done. The picking of the goods includes zone picking. The accurate
address and other information should be given so that there is no wrong delivery. The system
should pack all the product with good materials so that there is no effect or damage to the
product.
Management of the resources

Resources are wasted many times in every system. This system enables the organization or other
contributors to save resource utilization. The system manages all the resource such as labor. The
system manages labor by monitoring them and increase their productivity. Tracking of other
resources is also provided by the system so that there are no missuses of the resources.
Shipping details
Listing of the orders are made using the automation system and the details are attached with the
requests. According to Atieh et. al. (206), the system must provide fast shipment so that the
product can be delivered at the expected time or before the expected time. The invoice should be
generated so that the shipment notification can be sent to the customers. The process must be
support for all the information notification to the users.
Time management
The time management includes managing the time for all the process and function included in
the delivery of the product. The system should have a track of all the activities performed an able
to send all these details to users. All the task like processing request, listing, picking the product,
packing, shipping and delivering a product. All these tasks must be performed before the
expected time (Anđelković & Radosavljević. 2018).
Non-Functional Requirement
The non-functional requirements are the requirements which deal with the behavior of the
system. The quality of the system is the main focus to cover in this part. The non-functional
requirements measure the usability of the system and the performance report is shown. Non-
Functional Requirements can divide into a category depending upon the requirement areas.
Usability
The usability of the system shows the capability of the system that how effective and easily a
user can use it. Designing an interface of the system must be easy so that the user can easily use
the system by accessing all the feature. The targeted points must be covered like using
efficiency, responsive time, attractiveness, etc. The interface must be simple so that the user can
use all the options. The proposed system must be developed in such a way that everyone can use
the system can order auto parts online (Baruffaldi, Accorsi & Manzini. 2019).
Security
The security is the main aspect as the sensitive data can be misused. The system must have all
the possible security protection so that the personal details like mobile number, email,
passwords, bank details, etc. should not be accessed by fake or fraud persons. The Warehouse
Management System for the auto parts is designed in such a way that the users who entered the
details have complete protection and their personal information should not be shared by others.
There are different techniques for securing sensitive data such as encryption.

Reliability
The reliability of the system concern with the capabilities of the system that how long it can
work without failure. The system needs to be highly reliable so that there is no issue while using
it. The designing of the system must be in such a way that all the problems and fault are resolved
in the early stages.
Performance
Every system needs to be optimized in the performance term. The proposed system has to
process multiple requests and manage all the details regarding it. There must be a good
performance of the system so that the users can order the product without any issues (Balan,
Cioca, Torretta & Talamona. 2016) and (Mao, Xing & Zhang. 2018).
Availability
Availability of the system means the service and the feature availability for the users using the
system there should be no fault of issue while using any of the services. The availability of all
the services should be equal for all.

Use case Diagram
The use case diagram shows the different cases can occur in any system. The use case diagram
shows the different scenarios of the system and their process. The proposed system has different
cases like collecting request for customers, processing these requests, listing all the requests,
requesting for a product, picking a product, packing the product and delivering the products. All
these cases are managed by the system which also provides system failure alert or alert for any
unwanted situation in the system.
 Use cases: These are the cases included in the system. The proposed system has multiple
cases form requesting for the product to delivery of the product.
 Actors: Actors are the participators in the system who have their contribution to the
system. In the following system actors included are Organization, System, Customers,
Bank and Courier.
 Boundary: the boundary shows the domain of the system. The proposed system bound
the system for using it for auto parts organization only.
Figure 1: Use Case Diagram for Warehouse Management /system of Auto Parts Organization

Domain Model Class Diagram
The class diagram shows the different objects and classes present in the system. with showing
their relationship. The classes show different contributors to the system. The class diagram for
the following system shows the different contributors or objects which participate in the
complete process. The customer uses the system for ordering the product and the organization
provides the complete delivery of the product. The parts included in the diagram scan shows as:
 Class or Object: Class or object shows the participator in the system. For the following
system, the
 Class are is made of Customer, System, Bank, Organization, and courier. The relation
and flow between these classes are shown in the class diagram.
 Connectivity: The connectivity shows the relation between the classes or objects. The
type od the relation is shown using arrows.
 Variables and methods: Variables show the attribute of that particular class. The
methods show the function or operation performed by the object in the system.
Figure 2: Domain Model Class Diagram for System for Auto parts Organization

Event-partitioned System Model
The event-partitioned system model is used to show all the events occurred in the system. There
are different element or actors which is responsible for the particular event. This model is used to
analyses the system in an easy manner. Each and every element have their own task to perform
which shows the dependency of the event and elements. The proposed system contains different
events starting from requesting for the order and then control passes for completing the delivery
of that requested product. This Model contains three parts –
 Actor – The actor is the contributors who are responsible for happening of the events.
The actors interact with the system. The proposed system includes customers, bank,
organization, and courier.
 Events – The events are the operation or function performed by the actors and system in
the complete process. In the following system, the events are like requesting product,
sending a notification, delivering the orders, etc.
 System – The system is the center part which interacts with the actors and responds for
the events by actors. In the proposed system the system is Warehouse Management
System.
Figure 3: Event-partitioned System Model diagram of Warehouse Management System for Auto parts
Organization

ER diagram
The Entity Diagram is a diagram shows the relationship between entities. The entity has types of
attributes. The attributes can be weak or strong. The ER diagram is a structural representation of
the database and its connectivity. The entity can be an object, person, role, concept, and events.
For the following system, the entities used are customers, bank, courier service, system, and
organization.
Figure 4: ER Diagram for Auto parts Organization

Conclusion
The proposed system helps the Auto parts organization to expand its business and allow
customers to order the products online. The system provides all possible functions to costumer as
well as organization to interact with each other (Alyahya, Wang & Bennett. 2016). All the
necessary information is provided to the costumers relate to its orders. The system manages all
the operation of the warehouse and makes it possible to increase the functionality. The future
work will improve its security and in the coming time, the all system will replace by the
warehouse management system.

References
Alyahya, S., Wang, Q., & Bennett, N. (2016). Application and integration of an RFID-enabled
warehousing management system–a feasibility study. Journal of Industrial Information
Integration, 4, 15-25. DOI: https://doi.org/10.1016/j.jii.2016.08.001.
Anđelković, A., & Radosavljević, M. (2018). Improving order-picking process through
implementation of warehouse management system. Strategic Management, 23(1), 3-10. DOI:
https://doi.org/10.5937/StraMan1801003A.
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. DOI:
https://doi.org/10.1016/j.procir.2015.12.122.
Balan, I. L., Cioca, L. I., Torretta, V., & Talamona, L. (2016). Warehouse threats and loss
prevention management in case of fire. Procedia Technology, 22, 1028-1034. DOI:
https://doi.org/10.1016/j.protcy.2016.01.138.
Baruffaldi, G., Accorsi, R., & Manzini, R. (2019). Warehouse management system
customization and information availability in 3pl companies: a decision-support tool. Industrial
Management & Data Systems, 119(2), 251-273. DOI: https://doi.org/10.1108/IMDS-01-2018-
0033.
Lam, H. Y., Choy, K. L., Ho, G. T. S., Cheng, S. W., & Lee, C. K. M. (2015). A knowledge-
based logistics operation planning system for mitigating risk in warehouse order
fulfillment. International Journal of Production Economics, 170, 763-779. DOI:
https://doi.org/10.1016/j.ijpe.2015.01.005.
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. DOI:
https://doi.org/10.1080/00207543.2017.1394592.
Mao, J., Xing, H., & Zhang, X. (2018). Design of intelligent warehouse management
system. Wireless Personal Communications, 102(2), 1355-1367. DOI:
https://doi.org/10.1007/s11277-017-5199-7.
Zhao, Z., Fang, J., Huang, G. Q., & Zhang, M. (2017). Location management of cloud forklifts
in finished product warehouse. International Journal of Intelligent Systems, 32(4), 342-370.
DOI: https://doi.org/10.1002/int.21864.
Zhou, C., & Fei, Q. (2016, December). Warehouse management system development base on
open source web framework. In 2016 International Conference on Industrial Informatics-