ITC548 Assessment 2: Warehouse Management System Design

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

ITC548 Assessment 2

Table of Contents
Introduction................................................................................................................................................3
Identify and briefly describe the functional and non-functional requirements for the proposed system.
.................................................................................................................................................................... 4
Identify use cases and draw use case diagrams for the proposed system that show major use cases
and actors...................................................................................................................................................6
Draw domain model class diagrams for the proposed system. Be as specific and accurate as possible, if
needed information is not given, make realistic assumptions..................................................................7
Develop an event-partitioned system model encompassing all the use cases you identified in question
2. Assume that the classes and associations in question 3 correspond to entities and relationships
from similar entity-relationship diagrams.................................................................................................8
Conclusion...................................................................................................................................................9
References................................................................................................................................................10
List of figures
Figure 1 Use case diagram for Warehouse management system................................................................6
Figure 2 UML class diagrams for warehouse management.........................................................................7
Figure 3 Model of event partitioned system...............................................................................................8

Introduction
This report is based on the concept of warehouse management. It includes the whole functioning
of supply of the auto-parts through the warehouse management system. This assessment
describes the functionality and non-functionality requirements of warehouse management. This
report also clears out the concept of steps or the strategies involved in warehouse management. It
shows the strategies through which the warehouse management system gets efficient and cost-
effective. This also includes the UML diagram, class diagrams and the event-partitioned system
model. Through this strategy, the owner of the auto-parts business gets the idea to convert their
business positively by using some steps of the warehouse management.

Identify and briefly describe the functional and
non-functional requirements for the proposed
system.
The warehouse management system is like a software application that is mainly used for
monitoring and controlling the materials and operations based on the warehouse or the points
from the warehouse has been received. This system is used for ensuring all the storage materials
and the and management of the accounts based on the delivery or the receiving products in the
warehouse. This system is based on the chain block that can start from the client-side and close
form the member side (Fazal, et.al., 2017). This system provides the transparency to stock exist
for the management of the ware house.
Functional requirements:
Functional requirements are nothing but they are the components and system that can be used for
the management process (Tindley, J. 2017). The important functions of the warehouse
management system are the software on which the task will be performed due to this the main
functional requirements are the components and the parts of the system. The function
requirements involved the things like manipulation of the data, calculation of multiple data or
accounts, processes that include in the business, interaction with the several users, or the multiple
types of functionality which can be performed in the business. This functional requirement helps
the employee to understand a intend behavior based on several systems. These behaviors include
the numbers of functioning and the tasks that can be based or performed on the system. This can
easily be captured or mainly focused on the requirements of the user. It gives the answer to
products and about the product that what it is.
Some examples of the functional requirements are:
 It validates the customer to access the system based on the ABC contact management
automatically.
 It also allows the users for accessing the customers sailing record by the sales system,
 It provides the software with blue color in the background application along with
providing the theme of hexadecimal RGB color which exist in the range of 0*0000FF.
 The revenues data can only be view by the managerial level through which the security
remains constant.
 This provides the facility of integration of banking API with the software system.
 This system of software gives the accessibility requirement for passing the section 508.
Non-functional requirements:
Non-functional requirements are depending on the attributes of the quality of the system based
on software. They can be represented by the blocks of the standards that can be used for judging
the particular operations performed on the system. It may also include things like the capability
of loading the website. These non-functional requirements are used for ensuring the qualities,
usability or the effectiveness of the whole system based on the software (Jacyna, et.al., 2015).

Non-functional requirements are considered as the failure of all these demands are not getting
fulfill according to the task that performed on the software. This requirement gives allowance to
the user to restricting and impose the constraints according to the designing of the software. For
example: if the user’s amount is large in quantity then the site will be load is approx. 3 seconds.
This is hard for capturing and mainly focused on expectations, not on the requirements. This
provides the answer about the working of the products that how the product work.
Some examples based on the non-functional requirements:
 As this provides the accessibility of making the changes in the log in password constantly
or according to or the requirement.
 This system doesn’t allow the user for updating their information based on the salary. If
any user can do this type of attempt, then this will be reported to the administration of the
security.
 If the unsuccessful attempt can be happening by the user side, then that type of data can
also be accounted for as the audit trail.
 A website can give allowance to access for handling the 20 million users at a time
without disturbing the performance.
 This system software is portable that why in changing from one OS to another, the task
never creates any type of problem (Tindley, J. 2017).
 This system provides privacy for each small information. And restrict the export of
technologies and the rights of intellectual property that can be audited.

Identify use cases and draw use case diagrams for
the proposed system that show major use cases
and actors
Figure 1 Use case diagram for Warehouse management system
Use case diagrams are the type of UML diagrams which can be used for analyzing the several
systems at a single time. They are the collection of the requirements that can be used in the
system. The major importance of this diagram is that it identifies the functions and interact all
the relations with the task or actors (Nishadha. 2019).
In this task, the four actors are used to complete the tasks and their link-ups are also shown in
this diagram. Four actors can perform their roles and fulfill all the responsibilities by maintain
the scheduling and making the accounts for each task.

Draw domain model class diagrams for the
proposed system. Be as specific and accurate as
possible, if needed information is not given, make
realistic assumptions.
Figure 2 UML class diagrams for warehouse management
A UML class diagrams give an overview of the software system which includes the classes,
operations, several attributes and also shows their relationship. They all are separated by each
other and connect by the link-up relation. This makes the task easy in completion because of it a
user can identify each step of the project or the software.
In this diagram, the warehouse management system can be described very easily by evaluating
each task along with specifying the operations and the classes. They can be separated by using
the relations between each other.

Develop an event-partitioned system model
encompassing all the use cases you identified in
question 2. Assume that the classes and
associations in question 3 correspond to entities
and relationships from similar entity-relationship
diagrams.
Figure 3 Model of event partitioned system
The event-partitioned system model is the technique which can be used for applying the system
methodology in an easy way. It is the collection of each part include in the system it means the
small, medium and large parts can briefly be described through this technique. It shows the
requirements and the system of business that can be sued in fulfilling the requirements of the
clients.

In this model, there is a proper description given for the warehouse management system. Which
includes the several important tasks along with their sub-parts. They all are linking with each
other for marinating the structure.
Conclusion
This assessment provides a brief description of the strategies that can include in the warehouse
management. This includes the Use case diagrams, class diagrams and the model of the event-
partitioned system. It includes the description of the requirements that are based on the
functionality and the non-functionality concept of warehouse management. Through which the
researcher can know about what and how both the terms can reveal each concept. These different
types of diagrams can divide the concept into several parts through which the task can easily
complete with balancing the schedule along with the proper management. It describes the entire
process of warehouse management through which the other tasks can be completed in proper
management from the login of the clients to log out of the clients.

References
Tindley, J. (2017). Core Functions of a Warehouse Management System. Retrieved from
https://blog.lpcinternational.co.uk/core-functions-of-a-warehouse-management-system
Fazal, T., Strutt, D., Gibb, R., Armstrong, M., Adendorff, M., & Helal, R. (2017). U.S. Patent
No. 9,740,992. Washington, DC: U.S. Patent and Trademark Office.
Nishadha. (2019). Use Case Diagram Tutorial (Guide with Examples). Retrieved from
https://creately.com/blog/diagrams/use-case-diagram-tutorial/
Jacyna, M., Lewczuk, K., & Kłodawski, M. (2015). Technical and organizational conditions of
designing warehouses with different functional structures. Journal of KONES, 22.