System Analysis and Design

This document provides an analysis and design of the system for Fulfilment by Amazon, Customer Support and Return, and Warehouse. It includes stakeholder analysis, use case descriptions, use case diagrams, and class diagrams.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Subsystem 1: Fulfilment by Amazon..............................................................................................1
1. Stakeholders.............................................................................................................................1
2. Brief Use Case Description.....................................................................................................2
3. Use Case Diagram...................................................................................................................4
4. Class Diagram..........................................................................................................................5
Subsystem 2: Customer Support and Return...................................................................................6
1. Stakeholders.............................................................................................................................6
2. Brief Use Case Description.....................................................................................................7
3. Use Case Diagram...................................................................................................................9
4. Class Diagram........................................................................................................................10
Subsystem 3: Warehouse...............................................................................................................10
1. Stakeholders...........................................................................................................................10
2. Brief Use Case Description...................................................................................................12
3. Use Case Diagram.................................................................................................................14
4. Class Diagram........................................................................................................................15
Bibliography..................................................................................................................................16

2SYSTEM ANALYSIS AND DESIGN
Subsystem 1: Fulfilment by Amazon
1. Stakeholders
Stakeholders Name Stakeholders Role Stakeholders Type
Sellers The sellers associated with
the FBA system sells their
individual product or bunch
of product to Amazon
Internal stakeholders
Resellers The resellers sells their
products in large quantity to
amazon.
Internal stakeholders
Amazon Buy all products that sellers
and resellers sell to amazon.
If the sellers and resellers
wants Amazon to label the
products, the labelling is also
done by Amazon.
Executive/operational
stakeholders
Customer Customers are stakeholders
who buys products from the
company which are FBA
authorized.
External stakeholders
Table 1: Stakeholder table

3SYSTEM ANALYSIS AND DESIGN
2. Brief Use Case Description
Actor Use Case Name Use Case Description
Seller Sign Up the system for
accessing the FBA Prep
Service from Amazon.
For getting the service from
FBA Prep system, the seller
needs to sign up the system
by providing their name,
address, phone number, email
and all other personal data so
that they can be tracked by
Amazon.
Seller Enabling the service of FBA
Prep
For enabling this option, the
seller needs to give their
details about their how they
want their products to be
packed. They can pack
themselves or can hand the
products to amazon prep for
them to pack the products.
Seller Product Packing Preparation The sellers packs the product
on their own.
Seller Labelling of Products The seller also labels the
product of their own.
Seller Paying for Preparing Service In case amazon does the

4SYSTEM ANALYSIS AND DESIGN
preparing, the seller need to
pay the required amount to
Amazon.
Re-Seller Sign Up for FBA Prep
Service
The seller sign ups in the
FBA system to sell their
products in a bulk order
Re-Seller Product Packing Preparation Packs the product by own.
Re-Seller Enter Product Details and
pickup location
Enter the details of the
product and the location from
where the product will be
picked up.
Re-Seller Enable FBA Prep Service For enabling the FBA prep
service, the seller needs to
select the option either to
pack the product by own or
hand it over to Amazon Prep
for packing.
Re-Seller Labelling of Products Labels the product by their
own.
Amazon Provide Deals The resellers are provided
with lighting deals from
amazon from where they can
get discount of product

5SYSTEM ANALYSIS AND DESIGN
shipping of product
packaging.
Table 2: Use case Description Table
3. Use Case Diagram
Figure 1: Use case Diagram of Fulfilled by Amazon System
(Source: Created by Author)

6SYSTEM ANALYSIS AND DESIGN
4. Class Diagram
Figure 2: Class Diagram of Fulfilled by Amazon System
(Source: Created by Author)

7SYSTEM ANALYSIS AND DESIGN
Subsystem 2: Customer Support and Return
1. Stakeholders
Stakeholders Name Stakeholders Role Stakeholders Type
Customer The customer are the external
stakeholder who has to buy
the products from amazon.
External Stakeholders
Manager The manager has to manage
all the internal works of the
amazon system from the
warehouse to the customer
support system.
Executive Stakeholders
Support Team The support team needs to
support the queries and
complaints of customer who
faces problem.
Operational Stakeholders
Resellers/Sellers The resellers and the sellers
can also get query related to
their products and needs
customer care and support.
External stakeholders
Table 3: Stakeholder table

8SYSTEM ANALYSIS AND DESIGN
2. Brief Use Case Description
Actor Use Case Name Use Case Description
Customer Makes Call The customer needs to make
call to the customer service
for lodging their complaints.
Customer Enter Invoice number After the call gets connected,
the customer needs to enter
the invoice number of the
product for which they need
to lodge complain.
Customer Waits in Queue/select dial
back option
The customer can wait for
getting customer support call
in the queue or can
disconnect the call and can
request for call back option.
System of Amazon Confirms the Number When the customer selects
the call back option, the
system confirms the number
from the customer so that
they can call back.
System of Amazon Generate Ticket When the call is
disconnected, a ticket is
generated about to call the

9SYSTEM ANALYSIS AND DESIGN
customer at the number given
by the customer.
Managers Evaluates return System The managers evaluates the
return system that is
processes by the support team
of the company.
Managers Review performance support
team
The performance report of the
support team is also done by
the managers of customer
system.
Managers Generates Report The manager generates the
report for the system.
Amazon Support Team Solves Issues The support team of Amazon
solves the issues that are
lodged by the customers in
the system.
Amazon Support Team Generate label of return case The support team also
generates a label when there
is case of returning the
product.
Table 4: Use case Description Table

10SYSTEM ANALYSIS AND DESIGN
3. Use Case Diagram
Figure 3: Use case Diagram of Customer Support and Return System
(Source: Created by Author)

11SYSTEM ANALYSIS AND DESIGN
4. Class Diagram
Figure 4: Class Diagram of Customer Support and Return System
(Source: Created by Author)
Subsystem 3: Warehouse
1. Stakeholders
Stakeholders Name Stakeholders Role Stakeholders Type
Managers The managers associated with
the warehouse has to hire new
staffs for the warehouse
works. The manager also
have to create a cost analysis
Internal stakeholders

12SYSTEM ANALYSIS AND DESIGN
and can bring profit for the
company.
Packer The packer associated with
the system packages all the
products that comes to the
warehouse. They are paid for
keeping update on the
products that comes in and
goes out from the warehouse
Internal Stakeholder
Customers Can view the products that
are available in the
warehouse and can order
them accordingly.
External Stakeholder
Sellers and resellers The can give their product
directly to amazon after
packing and labelling the
product.
Operational Stakeholders
Table 5: Stakeholder table

13SYSTEM ANALYSIS AND DESIGN
2. Brief Use Case Description
Actor Use Case Name Use Case Description
Manager Hires Staffs The manager hires the staffs
for the inventory who will
manage the system and helps
in update of packing the
system.
Manager Evaluate Cost Analysis
Report
Cost analysis is calculated by
the manager.
Manager Creates Recall Request Recall Request is created by
the manager of the
warehouse.
Manager Add/Remove Shelves The manager can add and
remove some shelves form
the warehouse and can update
them in the system.
Packer Login in System The staff of the packer hired
by manager has to login in
the system at their desired
shift time.
Packer Pack the Products The packer or the member
has to pack the products that

14SYSTEM ANALYSIS AND DESIGN
are not packed by the sellers.
Packaging System Update the Package The packaging system update
the status pf package in the
system so that the customer
gets to know about their
status.
Packaging System Update status of shelves The shelves added or deleted
by the manager is updated or
deleted by the packing
system.
Packaging System Update quantity of products The total quantity of
packages in warehouse is also
updated by the system of
packaging.
Table 6: Use case Description table

15SYSTEM ANALYSIS AND DESIGN
3. Use Case Diagram
Figure 5: Use case Diagram of Warehouse System
(Source: Created by Author)

16SYSTEM ANALYSIS AND DESIGN
4. Class Diagram
Figure 6: Class Diagram of Warehouse System
(Source: Created by Author)

17SYSTEM ANALYSIS AND DESIGN
Bibliography
Adamu, A. and Zainoon, W.M.N.W., 2016, June. A framework for enhancing the retrieval of
UML diagrams. In International Conference on Software Reuse (pp. 384-390). Springer, Cham.
Dahiya, S., Bhatia, R.K. and Rattan, D., 2016. Regression test selection using class, sequence
and activity diagrams. IET Software, 10(3), pp.72-80.
Dori, D., 2016. SysML: Use Case, Block, and State Machine Diagrams. In Model-Based Systems
Engineering with OPM and SysML (pp. 29-35). Springer, New York, NY.
Faitelson, D. and Tyszberowicz, S., 2017, May. UML diagram refinement (focusing on class-and
use case diagrams). In Proceedings of the 39th International Conference on Software
Engineering (pp. 735-745). IEEE Press.
Haoues, M., Sellami, A. and Ben-Abdallah, H., 2016, November. Predicting the functional
change status in UML activity diagram from the use case diagram. In 2016 IEEE/ACS 13th
International Conference of Computer Systems and Applications (AICCSA) (pp. 1-8). IEEE.
Jiang, Y., Duan, Y., Huang, M., Chen, M., Li, J. and Zhou, H., 2017, June. Processing
Redundancy in UML Diagrams Based on Knowledge Graph. In International Symposium on
Parallel Architecture, Algorithm and Programming (pp. 418-426). Springer, Singapore.
Nassif, A.B., Capretz, L.F. and Ho, D., 2016. Enhancing use case points estimation method using
soft computing techniques. arXiv preprint arXiv:1612.01078.
Sulaiman, N., Ahmad, S.S.S. and Ahmad, S., 2019. Logical Approach: Consistency Rules
between Activity Diagram and Class Diagram. International Journal on Advanced Science,
Engineering and Information Technology, 9(2).

18SYSTEM ANALYSIS AND DESIGN
Vachharajani, V., Vasant, S. and Pareek, J., 2016. Feasibility Study of Proposed Architecture for
Automatic Assessment of Use-Case Diagram. In Proceedings of International Conference on
ICT for Sustainable Development (pp. 97-104). Springer, Singapore.
Wang, C., Pastore, F., Goknil, A., Briand, L. and Iqbal, Z., 2015, July. Automatic generation of
system test cases from use case specifications. In Proceedings of the 2015 International
Symposium on Software Testing and Analysis(pp. 385-396). ACM.