Report: Functional Requirements Analysis for Amazon Online System

This report provides a detailed analysis of the functional requirements for Amazon's online retail system, focusing on three key subsystems: Fulfillment by Amazon (FBA), customer support and returns, and the warehouse. The analysis utilizes Unified Modeling Language (UML) to document these requirements. The report identifies stakeholders for each subsystem and presents use case texts and diagrams to illustrate system functionality. The FBA subsystem is examined in terms of its role in product shipping, while the customer support subsystem's processes for live chat and telephone support are outlined, including the queuing system. The warehouse subsystem, responsible for order processing and packing, is also analyzed. The report concludes with a class diagram representing the structure of the system. This report is a comprehensive analysis, which is a part of a group work.

Executive summary
As a system analyst, I will document the functional requirements for Amazon which is an online retail
system, using Unified Modelling Language. At the analysis stage this paper will specify the system
requirements that will to design the computer system. Amazon is an online shopping systems under the
banner www.amazon.com.au. Some of the amazon online system functionality have been modified or
simplified so as to meet a certain criteria. Specifically this paper will investigate three subsystems in
Amazon which are Fulfillment by Amazon that is FBA, warehouse and customer support. The first sub-
system i.e. FBA subsystem is one of the business models where sellers leave the merchandise at the
company and then Amazon ships the products on behalf of sellers. The second sub-subsystem is the
customer support and returns sub-system; this is where the Amazon team provides telephone or live
chat only. The last sub-sub-system the warehouse is the biggest part of Amazon which maintains high
efficiency; where orders are received and then the system prepares a packing lists.
Introduction
This paper will have two sections; the first part will lists at least four stakeholders of each sub-system. In
addition this part will indicate the use case texts of the sub-system. This section will also indicate a use
case diagram which will be based on a brief use case description. The second part will high a class
diagram of the system.
Task one
Online shopping system is said to be a form of electronic commerce that allows customers to directly
buy services or goods from the seller through internet using browsers. This is because the internet has
become one of the essential component in our daily life.
Stakeholders of the subsystem
A stakeholder is a person who has an interest in the proposed or the existing system. Stakeholders
includes both non-technical and technical workers. The overall Amazon online shopping system users
are the system owners, system analyst, and system users. Stakeholders are divided into three categories
these are the primary stakeholders, secondary stakeholders, tertiary stakeholders, and the facilitating
stakeholders. The primary stakeholders are those people who directly use the system; they are also
referred to as the end-users. Secondary stakeholders are those people who don’t directly use the
system but at they can receive output from or even provide input from the system. Tertiary stakeholders
are those people who don’t fall into the first and second category but they are affected by the failure or
success of the system. Facilitating stakeholders are those people who are involved in the development,
design and maintenance of the overall system
Use case texts of the subsystem
All the actors of the Amazon Online shopping system are web customers. There are three sub-systems
for the online shopping system; a sub-system is a portion of the overall system. Based on functional
requirements Amazon online system have three sub-system; the FBA sub-system, customer support and
returns sub-system, and warehouse subsystem

Use case 1: FBA system
Use case 2: Customer support
The second sub-system is the customer and return subsystem. In here the company provides live chat
and telephony calls, a human agent is then assigned to the telephone or to the live chat. In here the
customer is prompted to enter the invoice number of the product which is then placed on a queue. The
system then automatically informs how far the client is in the queue and the mean waiting time. This
means that the web based customer subsystem requires the user to logon to the online system. After
logon, the system takes the client to a powerful and an easy way to get the instant view of the Amazon
call center operational details. These operational details includes creating a new call. The actors of these
sub-system are call agent, technician, head of call center, call center information system, client, and the
marketing manager. Other actions in this system are asking for refund or replacement of good or
service. In here the actors o
Figure 2: Customer-Support use case

Use case 3: Warehouse sub-system
Class diagram
Task two Group work