Warehouse Management System Design Report: ITC 548

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

ITC 548
Assessment Item 2
Requirement gathering
Student Name
Student ID

Introduction:
On the basis of assignment 1, that is the system vision document of a warehouse management
system; this report will cover the detailed architecture and the design of the suggested warehouse
management system. This report will describe the non-functional and functional requirements for
the warehouse management system. To better understand the system, it will include use case
diagrams and class diagrams. This also has an event partitioned system model.

Contents
Introduction:....................................................................................................................................2
Functional and non-functional requirements of the system.............................................................4
Functional requirements:.............................................................................................................4
Non-functional requirement:.......................................................................................................4
Use case diagram.............................................................................................................................6
Domain model class diagram...........................................................................................................8
Event-partitioned system model....................................................................................................11
Conclusion.....................................................................................................................................13
References:....................................................................................................................................14
List of figures
Figure 1 Use case diagram for the WMS.........................................................................................7
Figure 2 UML class diagram for WMS...........................................................................................9
Figure 3 Event portioned system for warehouse management......................................................12

Functional and non-functional requirements of the system
The warehouse management system enables the organization to management and controls the
warehouse activities. Warehouse management system offers visibility and easy tracking to the
inventory. This is helpful to improve the performance and efficiency of the system. This manage
the activities of the warehouse like order receiving, picking and packing, shipping, invoice,
security, payment etc. The design of the warehouse system ensure the efficient working of it.
Non-functional requirement refers to the common characteristics of the general system. The
functional requirement describes the behavior of the warehouse management system. These
include that the system should be able to perform basic operations of the WMS such as order the
item, checking the order, searching the inventory, edit and update the database, cancel the order,
payment, etc. Also, it should be able to perform inventory tracking and other operations in a fast
and effective manner.
Functional requirements:
This shows the basic features of the general system. This is basically aligned with user
requirements and business requirements. For the warehouse management system, the functional
requirements are the following:
 Tracking of inventory: The authorized and responsible person should be able to perform
the tracking of the inventory, in order to fulfill the requests properly. As the system is
based on cloud services, it should have the facility of live tracking of the inventory.
 Picking orders: The system should have an optimum way to pick the orders from the
buyers or customers to avoid any a delay in the order delivery.
 Packing orders: The system should be able to do a good packing of the materials or order
in order to prevent any damage.
 Add and search inventory: Responsible person should be able to track the inventory by
adding and searching the items in it. After these operations, the system should be able to
automatically update itself.
 Database management: The system should be able to manage the database effectively in
order to keep records organized.
 Payment: The WMS system should be able to manage the payment. To enhance customer
satisfaction, the system should support a different kind of payment methods.
 Shipping details: the system should be able to generate the invoice of the orders. This
enables the system to send alerts and messages to the customers time-to-time (Eriksson,
2015).
Non-functional requirement:
This refers to the behavioral characteristics of the warehouse management system. This includes
the following characteristics:

 Usability: This refers that how the users can use the features of the WMS effectively. It
shows the ability of user to operate and learn about the system. This includes average time
taken by the system to accomplish the tasks.
 Performance: it refers to the capability of the system that how long a system can work
without any failure. This reduces due to the bugs in the program code or some other failures.
This also refers that how fast a system respond to the query or interaction. Poor customer
satisfaction and experience caused by poor performance.
 Flexibility: The system should be flexible to support a different kind of platforms.
 Efficiency: The system should be able to perform the operations efficiently.
 Security: The ware house management system and services should not be accessible to the
unauthorized person and have proper arrangements to maintain security. Various levels of
authorization and authentication mechanisms are considered in this. This also covers the
protection from malwares.
 Availability: The system and services should be available to the authorized person, whenever
required. This also shows that the maintenance and testing of the system should be done in
such way that it does not affect the availability of the services and operations to the
customers.
 Scalability: This shows the ability of the system to grow without a negative impact on
performance or operations (Eriksson, 2015). This refers to handling more operations with
more users in the warehouse management system.

Use case diagram
The use case shows the working of the system with the help of actors and operations. This
describes the various situations that can occur in the system and the process to do it. Use case
basically shows the interaction between the users and the system to achieve a specific set of
objectives. The use case diagram mainly has actors, system, and objectives (use cases). Actors
are the users, who used to interact with the system. The diagram has a boundary line to show the
system domain. System is the software that is providing the services. Goals are the objectives
that are the reasons behind the interaction. The use case is helpful to clarify, identify and
organize the requirements of the system (Rouse, 2019).
For the warehouse management system, the uses cases can be ordered generation, picking the
order, packing the order, managing the database, cancel the order, update the order status, etc.
All these situations are performed and managed in the cloud-based warehouse management
system by different actors.

Figure 1 Use case diagram for the WMS
As shown in the above diagram, there are many use cases in a warehouse management system.
Some of the use cases are good movement summary, order receiving, order picking, order
processing, payment, order tracking, status update, security design and many more. This
warehouse management system has 5 actors that are buyer, administrator, bank, CDT operator
and MW operator. These actors are able to perform different operations. For example, the buyer
is able to log in and log out into the WMS system. Order can be generated by the buyer. Buyer is
also allowed to check the status of the order and cancel the order if wanted. For making the
payment, the buyer is connected to the bank. Similarly, other actors are performing their tasks.

Domain model class diagram
The class diagram refers to the static representation of the program. This is used to define the
objects in the system along with the relationship among them. A UML class diagram displays
classes, operations, attributes, functions, and relationships. This shows the structure of the
application to better understand the code. This is helpful for the customers as well as the
stakeholder. The main elements of the class diagrams are the class name, attributes and the
operations ("Class diagrams with UML", 2018). To represent the class in a graphical way, the
class name is required. Attributes are the named property of the class.

Figure 2 UML class diagram for WMS
Relationships:
In the class diagram there, are three types of relationships;
 Associations
 Generalization
 Dependencies

This is the class diagram for the suggested warehouse management system. This class diagram
has 7 classes that are buyer, order details, staff, bank, administrator, MW operator, and CDT
operator. These classes have a set of attributes and functions. For example, the buyer class has
buyer_name, buyer_phone, buyer_email and buyer_passwd as attributes. The functions included
in this class are login(), logout(), payment(), check_status(), and order_item(). Another example
is that, administrator has attributes like admin_name, admin_id, admin_phone and admin_mail
along with the functions such as security_option(), login(), logout(), receive_payement() etc.

Event-partitioned system model
This is a simple technique to analyze the system which helps to understand the system in a
simpler and smaller way. This shows the possible operations that are related to the use case
diagram. Each element has its own set of tasks or operations and these shows dependencies with
each other. The suggested warehouse management system consists of various events such as
order item, cancel the order, add inventory, security design, etc. The event portioned system
model includes the following elements:
 Actors: Similar to the use case diagram, the actors in the event portioned model are
responsible for the occurrence of the events. The given warehouse management system
includes actors as a buyer, MW operator, administrator, CDT operator, and bank.
 Events: The events are the activities that are performed by these actors included the system
to achieve desired goals. In the given system, events are ordered item, add inventory, cancel
the order, search inventory, security option, database management, etc.
 System: The system is the program which provides the services to the actors. A warehouse
management system is a system in this given scenario.
The below-given diagram is the event portioned system model diagram for the warehouse
management system. This diagram has 5 actors. The diagram shows that the buyer is able to
order the item, cancel the order and check the status of the order. MW operator is able to add and
search the inventory along with the ability to edit the database. A bank is responsible for
payment.

Figure 3 Event portioned system for warehouse management