微信客服：xiaoxionga100
微信客服：ITCS521
INFS7007-英文代写
时间：2022-11-07
INFS7007
Online Shopping System
Analysis Report
Anissa Mashor | U7097898
2
Executive Summary
ZALORA was established in 2012 and currently is South-East Asia's leading online fashion
retailer that operates in Malaysia, Indonesia, Singapore, Philippines, Taiwan, Hong Kong,
Vietnam, Thailand, and Singapore. It serves as an online fashion as well as lifestyle retailer
that caters a variety of products for men, women, and children.
The e-commerce fashion retailer operates only on the website and mobile applications; hence
their online shopping system is vital to the organisation for customers to be able to purchase
their goods. The system provides value to ZALORA as customers can search for the product
of interest, check the product's availability and purchase products anywhere at any time. In
order to deliver a shopping-centric experience and meet the expectations of the customers,
online shopping system at ZALORA holds an essential role for the e-commerce as well as
providing the best way to interact and engage with online customers.
The report consists of a system overview which analyses ZALORA's online shopping system
scope, functions, features, constraints and system feedback. Furthermore, the report will
conduct a requirement analysis which is undertaken through survey and interview to
investigate the requirements needed by customers and management. It then proceeds with
providing system documentation based on traditional models (DFD, ERD and logic modelling)
as well as modern analysis using UML diagram. Based on the requirements gathering, below
are the requirements that are required by the users:
Functional requirements
1. Customer registration and login
2. Provide payment methods
3. Generate sales report for management
4. Generate order confirmation for the customer
Non-Functional requirements
1. 24/7 availability
2. Faults detection
3. Clean white background and black font
4. Secured database
3
Contents
Executive Summary ................................................................................................................................................ 2
1.0 Introduction .............................................................................................................................................. 5
1.1 Company Background ........................................................................................................................... 5
1.2 ZALORA's Online Shopping System and Rationale ................................................................................ 6
2.0 Systems Overview ..................................................................................................................................... 7
Scope .................................................................................................................................................................. 7
Major Functions ................................................................................................................................................. 8
System Features ................................................................................................................................................. 9
Constraints ......................................................................................................................................................... 9
Internal Constraints ....................................................................................................................................... 9
External Constraints ..................................................................................................................................... 10
System Feedback ......................................................................................................................................... 10
3.0 Requirement Analysis ............................................................................................................................. 11
3.1 Requirements Gathering .................................................................................................................... 11
3.1.1 Survey ......................................................................................................................................... 11
3.1.2 Interview .................................................................................................................................... 11
3.2 Requirements Identification .............................................................................................................. 12
3.3 Matching system functions with requirements ................................................................................ 13
4.0 Traditional Models .................................................................................................................................. 14
4.1 Process Models (DFD Diagram) .......................................................................................................... 14
4.1.1 Online Shopping System Context Diagram ................................................................................. 14
4.1.2 Online Shopping System Level 0 DFD ......................................................................................... 14
4.1.3 Level 1 DFD & Logic Model for Process 1.0 ................................................................................ 15
4.1.4 Level 1 DFD & Logic Model for Process 2.0 ................................................................................ 17
4.1.4 Level 1 DFD & Logic Model for Process 3.0 ................................................................................ 19
4.2 Entity-Relationship Diagram (ERD) .................................................................................................... 20
4.2.1 Data Dictionary ........................................................................................................................... 21
5.0 Modern Analysis ..................................................................................................................................... 25
5.1 Use-Case Diagram ............................................................................................................................... 25
5.1.1 Use-Case Description ..................................................................................................................... 26
5.2 Class Diagram ..................................................................................................................................... 28
5.3 Sequence Diagram - Customer ........................................................................................................... 29
5.3.1 Updated Class Diagram - Customer ................................................................................................ 29
5.4 Sequence Diagram – Sales Supervisor ............................................................................................... 30
5.4.1 Updated Class Diagram – Sales Supervisor ..................................................................................... 30
5.4 Sequence Diagram – Sales Manager .................................................................................................. 31
5.4.1 Updated Class Diagram – Sales Manager ....................................................................................... 31
4
5.5 State Diagram ..................................................................................................................................... 32
5.5 Activity Diagram – Customer .................................................................................................................. 34
5.5 Activity Diagram – Sales Supervisor ................................................................................................... 35
6.0 Reflection ................................................................................................................................................ 36
7.0 References ............................................................................................................................................... 38
8.0 Appendix ................................................................................................................................................. 39
List of Figures
Figure 1: ZALORA's Mobile Application .................................................................................................. 5
Figure 2: Online Shopping System Diagram ............................................................................................ 7
Figure 3: ZALORA's online shopping system context diagram .............................................................. 14
Figure 4: ZALORA online shopping system Level 0 ............................................................................... 14
Figure 5: ZALORA's online shopping system level 1 (process 1.0) ........................................................ 15
Figure 6: Process 1.3 decision tree ....................................................................................................... 16
Figure 7: ZALORA's online shopping system level 1 (process 2.0) ........................................................ 17
Figure 8: Process 2.3 decision tree ....................................................................................................... 18
Figure 9: ZALORA's online shopping system level 1 (process 3.0) ........................................................ 19
Figure 10: ERD of ZALORA's Online Shopping System .......................................................................... 20
Figure 11: Use-Case diagram ................................................................................................................ 25
Figure 12: Online shopping system class diagram ................................................................................ 28
Figure 13: Customer sequence diagram ............................................................................................... 29
Figure 14: Customer updated class diagram ........................................................................................ 29
Figure 15: Sales supervisor sequence diagram ..................................................................................... 30
Figure 16: Sales supervisor updated class diagram .............................................................................. 30
Figure 17: Sales manager sequence diagram ....................................................................................... 31
Figure 18: Sales manager updated class diagram ................................................................................. 31
Figure 19: Order confirmation status state diagram ............................................................................ 32
Figure 20: Updated class diagram for state diagram ............................................................................ 33
List of Tables
Table 1: Customer requirements identification .................................................................................... 12
Table 2: Management requirements identification .............................................................................. 12
Table 3: Matching system functions with user requirements .............................................................. 13
Table 4: Process 1.2 decision table ....................................................................................................... 16
Table 5: Process 1.2 reduced decision table ......................................................................................... 16
Table 6: Process 2.1 decision table ....................................................................................................... 17
Table 7: Process 2.2 reduced decision table ......................................................................................... 18
Table 8: Process 3.3 decision table ....................................................................................................... 20
Table 9: Data dictionary ........................................................................................................................ 21
Table 10: Browse product use-case description ................................................................................... 26
Table 11: Submit order use-case description ....................................................................................... 26
Table 12: Process and generate report use-case description ............................................................... 27
5
1.0 Introduction
1.1 Company Background
ZALORA was established in 2012 and currently is South-East Asia's leading online fashion
retailer that operates in Malaysia, Indonesia, Singapore, Philippines, Taiwan, Hong Kong,
Vietnam, Thailand, and Singapore. It serves as an online fashion as well as lifestyle retailer
that caters a variety of products for men, women, and children. The products include clothing,
shoes, accessories, sports, and beauty. ZALORA ensures that the fashion catered to different
countries and adapted based on the consumer's preferences with a combination of 500
international brands and locals that are offered. Recently, Zalora introduces ZMart to serve
the COVID-19 pandemic essentials such as masks and sanitisers along with household
essentials, health supplements and vitamins, baby supplies and selection of food from snacks,
pasta, baking supplies and alcohol (Tan, 2020). This allows customers to be able to purchase
their daily essentials alongside their fashion purchases.
Figure 1: ZALORA's Mobile Application
6
1.2 ZALORA's Online Shopping System and Rationale
ZALORA is an e-commerce fashion retailer that operates only on the website and mobile
applications; hence their online shopping system is vital to the organisation for customers to
be able to purchase their goods. According to Li et al. (2020), the online shopping system is a
type of electronic commerce that allows customers to directly purchase any product or
services from a seller using the internet. The system provides value to ZALORA as customers
can search for the product of interest, check product's availability and compare different
brands and prices simultaneously. From this, customers can save due to the discounted prices
and do not have to visit multiple offline stores for them to select the best option. Moreover, the
system provides a variety of payment and shipping method to suit the convenience of the
customers. The items that are purchased through ZALORA's online shopping system would
be delivered straight to the customer's home based on the estimated delivery date given
through the chosen courier. To produce a shopping-centric experience and meet the
expectations of the customers, online shopping system at ZALORA holds an essential role for
the e-commerce as well as providing the best way to interact and engage with online
customers.
According to Kemp & Moey (2019), online shopping system is essential to widen their reach
in the e-commerce market as Malaysia's e-commerce spending grew 24% from the year 2019
and 80% of internet users from the age of 16 to 64 years old have made an online purchase.
This has intrigued me in doing business analysis on Zalora's online shopping system as I am
one of the 80% internet users that loves shopping online and are one of Zalora's loyal
customers. Since I was young, walking around the shopping centre and buying clothes has
been a hassle for me since I would go through different clothing stores before deciding what I
would want to buy. Hence, I prefer purchasing my clothing and accessories from online stores
as it allows me to compare different brands at once and ensures that the prices are lower than
retail shops.
7
2.0 Systems Overview
Figure 2: Online Shopping System Diagram
Scope
The online shopping system that implemented on the ZALORA website and mobile application
facilitates the user to be able to perform purchase transactions of products without needing to
travel to the shops. The online shopping system offers product images, description, and price.
The system provides benefits such as multiple payment methods, shipping options,
discounts/coupons availability as well as the ability to compare different brands at once.
Moreover, the online shopping cart is included that allows customers to be able to browse
various products and selecting the items that they would like to purchase and even remove
before placing the final order.
On the other hand, the online shopping system excludes other functional systems that exist in
ZALORA organisation. For example, the system would exclude inventory system, customer
management system, logistic system, the payment system that are used explicitly by specific
functional departments and third parties.
8
Major Functions
ZALORA's online shopping system allows to create and enhance the experience by easing
the transaction between customers and organisation by offering different functions to support:
1. Registering Customer and Login Details
To make a purchase and have exclusive access to discounted deals, users are required to
register with the system. The system provides a function that allows users to register by
providing their customer details and information needed for shipping and billing. Once the user
has noted, the user would be able to login into their account, and all the information submitted
during the registration will be stored in a database which is available for authorised ZALORA's
employees.
2. Adding Products into Shopping Cart
The shopping cart will enable users that are shopping with ZALORA to select the products
that they would like to purchase and proceed to checkout for payment. The shopping cart
function would assist by summarising the user requests based on what they have selected
from the product catalogue. This would allow the user to check the shopping cart and can
cancel/modify the products that are in it.
3. Multiple Payment Methods
The online shopping system consists of a payment system that would account for the
interactions between the parties involved in the financial transaction. The system allows the
customers to pay for their products through other payments method such as using credit/debit
card, e-wallet application, and online transfer. This function would allow the system to check
with the bank and e-wallet merchants to authorise the payments. If the bank/e-wallet merchant
rejects the request, the transaction cannot be deleted, and the order will be cancelled. For
those who do not have online banking or e-wallet application, users are able to make payment
through convenience store such as 7-Eleven.
4. Generate Order Confirmation and Sales Report
Order management function would allow for the system to summarise all details on shipment
and order to make the proper delivery necessary. The function enables the system to generate
order confirmation for the users, which consist of details of their ordered products and shipping
details from their registration database. Moreover, the order confirmation details would assist
warehouse staff to pack the necessary items and pass to the logistics team.
9
System Features
1. Menu Navigation with Search Bar and Product Categories
The system has a user-friendly navigational bar whereby the layout is transparent, and product
categories are clearly divided. Each of the product categories is divided by subsections which
will allow the user to easily search for products based on the brand, product type or price
range. Furthermore, the on-site search would enable users to find what they are looking for
within a short amount of time.
2. High Definition Photos with Image with Image Zoom
Given that the nature of Zalora's business is online, product images play a vital role when
users are purchasing. Since users are unable to hold and touch the product, the system
requires this feature in which for each product, at least three high-quality images are showing
the work from different angles. Furthermore, the feature consists of a zoom which gives the
user option to see a given part of the product.
3. Detailed Product Description
Each of the products listed on the online shopping system is provided with clear and extensive
bullet points description. The feature allows the product description to be concise, quick, and
easy to read.
4. Order Tracking
The feature allows users to see the process of their product delivery and predict the arrival
time. It will enable users to track their order manually without needing to email or call customer
service enquiring on their order delivery.
Constraints
Internal Constraints
The internal constraints that can apply to ZALORA's online shopping system are in terms of
its system's architecture. The constraints could be that when the server may experience
downtime. According to Warrington (2019), server downtime is one of the crucial issues faced
by the organisation as 90% of companies suffers unplanned downtime with an average cost
of $1.55 million each year. Given that ZALORA businesses are taking place online; hence this
constraint heavily affects the organisation as they are entirely dependant on IT infrastructures
and system architectures which keep the internet services running smoothly. When the server
10
is down, ZALORA customers are unable to access the mobile application and website,
therefore not capable of purchasing the products. This would result in ZALORA losing sales
and revenue.
External Constraints
The external constraints that could apply to ZALORA's online shopping system is based on
the government's rule and regulations. When operating in Malaysia, ZALORA would need to
be abide by the Data Protection Act 2010. The online shopping system requires customers to
register and store their personal information that includes name, address, email address and
possibly their financial report. Hence, the constraints occur in which ZALORA would need to
handle the data in compliance with the law through holding the information that is relevant to
the business and ensuring that their personal information are always protected against the
third party.
Besides that, the constraints that may apply is that ZALORA experience a hacking situation
that could negatively affect the business's reputation and halts the online shopping system
operations. According to Meikeng (2020), cybersecurity which involves unethical hacking have
spiked by 82.5% compared to the year 2019. Unethical hacking on ZALORA's online shopping
system would negatively affect the organisation as it would affect the user experience when
shopping through the website or mobile application. Further, it causes the customer not feeling
safe as they are aware the hacker may breach their private confidential information.
System Feedback
The system’s feedback for Zalora’s online shopping system is balancing when the customer
user receives notification that the payment status for their order failed which in turn the
customer will require to input a new payment method to purchase the order. The change of
the system’s output causes through the environment a change in input that will tend to return
the output to its original value which is the payment has been successful.
Besides that, the system’s feedback for ZALORA online shopping system is positive when
there is an increase in revenue. It can be assumed that previously that customers shop
traditionally by going to the shops rather than purchasing online. Hence, the online shopping
system provides more customers in shopping with ZALORA, which increases the
organisation’s revenue. This allows for ZALORA to enhance their online shopping system by
providing additional features, functions, and security to provide a great user experience.
11
3.0 Requirement Analysis
3.1 Requirements Gathering
3.1.1 Survey
The first requirement gathering method that are used to develop a set of user requirements
for ZALORA's online shopping system are by using a survey that are done through
questionnaire. The method was chosen because questionnaire allows to gather responses
from many respondents within a short time. This is supported by Elijah et al. (2017) as survey
are the popular method for researchers and system analyst in gathering responses from large
respondents as it is effective and economically. The survey is given to customers to find out
their requirements and expectations for the online shopping system. The survey distribution
method that are being used is the snowball effect whereby the questionnaires are passed to
family and friends who have purchased through online shopping system previously. From
there, the questionnaire will be passed from family and friends to people that they knew whom
have experienced the online shopping system. The survey is accompanied with guidelines
and instructions for the respondents and it was done individually. The method provided the
ability to gather information from respondents on their own positive/negative experience using
the system which would result in unbiased answers.
3.1.2 Interview
The second requirement gathering method that are used is interview. The method chosen
would enable me to obtain feedback on the system's requirements from ZALORA's
employees. To gather the requirements, I had set an appointment with three employees from
ZALORA organisation. The interview with the employees is done one-on-one ensuring that I
would understand the user's environment using the system as well as their individual
requirement on the system. The technique was chosen to gather requirements from the
business side as it would provide an opportunity for employees to respond freely and openly
to the questions. It would also give me the opportunity to ask any follow-up questions on their
standard operating procedure for the system and get an instant back from the interviewees.
This has been supported by Rueda, Panach & Distante (2020) as interview is the fastest
method in order to gather system requirements.
12
3.2 Requirements Identification
Based on the requirements gathering that has been conducted, below are the requirements
according to the user type.
3.2.1 Customer
Table 1: Customer requirements identification
Req
#
Requirements
Mandatory 1 The system will provide list of products with prices.
2 The system will be available 24/7 and generate order
confirmation after purchasing the product.
3 The system will provide a secured payment sub-system and
database.
Optional 4 The system will have provided a clear instruction and guidance
on user registration and purchasing a product.
5 The system will visually track the product's order
Frill 6 The system will feature the user's recently viewed products.
7 The system will produce sound once order has been confirmed
3.2.2 Management
Table 2: Management requirements identification
Req
#
Requirements
Mandatory 1 The system should be able to generate platform's data to generate
report.
2 The system should retrieve customer's order and delivery detail in
real-time.
13
Optional 3 The system will securely store and view sales data.
4 The system will allow to feature selected products for campaign.
Frill 5 The system will allow different colour background.
6 The system will create a sound when order is received.
3.3 Matching system functions with requirements
Table 3: Matching system functions with user requirements
Functions Req# Requirements
Functional Requirements
1. Customer
registration and
login
4 • The system should be easy to use for various
customer age group with different level of computer
skills.
2. Provide payment
methods
3 • The system should detect unauthorised access
• The transaction using the system should be secure
and using encryption mechanism
3. Generate sales
report for
management
1 & 2 • The system should include the list of all customer's
purchases with the sales value and its uplift
compared to the previous month
• The system can display all user transactions for
management
4. Generate order
confirmation for
customer
2 • The system should include order confirmation that
combines their purchases along with their customer
and shipping details.
Non-Functional Requirements
24/7 availability 2 • The system should have a backup server that allows
customers to purchase online anytime at anywhere
Clean white
background and black
font
3 • The system should have a clean white background
and black font throughout the product pages so that
it provides customer with good customer journey and
can easily read.
Secured database 1 & 3 • The system should have an encrypted database with
high level of security to avoid potential unauthorised
access from unknown third party.
14
4.0 Traditional Models
This section presents the traditional models that are constructed using data flow diagram, logic
modelling (structured English, Decision table and decision tree) for ZALORA’s online shopping
system.
4.1 Process Models (DFD Diagram)
4.1.1 Online Shopping System Context Diagram
Figure 3: ZALORA's online shopping system context diagram
4.1.2 Online Shopping System Level 0 DFD
Figure 4: ZALORA online shopping system Level 0
15
4.1.3 Level 1 DFD & Logic Model for Process 1.0
The level 1 DFD shows the breakdown of the activities of 1.0 process. The activities would
include the system receiving the product selection from the customer, recording the order into
relevant data stores, and verifying the product selection.
Figure 5: ZALORA's online shopping system level 1 (process 1.0)
Logic Model for Process 1.1 – Structured English
RECEIVE product selection from customer
DO WHILE there is product selection from customer to process
BEGIN IF
IF product selection = > 1
THEN record product selection
ELSE compute error
END-IF
END-DO WHILE
UNTIL there is no more problem selection
16
Logic Model for Process 1.2 – Decision Table
Table 4: Process 1.2 decision table
Conditions
Rules
1 2 3 4 5 6
Product have Product ID Y Y Y N N N
Product selection <1 1 >1 <1 1 >1
Course of Action
Record in Product DB X X
Record in Add to Cart DB X X
Compute Error X X X X
Table 5: Process 1.2 reduced decision table
Conditions
Rules
1 2 3 4
Product has Product ID Y Y Y N
Product selection <1 1 >1 -
Course of Action
Record in Product DB X X
Record in Add to Cart DB X X
Compute Error X X
Logic Model for Process 1.3 – Decision Tree
Figure 6: Process 1.3 decision tree
17
4.1.4 Level 1 DFD & Logic Model for Process 2.0
The level 1 DFD below shows the breakdown of the activities of 2.0 process. The activities
would include the system receiving the confirmed products, calculate total price, collect
payment as well as record and send relevant data.
Figure 7: ZALORA's online shopping system level 1 (process 2.0)
Logic Model for Process 2.1 - Decision Table
Table 6: Process 2.1 decision table
Conditions Rules
1 2 3 4 5 6 7 8 9 10 11 12 13
Type of Customer N N N N N N E E E E E E E
Number of Items
Order
<1 <1 1 1 >1 >1 <1 <1 1 1 >1 >1 >1
Subscribed Priority
Membership
Y N Y N Y N Y N Y N Y N N
Course of Actions
Accept Order X X X X X X X X X
Reject Order X X X X X
Calculate Price X X X X X X X X X
10% Discount
Eligibility
X X X X
20% Discount
Eligibility
X X X X
Priority Shipping X X X X
18
Table 7: Process 2.2 reduced decision table
Conditions Rules
1 2 3 4 5 6 7 8 9
Type of Customer - N N N N E E E E
Number of Items Order <1 1 1 >1 >1 1 1 >1 >1
Subscribed Priority
Membership
- Y N N Y Y N Y N
Course of Actions
Accept Order
X X X X X X X X
Reject Order X
X
Calculate Price X X X X X X X X
10% Discount Eligibility
X X
X
20% Discount Eligibility
X
X X
X
Priority Shipping
X
X X
X
Logic Model for Process 2.2 – Decision Tree
Figure 8: Process 2.3 decision tree
Logic Model for Process 2.3 – Structured English
RECEIVE payment status
RECEIVE customer order
IF payment status = "success"
THEN generate order confirmation and send to customer,
send delivery order to warehouse,
update order status to Customer DB & order data to Order DB
ELSE compute error
END-IF
SEND order status to Customer
19
4.1.4 Level 1 DFD & Logic Model for Process 3.0
The level 1 DFD below shows the breakdown of the activities of 3.0 process. The activities
would include the system receiving the relevant data from the datastore, transform the data
into report as well as store and send report.
Figure 9: ZALORA's online shopping system level 1 (process 3.0)
Logic for Process 3.1 – Structured English
RECEIVE monthly order details from order DB
RECEIVE inventory level from Product DB
DO WHILE there are monthly order details to process for the month
BEGIN IF
IF product selection = > 1
THEN create report data
ELSE compute error
END-IF
END-DO WHILE
UNTIL there are no more order details for the month
Logic for Process 3.2 – Structured English
RECEIVE report data
RECEIVE monthly sales analysis from Sales Supervisor
BEGIN IF
If report >0
THEN generate formatted report
ELSE compute error
END-IF
20
Logic for Process 3.3 – Decision Table
Table 8: Process 3.3 decision table
Conditions
Rules
1 2 3 4
Report includes monthly sales analysis Y Y N N
Report data is accurate and validated Y N Y N
Course of Action
Record in Management DB X
Send Report to Sales Manager X X
Compute Error X X
4.2 Entity-Relationship Diagram (ERD)
Figure 10: ERD of ZALORA's Online Shopping System
21
4.2.1 Data Dictionary
Table 9: Data dictionary
Entry Name Entry
Description
Column Name Column
Description
Data
Type
Field
Size
Primary
Key
Customer Potential or
existing
individuals
that would
like to
purchase
using the
Zalora's
Online
shopping
system.
Disc Rate Discount rate
that are eligible
based on their
purchase
Int 2 FALSE
Address The address of
the customer
for shipping
String 100 FALSE
City The city that
customers live
in.
String 20 FALSE
Postcode The postage of
the customer's
address.
Int 10 FALSE
Number The number of
the customers
house
Int 4 FALSE
Street The street
where the
customer lives.
String 50 FALSE
User The
individuals
that are using
the online
shopping
system
User ID For the unique
identification of
users records.
Int 10 TRUE
Username The username
that users need
to key in when
login to the
system.
String 20 FALSE
Name The name of the
user
String 20 FALSE
EmailAddress The email of the
user
String 20 FALSE
PhoneNo The phone
number of the
user
Int 10 FALSE
DOB The user’s date
of birth
Date 10 FALSE
Employee Individual
who
performs
certain
functions
associated
with a
Level_Access Different
employee will
be given
different level
of access in the
company.
String 10 FALSE
22
particular
position.
Manager Individual
who
responsible
for
controlling or
administering
an
organisation
or group of
staff.
Grade Different grade
to differentiate
between
positions, skill
sets and
responsibilities.
String 20 FALSE
Supervisor The
individual
that is
responsible
for the
productivity
and actions
of the
employee
SupervisorType Different
supervisor that
are from
different
department.
String 20 FALSE
Payment The amount
paid or
payable for
the purchase
order
PaymentID Unique code for
each transaction
made.
Int 10 FALSE
Date Exact date that
the payment
was made.
Date 10 FALSE
Payment
Merchant
Where all the
payment
transaction
are verified.
MerchantID Unique code for
to identify
payment
merchant
Int 30 TRUE
MerchantName Name of the
payment
merchant that is
available on
Zalora
String 20 FALSE
Order
Confirmation
The details of
order
confirmation
are
generated
Order_Status The status of
the order
String 10 FALSE
Delivery Partner The 3rd party
that will be
used to help
deliver the
product.
PartnerID The unique
number that
identify the
partner.
Int 30 TRUE
PartnerName The name of the
delivery partner
that is used for
delivery.
String 20 FALSE
23
Order The item that
the user
wanted to
purchase.
OrderID Number system
that help keep
track of the
order.
Int 30 TRUE
ProductID Specific code for
the item to help
identify it
easier.
Int 30 FALSE
Total_Price The total price
of the products
in the order
Int 10 FALSE
Qty The total
amount of item
that the user
have purchase.
Int 5 FALSE
OrderDate The date that
the user made
the order.
Date 10 FALSE
Product The product
that is being
sold on the
website.
Name The name of the
specific product.
String 30 FALSE
Image An image of
what the
product will
look like.
Byte 100 FALSE
ProductID Specific code for
the item to help
identify it
easier.
Int 30 TRUE
PurchasePrice The original
price that the
buyer purchase
the product.
Int 10 FALSE
Stock_Level The amount of
item that is left
in the inventory.
String 30 FALSE
SalePrice The price that is
being sold to
the user.
Int 10 FALSE
Shopping Cart Section
where it
shows all the
product that
the customer
have chosen.
Total_Price Amount shown
of the total
product in the
shopping cart
Int 10 FALSE
ShoppingCartID Specific code for
shopping cart.
Int 20 TRUE
Date The date users
purchase the
product.
Date 10 FALSE
Product_Name The name of
product that are
available in
Zalora
Int 10 FALSE
24
Quantity Amount of the
individual
product that is
in the cart.
Int 5 FALSE
Price Amount of the
specific product.
Int 5 FALSE
Warehouse Where all the
inventories
are kept.
WarehouseID Specific number
to identify the
warehouse.
Int 10 TRUE
PhoneNo The number for
the warehouse
Int 15 FALSE
WarehouseNam
e
The name for
the warehouse
String 20 FALSE
Location Where the
warehouse is
located
String 20 FALSE
Categories Different
product
categories
that are
available on
Zalora
Category_Name The name of the
category
String 10 FALSE
25
5.0 Modern Analysis
The section presents the modern analysis that are constructed using UML diagram (Use-Case
Diagram, Class Diagram, Sequence, State Machine and Activity Diagram). For the UML
diagram, I have decided to narrow the scope that consists of browsing product, submitting
order as well as processing and generate report. I have reduced the scope of the online
shopping system by removing payment sub-system and logistic system to focus on the specific
functions mentioned.
5.1 Use-Case Diagram
Figure 11: Use-Case diagram
26
5.1.1 Use-Case Description
Table 10: Browse product use-case description
Use case name: Browse Products
Actor(s): Customer
Description: Viewing the products that are available from Zalora and enable for existing
customers to add to shopping cart and new customers to register for an account before
adding to shopping cart.
Steps: Information required [produced]:
Customer search for items Product ID [Product name]
Customer browse for items Product name, price, and stock availability
New or existing customer inserts an item
into the shopping cart
[Shopping Cart ID, Date, Product ID,
Product Name, Quantity, Price]
If the customer is already an existing
customer, request login details
Username and Password [User ID]
If the customer is a new customer, then
register an account and assign a unique
username
[Username, Password, User ID, Name,
Address, Telephone Number, Email
Address]
Table 11: Submit order use-case description
Use case name: Submit Order
Actor(s): Customer
Description: submit order and make payment when the customer have decided on what
to purchase from the online shopping system.
Steps: Information required [produced]:
Customer view and update shopping cart Shopping Cart ID, Date, Product ID,
Product Name, Quantity, Price
Customer checks out the shopping cart Shopping Cart ID, Date, Product Name,
Quantity, Price [Order]
System retrieves the order Order
System calculates the total price of the
products
Product Name, Product Quantity, Price
27
System retrieves customer details Name, Address, Telephone Number, Email
Customer updates shipping and billing
information
[Address]
System forwards customer to payment
sub-system.
Table 12: Process and generate report use-case description
Use case name: Process and Generate report
Actor(s): Sales Supervisor, Sales Manager
Description: retrieving financial data and analysis and produce the sales report
Steps: Information required [produced]:
System retrieves monthly order data Monthly sales
System retrieves current inventory level Product inventory level
System send monthly order and current
inventory level to sales supervisor
Sales supervisor provides monthly sales
analysis
[monthly sales analysis]
System combines the retrieved data and
monthly sales analysis
Monthly sales, product inventory level,
monthly sales analysis
System produces the management report Monthly order data, current inventory level
data, monthly sales analysis [management
report]
System sends the management report to
Sales Manager
Management report
28
5.2 Class Diagram
Figure 12: Online shopping system class diagram
29
5.3 Sequence Diagram - Customer
Figure 13: Customer sequence diagram
5.3.1 Updated Class Diagram - Customer
Figure 14: Customer updated class diagram
30
5.4 Sequence Diagram – Sales Supervisor
Figure 15: Sales supervisor sequence diagram
5.4.1 Updated Class Diagram – Sales Supervisor
Figure 16: Sales supervisor updated class diagram
31
5.4 Sequence Diagram – Sales Manager
Figure 17: Sales manager sequence diagram
5.4.1 Updated Class Diagram – Sales Manager
Figure 18: Sales manager updated class diagram
32
5.5 State Diagram
The possible state that the order confirmation can be is in checking the status of the order and see if
the order has been paid. Hence, an additional attribute and attribute actions are added into the Order
Confirmation class definition:
Figure 19: Order confirmation status state diagram
33
Updated Class Diagram
Figure 20: Updated class diagram for state diagram
34
5.5 Activity Diagram – Customer
35
5.5 Activity Diagram – Sales Supervisor
36
6.0 Reflection
Sir Arthur Conan Doyle once quoted "data, data, data! I cannot make bricks without clay". The
quote remembers me back to my time working at an e-commerce company as a senior analyst
in campaign in which my job heavily relies on the use of data and information system to
analyse the performance of my campaigns as well as making decisions to improve my future
campaigns. Based on my past working experience, this has intrigued me in analysing an online
shopping system in order to understand its complex structure, components and sub-systems
that lies within the online shopping system. As an online shopping enthusiast, I was also
interested how the system provides the convenience for online shoppers to purchase products
regardless of the time using smartphone or computer. Furthermore, it interests me in
understanding how the data are flowed through the system and used by different functions in
the organisation to complete an order and deliver to the customers.
The online shopping system analysis process that was done throughout the twelve weeks
have made me realise on how data is important to an organisation in order to provide great
customer experience. According to Packer (2018), functional excellence does not guarantee
overall success and working with different functions altogether provides the greatest possibility
for superior performance. Hence, I learnt that using bridging the gap between different
functions using the system gives the benefit to an organisation which can be done by visually
representing the interrelationship between the components of the online shopping system
using diagram modelling. The use of data flow diagram enables me to understand how the
data inputted from the customer are flowed throughout the system to different parts of the
organisation and processed to generate an output to the end user such as order confirmation
and sales report. Moreover, the different diagramming concepts learnt allows me to further
comprehend the relationships between the entities and their attributes in the system. I have
developed an increasing respect for and fascination on the number of ways that individuals
and different functions in the organisation can benefit from the online shopping system. For
example, the online shopping system processes the customer's order and forwards the order
to warehouse so that the workers in the department are able to pick and pack the goods as
well as giving the parcel to delivery partner for delivery. I have come to admire the power that
the diagramming concepts and tools that I have learnt throughout the twelve weeks can bring
to organisational matters so it could be improved and increase in efficiency.
During the analysis process for the online shopping system, I have trouble in understanding
certain system concepts such as data flow diagram and logic modelling. Given that I am
previously a business major student, learning about systems and diagramming tools are new
and foreign to me hence I did not understand on the steps that need to be taken to start the
37
diagram. In order to overcome the difficulty, I found that listening the lecture and tutorials
multiple times helps me in finding the connections between the diagram components and
grasping the concept. Furthermore, I have realised that YouTube consists of various tutorial
videos that you can watch and understand the concept further. The step-by-step videos on
creating diagram have helped me tremendously in creating my diagrams for the assignment.
Nevertheless, the assignment has provided me a great insight on becoming a business
analyst. Nowadays, business analysts require to help organisations implement technology
solutions in cost-effective way by determining the requirements and communicating the
requirements clearly to the stakeholders. The role and responsibilities heavily rely on the
system development life cycle stages whereby the assignment allows us to practice the
system analysis and requirement phase in real-life. For example, the assignment requires me
to conduct requirement gathering for Zalora's online shopping system hence I would need to
conduct survey and interview with Zalora's management employees as well as Zalora's
customers. The requirement gathering has helped me in identifying the crucial functions that
is needed from the stakeholder which then proceeded with drawing system diagram. Drawing
system diagram (DFD, ERD and UML) also provides the assignment value as it allows me to
see the different components of the system. The diagram visually illustrates the relationships
between entities and attributes as well as identifying the data needed for input and process to
generate the output. Hence, the tools learnt would be beneficial for me to implement in my
working life in the future.
Overall, the assignment has improved my knowledge on system analysis and the feedback
from the lecturer from my mid-term report progress have enable me to develop my project
further. However, the current assignment have only enable me to analyse the current functions
of Zalora's online shopping system; and the assignment can be further improved by including
the requirements that are needed as stated by the end-users based on the requirement
gathering phase.
38
7.0 References
Elijah, J., Mishra, A., Mathew Chukwu Udo, E., Abdulganiyu, A., & Musa Aibinu, A. (2017).
Survey on Requirement Elicitation Techniques: It's Effect on Software Engineering.
International Journal of Innovative Research in Computer and Communication
Engineering, 5(5), 9201–9215. https://doi.org/10.15680/IJIRCCE.2017
Kemp, S., & Moey, S. (2019). Ecommerce in Malaysia in 2019. Data Reportal.
https://datareportal.com/reports/digital-2019-ecommerce-in-malaysia
Li, X., Zhao, X., Xu, W. (Ato), & Pu, W. (2020). Measuring ease of use of mobile applications
in e-commerce retailing from the perspective of consumer online shopping behaviour
patterns. Journal of Retailing and Consumer Services, 55, 102093.
https://doi.org/10.1016/j.jretconser.2020.102093
Meikeng, Y. (2020). Cybersecurity cases rise by 82.5%. The Star.
https://www.thestar.com.my/news/focus/2020/04/12/cybersecurity-cases-rise-by-825
Packer, D. W. (2018). Taking a Systems View: A Reflection.
https://thesystemsthinker.com/taking-a-systems-view-a-reflection/
Rueda, S., Panach, J. I., & Distante, D. (2020). Requirements elicitation methods based on
interviews in comparison: A family of experiments. Information and Software
Technology, 126, 106361. https://doi.org/10.1016/j.infsof.2020.106361
Tan, C. (2020). Online Fashion Retailer Zalora Is Now Selling Essential Supplies Like Face
Masks, Snacks, Health Supplements & Wine. Today Online.
https://www.todayonline.com/8days/liveandlearn/style/online-fashion-retailer-zalora-
now-selling-essential-supplies-face-masks
Warrington, R. (2019). What Happens When Your Servers Go Down. VXchnge.
https://www.vxchnge.com/blog/when-servers-go-down
39
8.0 Appendix
Appendix A: Management Requirement Gathering Interview Questions (SAMPLE)
Interview Outline
Interviewee: Interviewer: Anissa MD Mashor
Location: ZALORA HQ, Kuala Lumpur Date: 23 Sept 2020
Objectives: To investigate the system
requirements needed
Reminder:
General Observation: The interviewee will involve directly with the system
Interviewer Interviewee
Question 1:
What is your position in ZALORA?
Question 3:
Is your usage of the current online shopping
system low, medium, or high?
Question 2:
Do you think the online shopping system provided
you with necessary functions for your task and
responsibilities?
Question 3:
What is the information that you needed from the
system?
40
Question 4:
How does the online shopping system add value
to the team and the entire organisation?
Question 5:
What effect, if any do you think a user-friendly
online shopping system would have on employees
in completing their work?
Question 6:
If any, can you describe the problems that you
faced when using the system?
Question 7:
What can the system do to better support your
responsibilities?
41
Appendix B: Customer Requirement Gathering Interview Questions (SAMPLE)
Introduction
Providing the best online shopping system is the main priority for ZALORA as it would provide
customers with great experience when shopping online. This survey will help us on gathering
functional requirements of customer as well as their experience when using online shopping system.
All the data collected from this survey will help me in gathering the functional requirements for
ZALORA online shopping system. All responses from this survey will be kept anonymous and
confidential.
Thank you for completing this survey.
The objectives of this survey are:
• To find out the functional requirement for ZALORA's online shopping system.
• To know customer's experience when booking using the online shopping system.
Section A: Demographic
Please tick one for each question.
1. Age:
Under 18 years old □ 25 – 34 years old
18 - 24 years old □ 35 – 44 years old
45 – 54 years old □ Above 55 years old
2. Your computer's skill
Beginner
Intermediate
Advanced
3. Averagely, how often do you shop online in the last 6 months?
Everyday
Weekly
Once every two weeks
Once a month
Every 2 or 3 months
Section B: Psychographic
6. Overall, are you satisfied with your experience using online shopping system?
Yes (why):______________________________________________________________
No (why):_______________________________________________________________
42
4. How important is these functions in the online shopping system?
Please choose the best answer for the following by ✓ at the boxes below.
Really not
important
Not important Neutral Important Really
Important
a) User
Account
Registrati
on
b) Generatin
g Order
Confirmat
ion
c) Shopping
Cart
d) Secured
Payment
System.
e) Live Chat
Support
f) Order
Tracking
5. For each of the following statement, mark one box that best describe your experience with
the online shopping system.
(Range from 1 = Strongly Disagree to 5 = Strongly Agree)
1 2 3 4 5
a) I found the system was easy to use.
b) The system would generate order
confirmation immediately after I have
purchased the product.
c) I found the various functions in this
system were well-integrated
d) I found the system very cumbersome to
use
e) I felt very confident using this system
f) I needed to learn a lot of things before
using this system
43
7. Are there any functions that you would like to add in the online shopping system?
Thank you for participating.
Online Shopping System
Analysis Report
Anissa Mashor | U7097898
2
Executive Summary
ZALORA was established in 2012 and currently is South-East Asia's leading online fashion
retailer that operates in Malaysia, Indonesia, Singapore, Philippines, Taiwan, Hong Kong,
Vietnam, Thailand, and Singapore. It serves as an online fashion as well as lifestyle retailer
that caters a variety of products for men, women, and children.
The e-commerce fashion retailer operates only on the website and mobile applications; hence
their online shopping system is vital to the organisation for customers to be able to purchase
their goods. The system provides value to ZALORA as customers can search for the product
of interest, check the product's availability and purchase products anywhere at any time. In
order to deliver a shopping-centric experience and meet the expectations of the customers,
online shopping system at ZALORA holds an essential role for the e-commerce as well as
providing the best way to interact and engage with online customers.
The report consists of a system overview which analyses ZALORA's online shopping system
scope, functions, features, constraints and system feedback. Furthermore, the report will
conduct a requirement analysis which is undertaken through survey and interview to
investigate the requirements needed by customers and management. It then proceeds with
providing system documentation based on traditional models (DFD, ERD and logic modelling)
as well as modern analysis using UML diagram. Based on the requirements gathering, below
are the requirements that are required by the users:
Functional requirements
1. Customer registration and login
2. Provide payment methods
3. Generate sales report for management
4. Generate order confirmation for the customer
Non-Functional requirements
1. 24/7 availability
2. Faults detection
3. Clean white background and black font
4. Secured database
3
Contents
Executive Summary ................................................................................................................................................ 2
1.0 Introduction .............................................................................................................................................. 5
1.1 Company Background ........................................................................................................................... 5
1.2 ZALORA's Online Shopping System and Rationale ................................................................................ 6
2.0 Systems Overview ..................................................................................................................................... 7
Scope .................................................................................................................................................................. 7
Major Functions ................................................................................................................................................. 8
System Features ................................................................................................................................................. 9
Constraints ......................................................................................................................................................... 9
Internal Constraints ....................................................................................................................................... 9
External Constraints ..................................................................................................................................... 10
System Feedback ......................................................................................................................................... 10
3.0 Requirement Analysis ............................................................................................................................. 11
3.1 Requirements Gathering .................................................................................................................... 11
3.1.1 Survey ......................................................................................................................................... 11
3.1.2 Interview .................................................................................................................................... 11
3.2 Requirements Identification .............................................................................................................. 12
3.3 Matching system functions with requirements ................................................................................ 13
4.0 Traditional Models .................................................................................................................................. 14
4.1 Process Models (DFD Diagram) .......................................................................................................... 14
4.1.1 Online Shopping System Context Diagram ................................................................................. 14
4.1.2 Online Shopping System Level 0 DFD ......................................................................................... 14
4.1.3 Level 1 DFD & Logic Model for Process 1.0 ................................................................................ 15
4.1.4 Level 1 DFD & Logic Model for Process 2.0 ................................................................................ 17
4.1.4 Level 1 DFD & Logic Model for Process 3.0 ................................................................................ 19
4.2 Entity-Relationship Diagram (ERD) .................................................................................................... 20
4.2.1 Data Dictionary ........................................................................................................................... 21
5.0 Modern Analysis ..................................................................................................................................... 25
5.1 Use-Case Diagram ............................................................................................................................... 25
5.1.1 Use-Case Description ..................................................................................................................... 26
5.2 Class Diagram ..................................................................................................................................... 28
5.3 Sequence Diagram - Customer ........................................................................................................... 29
5.3.1 Updated Class Diagram - Customer ................................................................................................ 29
5.4 Sequence Diagram – Sales Supervisor ............................................................................................... 30
5.4.1 Updated Class Diagram – Sales Supervisor ..................................................................................... 30
5.4 Sequence Diagram – Sales Manager .................................................................................................. 31
5.4.1 Updated Class Diagram – Sales Manager ....................................................................................... 31
4
5.5 State Diagram ..................................................................................................................................... 32
5.5 Activity Diagram – Customer .................................................................................................................. 34
5.5 Activity Diagram – Sales Supervisor ................................................................................................... 35
6.0 Reflection ................................................................................................................................................ 36
7.0 References ............................................................................................................................................... 38
8.0 Appendix ................................................................................................................................................. 39
List of Figures
Figure 1: ZALORA's Mobile Application .................................................................................................. 5
Figure 2: Online Shopping System Diagram ............................................................................................ 7
Figure 3: ZALORA's online shopping system context diagram .............................................................. 14
Figure 4: ZALORA online shopping system Level 0 ............................................................................... 14
Figure 5: ZALORA's online shopping system level 1 (process 1.0) ........................................................ 15
Figure 6: Process 1.3 decision tree ....................................................................................................... 16
Figure 7: ZALORA's online shopping system level 1 (process 2.0) ........................................................ 17
Figure 8: Process 2.3 decision tree ....................................................................................................... 18
Figure 9: ZALORA's online shopping system level 1 (process 3.0) ........................................................ 19
Figure 10: ERD of ZALORA's Online Shopping System .......................................................................... 20
Figure 11: Use-Case diagram ................................................................................................................ 25
Figure 12: Online shopping system class diagram ................................................................................ 28
Figure 13: Customer sequence diagram ............................................................................................... 29
Figure 14: Customer updated class diagram ........................................................................................ 29
Figure 15: Sales supervisor sequence diagram ..................................................................................... 30
Figure 16: Sales supervisor updated class diagram .............................................................................. 30
Figure 17: Sales manager sequence diagram ....................................................................................... 31
Figure 18: Sales manager updated class diagram ................................................................................. 31
Figure 19: Order confirmation status state diagram ............................................................................ 32
Figure 20: Updated class diagram for state diagram ............................................................................ 33
List of Tables
Table 1: Customer requirements identification .................................................................................... 12
Table 2: Management requirements identification .............................................................................. 12
Table 3: Matching system functions with user requirements .............................................................. 13
Table 4: Process 1.2 decision table ....................................................................................................... 16
Table 5: Process 1.2 reduced decision table ......................................................................................... 16
Table 6: Process 2.1 decision table ....................................................................................................... 17
Table 7: Process 2.2 reduced decision table ......................................................................................... 18
Table 8: Process 3.3 decision table ....................................................................................................... 20
Table 9: Data dictionary ........................................................................................................................ 21
Table 10: Browse product use-case description ................................................................................... 26
Table 11: Submit order use-case description ....................................................................................... 26
Table 12: Process and generate report use-case description ............................................................... 27
5
1.0 Introduction
1.1 Company Background
ZALORA was established in 2012 and currently is South-East Asia's leading online fashion
retailer that operates in Malaysia, Indonesia, Singapore, Philippines, Taiwan, Hong Kong,
Vietnam, Thailand, and Singapore. It serves as an online fashion as well as lifestyle retailer
that caters a variety of products for men, women, and children. The products include clothing,
shoes, accessories, sports, and beauty. ZALORA ensures that the fashion catered to different
countries and adapted based on the consumer's preferences with a combination of 500
international brands and locals that are offered. Recently, Zalora introduces ZMart to serve
the COVID-19 pandemic essentials such as masks and sanitisers along with household
essentials, health supplements and vitamins, baby supplies and selection of food from snacks,
pasta, baking supplies and alcohol (Tan, 2020). This allows customers to be able to purchase
their daily essentials alongside their fashion purchases.
Figure 1: ZALORA's Mobile Application
6
1.2 ZALORA's Online Shopping System and Rationale
ZALORA is an e-commerce fashion retailer that operates only on the website and mobile
applications; hence their online shopping system is vital to the organisation for customers to
be able to purchase their goods. According to Li et al. (2020), the online shopping system is a
type of electronic commerce that allows customers to directly purchase any product or
services from a seller using the internet. The system provides value to ZALORA as customers
can search for the product of interest, check product's availability and compare different
brands and prices simultaneously. From this, customers can save due to the discounted prices
and do not have to visit multiple offline stores for them to select the best option. Moreover, the
system provides a variety of payment and shipping method to suit the convenience of the
customers. The items that are purchased through ZALORA's online shopping system would
be delivered straight to the customer's home based on the estimated delivery date given
through the chosen courier. To produce a shopping-centric experience and meet the
expectations of the customers, online shopping system at ZALORA holds an essential role for
the e-commerce as well as providing the best way to interact and engage with online
customers.
According to Kemp & Moey (2019), online shopping system is essential to widen their reach
in the e-commerce market as Malaysia's e-commerce spending grew 24% from the year 2019
and 80% of internet users from the age of 16 to 64 years old have made an online purchase.
This has intrigued me in doing business analysis on Zalora's online shopping system as I am
one of the 80% internet users that loves shopping online and are one of Zalora's loyal
customers. Since I was young, walking around the shopping centre and buying clothes has
been a hassle for me since I would go through different clothing stores before deciding what I
would want to buy. Hence, I prefer purchasing my clothing and accessories from online stores
as it allows me to compare different brands at once and ensures that the prices are lower than
retail shops.
7
2.0 Systems Overview
Figure 2: Online Shopping System Diagram
Scope
The online shopping system that implemented on the ZALORA website and mobile application
facilitates the user to be able to perform purchase transactions of products without needing to
travel to the shops. The online shopping system offers product images, description, and price.
The system provides benefits such as multiple payment methods, shipping options,
discounts/coupons availability as well as the ability to compare different brands at once.
Moreover, the online shopping cart is included that allows customers to be able to browse
various products and selecting the items that they would like to purchase and even remove
before placing the final order.
On the other hand, the online shopping system excludes other functional systems that exist in
ZALORA organisation. For example, the system would exclude inventory system, customer
management system, logistic system, the payment system that are used explicitly by specific
functional departments and third parties.
8
Major Functions
ZALORA's online shopping system allows to create and enhance the experience by easing
the transaction between customers and organisation by offering different functions to support:
1. Registering Customer and Login Details
To make a purchase and have exclusive access to discounted deals, users are required to
register with the system. The system provides a function that allows users to register by
providing their customer details and information needed for shipping and billing. Once the user
has noted, the user would be able to login into their account, and all the information submitted
during the registration will be stored in a database which is available for authorised ZALORA's
employees.
2. Adding Products into Shopping Cart
The shopping cart will enable users that are shopping with ZALORA to select the products
that they would like to purchase and proceed to checkout for payment. The shopping cart
function would assist by summarising the user requests based on what they have selected
from the product catalogue. This would allow the user to check the shopping cart and can
cancel/modify the products that are in it.
3. Multiple Payment Methods
The online shopping system consists of a payment system that would account for the
interactions between the parties involved in the financial transaction. The system allows the
customers to pay for their products through other payments method such as using credit/debit
card, e-wallet application, and online transfer. This function would allow the system to check
with the bank and e-wallet merchants to authorise the payments. If the bank/e-wallet merchant
rejects the request, the transaction cannot be deleted, and the order will be cancelled. For
those who do not have online banking or e-wallet application, users are able to make payment
through convenience store such as 7-Eleven.
4. Generate Order Confirmation and Sales Report
Order management function would allow for the system to summarise all details on shipment
and order to make the proper delivery necessary. The function enables the system to generate
order confirmation for the users, which consist of details of their ordered products and shipping
details from their registration database. Moreover, the order confirmation details would assist
warehouse staff to pack the necessary items and pass to the logistics team.
9
System Features
1. Menu Navigation with Search Bar and Product Categories
The system has a user-friendly navigational bar whereby the layout is transparent, and product
categories are clearly divided. Each of the product categories is divided by subsections which
will allow the user to easily search for products based on the brand, product type or price
range. Furthermore, the on-site search would enable users to find what they are looking for
within a short amount of time.
2. High Definition Photos with Image with Image Zoom
Given that the nature of Zalora's business is online, product images play a vital role when
users are purchasing. Since users are unable to hold and touch the product, the system
requires this feature in which for each product, at least three high-quality images are showing
the work from different angles. Furthermore, the feature consists of a zoom which gives the
user option to see a given part of the product.
3. Detailed Product Description
Each of the products listed on the online shopping system is provided with clear and extensive
bullet points description. The feature allows the product description to be concise, quick, and
easy to read.
4. Order Tracking
The feature allows users to see the process of their product delivery and predict the arrival
time. It will enable users to track their order manually without needing to email or call customer
service enquiring on their order delivery.
Constraints
Internal Constraints
The internal constraints that can apply to ZALORA's online shopping system are in terms of
its system's architecture. The constraints could be that when the server may experience
downtime. According to Warrington (2019), server downtime is one of the crucial issues faced
by the organisation as 90% of companies suffers unplanned downtime with an average cost
of $1.55 million each year. Given that ZALORA businesses are taking place online; hence this
constraint heavily affects the organisation as they are entirely dependant on IT infrastructures
and system architectures which keep the internet services running smoothly. When the server
10
is down, ZALORA customers are unable to access the mobile application and website,
therefore not capable of purchasing the products. This would result in ZALORA losing sales
and revenue.
External Constraints
The external constraints that could apply to ZALORA's online shopping system is based on
the government's rule and regulations. When operating in Malaysia, ZALORA would need to
be abide by the Data Protection Act 2010. The online shopping system requires customers to
register and store their personal information that includes name, address, email address and
possibly their financial report. Hence, the constraints occur in which ZALORA would need to
handle the data in compliance with the law through holding the information that is relevant to
the business and ensuring that their personal information are always protected against the
third party.
Besides that, the constraints that may apply is that ZALORA experience a hacking situation
that could negatively affect the business's reputation and halts the online shopping system
operations. According to Meikeng (2020), cybersecurity which involves unethical hacking have
spiked by 82.5% compared to the year 2019. Unethical hacking on ZALORA's online shopping
system would negatively affect the organisation as it would affect the user experience when
shopping through the website or mobile application. Further, it causes the customer not feeling
safe as they are aware the hacker may breach their private confidential information.
System Feedback
The system’s feedback for Zalora’s online shopping system is balancing when the customer
user receives notification that the payment status for their order failed which in turn the
customer will require to input a new payment method to purchase the order. The change of
the system’s output causes through the environment a change in input that will tend to return
the output to its original value which is the payment has been successful.
Besides that, the system’s feedback for ZALORA online shopping system is positive when
there is an increase in revenue. It can be assumed that previously that customers shop
traditionally by going to the shops rather than purchasing online. Hence, the online shopping
system provides more customers in shopping with ZALORA, which increases the
organisation’s revenue. This allows for ZALORA to enhance their online shopping system by
providing additional features, functions, and security to provide a great user experience.
11
3.0 Requirement Analysis
3.1 Requirements Gathering
3.1.1 Survey
The first requirement gathering method that are used to develop a set of user requirements
for ZALORA's online shopping system are by using a survey that are done through
questionnaire. The method was chosen because questionnaire allows to gather responses
from many respondents within a short time. This is supported by Elijah et al. (2017) as survey
are the popular method for researchers and system analyst in gathering responses from large
respondents as it is effective and economically. The survey is given to customers to find out
their requirements and expectations for the online shopping system. The survey distribution
method that are being used is the snowball effect whereby the questionnaires are passed to
family and friends who have purchased through online shopping system previously. From
there, the questionnaire will be passed from family and friends to people that they knew whom
have experienced the online shopping system. The survey is accompanied with guidelines
and instructions for the respondents and it was done individually. The method provided the
ability to gather information from respondents on their own positive/negative experience using
the system which would result in unbiased answers.
3.1.2 Interview
The second requirement gathering method that are used is interview. The method chosen
would enable me to obtain feedback on the system's requirements from ZALORA's
employees. To gather the requirements, I had set an appointment with three employees from
ZALORA organisation. The interview with the employees is done one-on-one ensuring that I
would understand the user's environment using the system as well as their individual
requirement on the system. The technique was chosen to gather requirements from the
business side as it would provide an opportunity for employees to respond freely and openly
to the questions. It would also give me the opportunity to ask any follow-up questions on their
standard operating procedure for the system and get an instant back from the interviewees.
This has been supported by Rueda, Panach & Distante (2020) as interview is the fastest
method in order to gather system requirements.
12
3.2 Requirements Identification
Based on the requirements gathering that has been conducted, below are the requirements
according to the user type.
3.2.1 Customer
Table 1: Customer requirements identification
Req
#
Requirements
Mandatory 1 The system will provide list of products with prices.
2 The system will be available 24/7 and generate order
confirmation after purchasing the product.
3 The system will provide a secured payment sub-system and
database.
Optional 4 The system will have provided a clear instruction and guidance
on user registration and purchasing a product.
5 The system will visually track the product's order
Frill 6 The system will feature the user's recently viewed products.
7 The system will produce sound once order has been confirmed
3.2.2 Management
Table 2: Management requirements identification
Req
#
Requirements
Mandatory 1 The system should be able to generate platform's data to generate
report.
2 The system should retrieve customer's order and delivery detail in
real-time.
13
Optional 3 The system will securely store and view sales data.
4 The system will allow to feature selected products for campaign.
Frill 5 The system will allow different colour background.
6 The system will create a sound when order is received.
3.3 Matching system functions with requirements
Table 3: Matching system functions with user requirements
Functions Req# Requirements
Functional Requirements
1. Customer
registration and
login
4 • The system should be easy to use for various
customer age group with different level of computer
skills.
2. Provide payment
methods
3 • The system should detect unauthorised access
• The transaction using the system should be secure
and using encryption mechanism
3. Generate sales
report for
management
1 & 2 • The system should include the list of all customer's
purchases with the sales value and its uplift
compared to the previous month
• The system can display all user transactions for
management
4. Generate order
confirmation for
customer
2 • The system should include order confirmation that
combines their purchases along with their customer
and shipping details.
Non-Functional Requirements
24/7 availability 2 • The system should have a backup server that allows
customers to purchase online anytime at anywhere
Clean white
background and black
font
3 • The system should have a clean white background
and black font throughout the product pages so that
it provides customer with good customer journey and
can easily read.
Secured database 1 & 3 • The system should have an encrypted database with
high level of security to avoid potential unauthorised
access from unknown third party.
14
4.0 Traditional Models
This section presents the traditional models that are constructed using data flow diagram, logic
modelling (structured English, Decision table and decision tree) for ZALORA’s online shopping
system.
4.1 Process Models (DFD Diagram)
4.1.1 Online Shopping System Context Diagram
Figure 3: ZALORA's online shopping system context diagram
4.1.2 Online Shopping System Level 0 DFD
Figure 4: ZALORA online shopping system Level 0
15
4.1.3 Level 1 DFD & Logic Model for Process 1.0
The level 1 DFD shows the breakdown of the activities of 1.0 process. The activities would
include the system receiving the product selection from the customer, recording the order into
relevant data stores, and verifying the product selection.
Figure 5: ZALORA's online shopping system level 1 (process 1.0)
Logic Model for Process 1.1 – Structured English
RECEIVE product selection from customer
DO WHILE there is product selection from customer to process
BEGIN IF
IF product selection = > 1
THEN record product selection
ELSE compute error
END-IF
END-DO WHILE
UNTIL there is no more problem selection
16
Logic Model for Process 1.2 – Decision Table
Table 4: Process 1.2 decision table
Conditions
Rules
1 2 3 4 5 6
Product have Product ID Y Y Y N N N
Product selection <1 1 >1 <1 1 >1
Course of Action
Record in Product DB X X
Record in Add to Cart DB X X
Compute Error X X X X
Table 5: Process 1.2 reduced decision table
Conditions
Rules
1 2 3 4
Product has Product ID Y Y Y N
Product selection <1 1 >1 -
Course of Action
Record in Product DB X X
Record in Add to Cart DB X X
Compute Error X X
Logic Model for Process 1.3 – Decision Tree
Figure 6: Process 1.3 decision tree
17
4.1.4 Level 1 DFD & Logic Model for Process 2.0
The level 1 DFD below shows the breakdown of the activities of 2.0 process. The activities
would include the system receiving the confirmed products, calculate total price, collect
payment as well as record and send relevant data.
Figure 7: ZALORA's online shopping system level 1 (process 2.0)
Logic Model for Process 2.1 - Decision Table
Table 6: Process 2.1 decision table
Conditions Rules
1 2 3 4 5 6 7 8 9 10 11 12 13
Type of Customer N N N N N N E E E E E E E
Number of Items
Order
<1 <1 1 1 >1 >1 <1 <1 1 1 >1 >1 >1
Subscribed Priority
Membership
Y N Y N Y N Y N Y N Y N N
Course of Actions
Accept Order X X X X X X X X X
Reject Order X X X X X
Calculate Price X X X X X X X X X
10% Discount
Eligibility
X X X X
20% Discount
Eligibility
X X X X
Priority Shipping X X X X
18
Table 7: Process 2.2 reduced decision table
Conditions Rules
1 2 3 4 5 6 7 8 9
Type of Customer - N N N N E E E E
Number of Items Order <1 1 1 >1 >1 1 1 >1 >1
Subscribed Priority
Membership
- Y N N Y Y N Y N
Course of Actions
Accept Order
X X X X X X X X
Reject Order X
X
Calculate Price X X X X X X X X
10% Discount Eligibility
X X
X
20% Discount Eligibility
X
X X
X
Priority Shipping
X
X X
X
Logic Model for Process 2.2 – Decision Tree
Figure 8: Process 2.3 decision tree
Logic Model for Process 2.3 – Structured English
RECEIVE payment status
RECEIVE customer order
IF payment status = "success"
THEN generate order confirmation and send to customer,
send delivery order to warehouse,
update order status to Customer DB & order data to Order DB
ELSE compute error
END-IF
SEND order status to Customer
19
4.1.4 Level 1 DFD & Logic Model for Process 3.0
The level 1 DFD below shows the breakdown of the activities of 3.0 process. The activities
would include the system receiving the relevant data from the datastore, transform the data
into report as well as store and send report.
Figure 9: ZALORA's online shopping system level 1 (process 3.0)
Logic for Process 3.1 – Structured English
RECEIVE monthly order details from order DB
RECEIVE inventory level from Product DB
DO WHILE there are monthly order details to process for the month
BEGIN IF
IF product selection = > 1
THEN create report data
ELSE compute error
END-IF
END-DO WHILE
UNTIL there are no more order details for the month
Logic for Process 3.2 – Structured English
RECEIVE report data
RECEIVE monthly sales analysis from Sales Supervisor
BEGIN IF
If report >0
THEN generate formatted report
ELSE compute error
END-IF
20
Logic for Process 3.3 – Decision Table
Table 8: Process 3.3 decision table
Conditions
Rules
1 2 3 4
Report includes monthly sales analysis Y Y N N
Report data is accurate and validated Y N Y N
Course of Action
Record in Management DB X
Send Report to Sales Manager X X
Compute Error X X
4.2 Entity-Relationship Diagram (ERD)
Figure 10: ERD of ZALORA's Online Shopping System
21
4.2.1 Data Dictionary
Table 9: Data dictionary
Entry Name Entry
Description
Column Name Column
Description
Data
Type
Field
Size
Primary
Key
Customer Potential or
existing
individuals
that would
like to
purchase
using the
Zalora's
Online
shopping
system.
Disc Rate Discount rate
that are eligible
based on their
purchase
Int 2 FALSE
Address The address of
the customer
for shipping
String 100 FALSE
City The city that
customers live
in.
String 20 FALSE
Postcode The postage of
the customer's
address.
Int 10 FALSE
Number The number of
the customers
house
Int 4 FALSE
Street The street
where the
customer lives.
String 50 FALSE
User The
individuals
that are using
the online
shopping
system
User ID For the unique
identification of
users records.
Int 10 TRUE
Username The username
that users need
to key in when
login to the
system.
String 20 FALSE
Name The name of the
user
String 20 FALSE
EmailAddress The email of the
user
String 20 FALSE
PhoneNo The phone
number of the
user
Int 10 FALSE
DOB The user’s date
of birth
Date 10 FALSE
Employee Individual
who
performs
certain
functions
associated
with a
Level_Access Different
employee will
be given
different level
of access in the
company.
String 10 FALSE
22
particular
position.
Manager Individual
who
responsible
for
controlling or
administering
an
organisation
or group of
staff.
Grade Different grade
to differentiate
between
positions, skill
sets and
responsibilities.
String 20 FALSE
Supervisor The
individual
that is
responsible
for the
productivity
and actions
of the
employee
SupervisorType Different
supervisor that
are from
different
department.
String 20 FALSE
Payment The amount
paid or
payable for
the purchase
order
PaymentID Unique code for
each transaction
made.
Int 10 FALSE
Date Exact date that
the payment
was made.
Date 10 FALSE
Payment
Merchant
Where all the
payment
transaction
are verified.
MerchantID Unique code for
to identify
payment
merchant
Int 30 TRUE
MerchantName Name of the
payment
merchant that is
available on
Zalora
String 20 FALSE
Order
Confirmation
The details of
order
confirmation
are
generated
Order_Status The status of
the order
String 10 FALSE
Delivery Partner The 3rd party
that will be
used to help
deliver the
product.
PartnerID The unique
number that
identify the
partner.
Int 30 TRUE
PartnerName The name of the
delivery partner
that is used for
delivery.
String 20 FALSE
23
Order The item that
the user
wanted to
purchase.
OrderID Number system
that help keep
track of the
order.
Int 30 TRUE
ProductID Specific code for
the item to help
identify it
easier.
Int 30 FALSE
Total_Price The total price
of the products
in the order
Int 10 FALSE
Qty The total
amount of item
that the user
have purchase.
Int 5 FALSE
OrderDate The date that
the user made
the order.
Date 10 FALSE
Product The product
that is being
sold on the
website.
Name The name of the
specific product.
String 30 FALSE
Image An image of
what the
product will
look like.
Byte 100 FALSE
ProductID Specific code for
the item to help
identify it
easier.
Int 30 TRUE
PurchasePrice The original
price that the
buyer purchase
the product.
Int 10 FALSE
Stock_Level The amount of
item that is left
in the inventory.
String 30 FALSE
SalePrice The price that is
being sold to
the user.
Int 10 FALSE
Shopping Cart Section
where it
shows all the
product that
the customer
have chosen.
Total_Price Amount shown
of the total
product in the
shopping cart
Int 10 FALSE
ShoppingCartID Specific code for
shopping cart.
Int 20 TRUE
Date The date users
purchase the
product.
Date 10 FALSE
Product_Name The name of
product that are
available in
Zalora
Int 10 FALSE
24
Quantity Amount of the
individual
product that is
in the cart.
Int 5 FALSE
Price Amount of the
specific product.
Int 5 FALSE
Warehouse Where all the
inventories
are kept.
WarehouseID Specific number
to identify the
warehouse.
Int 10 TRUE
PhoneNo The number for
the warehouse
Int 15 FALSE
WarehouseNam
e
The name for
the warehouse
String 20 FALSE
Location Where the
warehouse is
located
String 20 FALSE
Categories Different
product
categories
that are
available on
Zalora
Category_Name The name of the
category
String 10 FALSE
25
5.0 Modern Analysis
The section presents the modern analysis that are constructed using UML diagram (Use-Case
Diagram, Class Diagram, Sequence, State Machine and Activity Diagram). For the UML
diagram, I have decided to narrow the scope that consists of browsing product, submitting
order as well as processing and generate report. I have reduced the scope of the online
shopping system by removing payment sub-system and logistic system to focus on the specific
functions mentioned.
5.1 Use-Case Diagram
Figure 11: Use-Case diagram
26
5.1.1 Use-Case Description
Table 10: Browse product use-case description
Use case name: Browse Products
Actor(s): Customer
Description: Viewing the products that are available from Zalora and enable for existing
customers to add to shopping cart and new customers to register for an account before
adding to shopping cart.
Steps: Information required [produced]:
Customer search for items Product ID [Product name]
Customer browse for items Product name, price, and stock availability
New or existing customer inserts an item
into the shopping cart
[Shopping Cart ID, Date, Product ID,
Product Name, Quantity, Price]
If the customer is already an existing
customer, request login details
Username and Password [User ID]
If the customer is a new customer, then
register an account and assign a unique
username
[Username, Password, User ID, Name,
Address, Telephone Number, Email
Address]
Table 11: Submit order use-case description
Use case name: Submit Order
Actor(s): Customer
Description: submit order and make payment when the customer have decided on what
to purchase from the online shopping system.
Steps: Information required [produced]:
Customer view and update shopping cart Shopping Cart ID, Date, Product ID,
Product Name, Quantity, Price
Customer checks out the shopping cart Shopping Cart ID, Date, Product Name,
Quantity, Price [Order]
System retrieves the order Order
System calculates the total price of the
products
Product Name, Product Quantity, Price
27
System retrieves customer details Name, Address, Telephone Number, Email
Customer updates shipping and billing
information
[Address]
System forwards customer to payment
sub-system.
Table 12: Process and generate report use-case description
Use case name: Process and Generate report
Actor(s): Sales Supervisor, Sales Manager
Description: retrieving financial data and analysis and produce the sales report
Steps: Information required [produced]:
System retrieves monthly order data Monthly sales
System retrieves current inventory level Product inventory level
System send monthly order and current
inventory level to sales supervisor
Sales supervisor provides monthly sales
analysis
[monthly sales analysis]
System combines the retrieved data and
monthly sales analysis
Monthly sales, product inventory level,
monthly sales analysis
System produces the management report Monthly order data, current inventory level
data, monthly sales analysis [management
report]
System sends the management report to
Sales Manager
Management report
28
5.2 Class Diagram
Figure 12: Online shopping system class diagram
29
5.3 Sequence Diagram - Customer
Figure 13: Customer sequence diagram
5.3.1 Updated Class Diagram - Customer
Figure 14: Customer updated class diagram
30
5.4 Sequence Diagram – Sales Supervisor
Figure 15: Sales supervisor sequence diagram
5.4.1 Updated Class Diagram – Sales Supervisor
Figure 16: Sales supervisor updated class diagram
31
5.4 Sequence Diagram – Sales Manager
Figure 17: Sales manager sequence diagram
5.4.1 Updated Class Diagram – Sales Manager
Figure 18: Sales manager updated class diagram
32
5.5 State Diagram
The possible state that the order confirmation can be is in checking the status of the order and see if
the order has been paid. Hence, an additional attribute and attribute actions are added into the Order
Confirmation class definition:
Figure 19: Order confirmation status state diagram
33
Updated Class Diagram
Figure 20: Updated class diagram for state diagram
34
5.5 Activity Diagram – Customer
35
5.5 Activity Diagram – Sales Supervisor
36
6.0 Reflection
Sir Arthur Conan Doyle once quoted "data, data, data! I cannot make bricks without clay". The
quote remembers me back to my time working at an e-commerce company as a senior analyst
in campaign in which my job heavily relies on the use of data and information system to
analyse the performance of my campaigns as well as making decisions to improve my future
campaigns. Based on my past working experience, this has intrigued me in analysing an online
shopping system in order to understand its complex structure, components and sub-systems
that lies within the online shopping system. As an online shopping enthusiast, I was also
interested how the system provides the convenience for online shoppers to purchase products
regardless of the time using smartphone or computer. Furthermore, it interests me in
understanding how the data are flowed through the system and used by different functions in
the organisation to complete an order and deliver to the customers.
The online shopping system analysis process that was done throughout the twelve weeks
have made me realise on how data is important to an organisation in order to provide great
customer experience. According to Packer (2018), functional excellence does not guarantee
overall success and working with different functions altogether provides the greatest possibility
for superior performance. Hence, I learnt that using bridging the gap between different
functions using the system gives the benefit to an organisation which can be done by visually
representing the interrelationship between the components of the online shopping system
using diagram modelling. The use of data flow diagram enables me to understand how the
data inputted from the customer are flowed throughout the system to different parts of the
organisation and processed to generate an output to the end user such as order confirmation
and sales report. Moreover, the different diagramming concepts learnt allows me to further
comprehend the relationships between the entities and their attributes in the system. I have
developed an increasing respect for and fascination on the number of ways that individuals
and different functions in the organisation can benefit from the online shopping system. For
example, the online shopping system processes the customer's order and forwards the order
to warehouse so that the workers in the department are able to pick and pack the goods as
well as giving the parcel to delivery partner for delivery. I have come to admire the power that
the diagramming concepts and tools that I have learnt throughout the twelve weeks can bring
to organisational matters so it could be improved and increase in efficiency.
During the analysis process for the online shopping system, I have trouble in understanding
certain system concepts such as data flow diagram and logic modelling. Given that I am
previously a business major student, learning about systems and diagramming tools are new
and foreign to me hence I did not understand on the steps that need to be taken to start the
37
diagram. In order to overcome the difficulty, I found that listening the lecture and tutorials
multiple times helps me in finding the connections between the diagram components and
grasping the concept. Furthermore, I have realised that YouTube consists of various tutorial
videos that you can watch and understand the concept further. The step-by-step videos on
creating diagram have helped me tremendously in creating my diagrams for the assignment.
Nevertheless, the assignment has provided me a great insight on becoming a business
analyst. Nowadays, business analysts require to help organisations implement technology
solutions in cost-effective way by determining the requirements and communicating the
requirements clearly to the stakeholders. The role and responsibilities heavily rely on the
system development life cycle stages whereby the assignment allows us to practice the
system analysis and requirement phase in real-life. For example, the assignment requires me
to conduct requirement gathering for Zalora's online shopping system hence I would need to
conduct survey and interview with Zalora's management employees as well as Zalora's
customers. The requirement gathering has helped me in identifying the crucial functions that
is needed from the stakeholder which then proceeded with drawing system diagram. Drawing
system diagram (DFD, ERD and UML) also provides the assignment value as it allows me to
see the different components of the system. The diagram visually illustrates the relationships
between entities and attributes as well as identifying the data needed for input and process to
generate the output. Hence, the tools learnt would be beneficial for me to implement in my
working life in the future.
Overall, the assignment has improved my knowledge on system analysis and the feedback
from the lecturer from my mid-term report progress have enable me to develop my project
further. However, the current assignment have only enable me to analyse the current functions
of Zalora's online shopping system; and the assignment can be further improved by including
the requirements that are needed as stated by the end-users based on the requirement
gathering phase.
38
7.0 References
Elijah, J., Mishra, A., Mathew Chukwu Udo, E., Abdulganiyu, A., & Musa Aibinu, A. (2017).
Survey on Requirement Elicitation Techniques: It's Effect on Software Engineering.
International Journal of Innovative Research in Computer and Communication
Engineering, 5(5), 9201–9215. https://doi.org/10.15680/IJIRCCE.2017
Kemp, S., & Moey, S. (2019). Ecommerce in Malaysia in 2019. Data Reportal.
https://datareportal.com/reports/digital-2019-ecommerce-in-malaysia
Li, X., Zhao, X., Xu, W. (Ato), & Pu, W. (2020). Measuring ease of use of mobile applications
in e-commerce retailing from the perspective of consumer online shopping behaviour
patterns. Journal of Retailing and Consumer Services, 55, 102093.
https://doi.org/10.1016/j.jretconser.2020.102093
Meikeng, Y. (2020). Cybersecurity cases rise by 82.5%. The Star.
https://www.thestar.com.my/news/focus/2020/04/12/cybersecurity-cases-rise-by-825
Packer, D. W. (2018). Taking a Systems View: A Reflection.
https://thesystemsthinker.com/taking-a-systems-view-a-reflection/
Rueda, S., Panach, J. I., & Distante, D. (2020). Requirements elicitation methods based on
interviews in comparison: A family of experiments. Information and Software
Technology, 126, 106361. https://doi.org/10.1016/j.infsof.2020.106361
Tan, C. (2020). Online Fashion Retailer Zalora Is Now Selling Essential Supplies Like Face
Masks, Snacks, Health Supplements & Wine. Today Online.
https://www.todayonline.com/8days/liveandlearn/style/online-fashion-retailer-zalora-
now-selling-essential-supplies-face-masks
Warrington, R. (2019). What Happens When Your Servers Go Down. VXchnge.
https://www.vxchnge.com/blog/when-servers-go-down
39
8.0 Appendix
Appendix A: Management Requirement Gathering Interview Questions (SAMPLE)
Interview Outline
Interviewee: Interviewer: Anissa MD Mashor
Location: ZALORA HQ, Kuala Lumpur Date: 23 Sept 2020
Objectives: To investigate the system
requirements needed
Reminder:
General Observation: The interviewee will involve directly with the system
Interviewer Interviewee
Question 1:
What is your position in ZALORA?
Question 3:
Is your usage of the current online shopping
system low, medium, or high?
Question 2:
Do you think the online shopping system provided
you with necessary functions for your task and
responsibilities?
Question 3:
What is the information that you needed from the
system?
40
Question 4:
How does the online shopping system add value
to the team and the entire organisation?
Question 5:
What effect, if any do you think a user-friendly
online shopping system would have on employees
in completing their work?
Question 6:
If any, can you describe the problems that you
faced when using the system?
Question 7:
What can the system do to better support your
responsibilities?
41
Appendix B: Customer Requirement Gathering Interview Questions (SAMPLE)
Introduction
Providing the best online shopping system is the main priority for ZALORA as it would provide
customers with great experience when shopping online. This survey will help us on gathering
functional requirements of customer as well as their experience when using online shopping system.
All the data collected from this survey will help me in gathering the functional requirements for
ZALORA online shopping system. All responses from this survey will be kept anonymous and
confidential.
Thank you for completing this survey.
The objectives of this survey are:
• To find out the functional requirement for ZALORA's online shopping system.
• To know customer's experience when booking using the online shopping system.
Section A: Demographic
Please tick one for each question.
1. Age:
Under 18 years old □ 25 – 34 years old
18 - 24 years old □ 35 – 44 years old
45 – 54 years old □ Above 55 years old
2. Your computer's skill
Beginner
Intermediate
Advanced
3. Averagely, how often do you shop online in the last 6 months?
Everyday
Weekly
Once every two weeks
Once a month
Every 2 or 3 months
Section B: Psychographic
6. Overall, are you satisfied with your experience using online shopping system?
Yes (why):______________________________________________________________
No (why):_______________________________________________________________
42
4. How important is these functions in the online shopping system?
Please choose the best answer for the following by ✓ at the boxes below.
Really not
important
Not important Neutral Important Really
Important
a) User
Account
Registrati
on
b) Generatin
g Order
Confirmat
ion
c) Shopping
Cart
d) Secured
Payment
System.
e) Live Chat
Support
f) Order
Tracking
5. For each of the following statement, mark one box that best describe your experience with
the online shopping system.
(Range from 1 = Strongly Disagree to 5 = Strongly Agree)
1 2 3 4 5
a) I found the system was easy to use.
b) The system would generate order
confirmation immediately after I have
purchased the product.
c) I found the various functions in this
system were well-integrated
d) I found the system very cumbersome to
use
e) I felt very confident using this system
f) I needed to learn a lot of things before
using this system
43
7. Are there any functions that you would like to add in the online shopping system?
Thank you for participating.
