Amazon System Design: Stakeholders, Use Cases, Class Diagrams Analysis

This assignment provides a comprehensive analysis of the Amazon e-commerce system. It begins by identifying and categorizing Amazon's stakeholders, including customers, sellers, Amazon employees, and government regulatory bodies, outlining their roles and responsibilities. The analysis then delves into the operational aspects of the system with a brief use case description of online product purchasing, illustrated with a UML use case diagram. The assignment further explores the system's architecture by presenting a class diagram of the Amazon warehouse subsystem, detailing classes, attributes, and relationships within the warehouse management system. This includes classes for customers, orders, products, manufacturers, and managers, with associated attributes such as IDs, names, addresses, and order details, providing a detailed examination of the system's components and their interactions. The analysis is supported by references to key software engineering and system analysis texts.

Task 1 - Individual work.
Stakeholders.
According to Pressman (2018) explained that identifying stakeholder correctly helps system
analysist to collect and understand requirements.
Lists of stakeholders of amazon.
Customer (buyers).
Seller.
Amazon owner.
System Employees of Amazon.
Government regulating boards.
Roles of stakeholders.
According to Sommerville (2015) stated that Stakeholders roles ensure quality collection of
required data.
Amazon owner.
Strategies business goals, Visions, missions and objectives.
Role is to have high productivity and sale more.
Main role is how to increase profits.
Amazon Employees.
System administrator
Ensure amazon system (Website or mobile application s) are operating well.
Responsibility of system administrator is to ensure Amazon data policies of backing up,
recoveries, integrity, security, availability, performance and testing are well practiced.
System administrator updates, edits and upload images of products.
Manager
Manager role is to oversee daily operations of amazon departments and workers.
Customer.
Customer responsibility is to search, view, select, add product to shopping cart, make payments
and then buys.
Seller.
Seller supplies products to amazon, creates, manages the product listings, controls pricing of
products, manages sales, ships product and pays some fee to amazon. Finally offer customer care
services to buyer.
Government regulating boards.
Its role is to control and monitor online transaction because there are a lot frauds and different
cybercrimes done on online.
Indicting or mapping stakeholders.
According to Satzinger, Jackson and Burd (2012) stated that indicating and mapping correct
stakeholders well ensures timely delivery and projects meets their needs because stakeholders are
involved.
Internal stakeholders.
Amazon employees and managers are internal stakeholders.
External stakeholders.
Sellers, customer (buyers) and Government regulating bodies are external
Operational. Stakeholders.
Sellers, buyers and employees are operational Stakeholders.
Executive Stakeholders

Owner of amazon (Innovator) and Government regulating bodies.
Brief use case description.
According to Lethbridge and Laganiere (2017) explained that UML diagrams ensures most
software requirements are captured and this easy development.
Table 1 below shows brief use case descriptions online purchasing of products on amazon
website.
Use Case Brief Use Case Description
Create buyer’s account New Buyer enters details and the system
verifies details and assigns id number ,creates
buyers record in database then account is
created
The system server verifies Buyer details. The Amazon system server receives request
from buyer of creating new account .Details
are verified, verification code is send to buyer
by email or telephone. Buyer receives
verification code and insert it .Then
acceptance notification is sent to buy and can
successfully login on Amazon website.
Otherwise the amazon server can deny buyers
details because they are invalid .A notification
is sent to buyer to edit and try again.
Search product Buyer on successful login on amazon website,
Buyer searches item they need to buy. The
buyer insert product name or id in the search
form then products are displayed.
View product Buyer views products need to buy.
Add products to the shopping cart Buyers selects products and submits to
shopping cart.
View cart Buyer views product added on the shopping
cart.
Shipping product Buyer enters shopping details to where a
product is to be shipped.
Make Payment Buyer chooses available payment option on
amazon websites(FSA or HSA cards, credit or
Debit Card,Amazon.com store card,EBT card

and personal checking account)
Place order Buyer places order for products.
Supply products Seller supplies products to the amazon
Purchase confirmation Buyer receives email or call of confirmation
of order made even when cancelling is made
also an email is sent or customer care
department calls buyer.
Deliver products Seller arranges for delivery of product a buyer
bought

Figure 1 above shows use case diagram of Amazon.

Class diagram.
+

Task 2 - Group work.
Figure 2 below shows a class diagram of amazon warehouse.

Table 2 below shows lists of classes, attributes and relationships from amazon warehouse
subsystem.
Subsystem class Relationships Attributes
Amazon
Warehouse
Customer Orders
makes
Name
BuyerId
email
phoneNumber
Address
ProductStatus
Order receives OrderName
orderId
orderdate
shippingCost
payment
OrderStatus
Product packs
ship ships ShippingId
Shippingdate
ShippingCost
ShippingAddress
packer Packs
Manufacturer recalls Name
Address
Manufacturerid
ProductManufactured
Manager hires
staff caters Jobtitle
name
address
jobId
email
phoneNumber
shift worksonshift type
Time
date
casual Works as causal type
Time
date

REFERENCE:
Satzinger, W, J ,Jackson,B,R and Burd ,D,S (2012).System Analysis and Design in
A changing World (6th Ed).Boston Course Technology.
Sommerville, I (2015). Software engineering (10th Ed.).
University of St Andrews, Scotland: Pearson.
Pressman, S,R,Ph.D. (2018).Software Engineering. Practitioner’s Approach (8thEd.).
Inc., 1221 Avenue of the Americas, New York, McGraw-Hill.
Lethbridge, C, T and Laganiere,R.(2017) Object-Oriented Software Engineering:
Practical Software Development Using UML and Java (3ndEd.). New York, McGraw-Hill.