University System Analysis and Design 2 Report: Warehouse Analysis

This report provides a comprehensive analysis of warehouse management systems (WMS). It begins with an introduction to WMS and its growing acceptance in supply chain management, followed by a discussion of the strengths and weaknesses of cloud-based WMS solutions, including increased operational efficiency, lower costs, scalability, rapid implementation, and improved customer experience. The report also identifies weaknesses associated with cloud WMS. A significant portion of the report is dedicated to comparing and contrasting the Rational Unified Process (RUP) and Scrum methodologies, highlighting differences in their cycles, planning approaches, scope determination, and artifacts. The report concludes by emphasizing the advantages and disadvantages of WMS and the importance of choosing the right methodology for system development. References to relevant literature support the analysis.

Running head: SYSTEM ANALYSIS AND DESIGN
System analysis and design
Name of the Student:
Name of the University:
Author name:

1
SYSTEM ANALYSIS AND DESIGN
Introduction
Warehouse system has been one of the technologies that has been gaining high
acceptance among the supply chain managers. This report discusses about the strengths and
disadvantages of WMS. Proper difference in between the RUP and SCRUM is provided in
this report.
Discussion
The ware-house management system-(WMS) software offer businesses to monitor the
supply chain and manages the entire inventory operations from the whole seller to the
distributor [2]. The global project strategy and free-market strategy shaped our current
economy by creating various needs and demands for new customers. The WMS software
optimizes the fulfilment capabilities in order to meet their need, the business needs, and the
ability to fulfil to respond them quickly. It is reasonable that the ensuing to develop a system
makes the production faster, a better and cheaper way to increase the advantage and maintain
a competitive global market [4].
A cloud WMS provides the best of breed management capability for the warehouses
associated with a software as a services-(SAAS) model/prototype which helps to utilizing the
cloud technology over the enterprises [1]. The combination of variety of Auto ID technology
(ADC) along with deeply functionality, High-Jump Cloud Ware-house management and the
internet base architecture delivers a scalable, le flexible and powerful real time WMS.
Identify the strengths
Most of the organization develop a ware-house management software to automate and
streamline the inventory processes, which also control costs for the products. The proposed

2
SYSTEM ANALYSIS AND DESIGN
system can be easily configurable, dynamic and robust which influencing the cloud for a cot
effective and the rapid implementation that comprehends the benefits are given below:
 Increasing the operational efficiency – The warehouse software managing fulfil the
operations evolved in the cloud, the supply chains managing a real time visibility for
the inventory and for the organizational operations, meeting with their customers and
makes them busy in purchasing along with the relevant WMS technology [5].
 Lower Cost – the Cloud based WMS software provides benefits to control costs
which engage more customer to the businesses. Also it reduces the maintaining cost
and the upgradation cost are lower for the system.
 Scalability - this makes the system software interactive so that it can be operated on
any we enabled computer without much time taking, the hardware setup and easily
and quickly deployed by other warehouses which provide support to expand the
business support growth.
 Rapid implementation - WMS with hosting, implementation and configuration all
provide supports to the vendors on regular basis.
 Improve the customer experience
 Identify the weaknesses of Cloud
The differences between the Rational Unified Process and Scrum methodologies
The differences in between Rational Unified Process and Scrum methodology can be
diversified in 5 major areas. The areas are namely the cycle that is used as per the
methodology that is being implemented, planning that is imposed, difference in scope
determination process is also observed, difference in artifacts are also observed in the
process. Type of the project that is to be completed is also considered as in the difference
proposing section.

3
SYSTEM ANALYSIS AND DESIGN
The cycle that is taken up by the Rational Unified Process is formal cycles. It is seen
that these cycles are defined across 4 different phases and hence wise the work flow can be
considered as concurrent [5]. Whereas in case of the SCRUM, the major aspect that is
considered is that each sprint is considered as a complete cycle. Another aspect that is
considered as a complete iteration.
In case of the planning section Rational Unified Processing, formal project planning is
associated with a number of iterations and hence wise 4 phases are to be performed.
multiple iterations are performed for completion of this stage. The plan that is implemented is
end result driven and hence wise intermediate milestones are considered. Whereas in case of
SCRUM planning the main aspect that considered is that there is no end to end project plan.
There is no fixed plan that is to be performed for proper completion of the project. Planning
is performed as per completion of the steps. The outcome that is received after completion of
a step acts as a basis of new plan of the next stage. Owner of the project decides when the
project gets complete. After the owner agrees with the outcome received the project gets
complete.
In case of the Rational Unified processing the plan that is to be executed is pre
planned. This leads to the fact that the that outcome of the project is already defined and the
scope of the project is hence wise decided. Although the scope of the project is predefined,
alteration can be brought in. however there are steps that are taken to perform change the
scope. Whereas in case of the SCRUM, there are no specific goal that is set. This includes the
fact that the steps that are taken will be providing a better assessment of each steps that will
be taken for execution of the project. Another aspect that is considered is that there is no
predefined scope. In this case the scope keeps on varying as per the iterated steps. Re-
evaluation after every iteration is performed.

4
SYSTEM ANALYSIS AND DESIGN
The artifacts of RUP includes the likes of test scripts, scope development, requirement
packages, development plan, system architecture documentation and formal functional
packaging system is also considered [6]. Whereas, it can be stated that in case of the SCRUP,
operational software is the sole artifact that is present.
Usage of Rup can be made for recommendation regarding large scale organizations,
recommendations for having a long term goal is also performed with the help of RUP.
Projects with high and medium complexity is also included in the section. Whereas in case of
the using SCRUM, projects with quick enhancements can be made. Usage of SCRUM can be
made only when there is specific deadline provided.
Conclusion
From the above discussion it can be concluded that RUP and SCRUM are one of the
most used methodology. Despite the fact that both the methodologies are based on the
iterative system there are differences present in the system. Warehouse management also has
both advantages and disadvantages that are present in the system.

5
SYSTEM ANALYSIS AND DESIGN
References
[1] A.M. Atieh, H. Kaylani, Y. Al-abdallat, A. Qaderi, L. Ghoul, L. Jaradat and L. Hdairis.
Performance improvement of inventory management system processes by an automated
warehouse management system. Procedia Cirp, 41, pp.568-572, 2016.
[2] S. Madurapperuma, L.J. Ebert, S. Gamage and D. Kuruppuarachchi. 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), 2018.
[3] C.K.M. Lee, Y. Lv, K.K.H. Ng, W. Ho and K.L. Choy. Design and application of Internet
of things-based warehouse management system for smart logistics. International Journal of
Production Research, 56(8), pp.2753-2768, 2018.
[4] P. Goudarzi, H.T. Malazi and M. Ahmadi. Khorramshahr: A scalable peer to peer
architecture for port warehouse management system. Journal of Network and Computer
Applications, 76, pp.49-59, 2016.
[5] D. Maximini, Maximini and Rauscher. Scrum Culture. Springer International Publishing
AG, part of Springer Nature. 2018.
[6] H. Lei, F. Ganjeizadeh, P.K. Jayachandran and P. Ozcan. A statistical analysis of the
effects of Scrum and Kanban on software development projects. Robotics and Computer-
Integrated Manufacturing, 43, pp.59-67, 2017.