Project Title: Noon Online Store

2. Introduction: Noon is a Saudi Arabian online store that provides a platform for
customers to purchase various products, including electronics, fashion, home and
kitchen appliances, and much more. Noon's primary objective is to provide its customers
with a seamless shopping experience by offering a variety of products and convenient
delivery services.
3. Stakeholders:
 Administration.
 Product suppliers.
 Delivery providers.
 Customers.
4. Requirements: 4.1 Functional Requirements: 4.1.1 Customer User Functional
Requirements:
 The Customer shall be able to Sign Up.
 The Customer shall be able to Login.
 The Customer shall be able to Update account information.
 The Customer shall be able to Search for products.
 The Customer shall be able to View product details.
 The Customer shall be able to Add products to the cart.
 The Customer shall be able to Select payment methods.
 The Customer can be able to Cancel orders.
 The Customer shall be able to Confirm the order.
 The Customer shall be able to Communicate with the delivery provider.
 The Customer can be able to Track the order.
 The Customer can be able to Logout.

4.1.2 Delivery Provider User Functional Requirements:

 The Delivery Provider shall be able to Access the system.

 The Delivery Provider shall be able to Accept the order.
 The Delivery Provider can be able to Decline the order.
 The Delivery Provider shall be able to View the order data.
 The Delivery Provider shall be able to Close the order.

4.1.3 Product Supplier User Functional Requirements:

 Product suppliers shall be able to register to the system.

 Product suppliers shall be able to agree to the terms and conditions of the system
before they register.
 Product suppliers can be able to add new products.
 Product suppliers can be able to update their existing products.
 Product suppliers can be able to delete their existing products.

4.1.4 Administration User Functional Requirements

The administration can browse complaints through their interface.

The administration can browse user accounts through their interface.

The administration can add restaurants to the system.

The administration can block restaurant items that violate the terms and conditions of the system.

4.1.5 Customer System Functional Requirements

4.1.5.1 The customer shall be able to sign up. During the signup process, the user is prompted to enter
their username, phone number, email, and password. An activation code is sent to the user's phone,
which they enter to complete the signup process.

4.1.5.2 The customer shall be able to log in. During the login process, the user is prompted to enter their
username and password.

4.1.5.3 The customer shall be able to update their account information. During the update process, the
user can change their username, phone number, or password.

4.1.5.4 The customer shall be able to activate their location. During the activate process, the user is
prompted to enable location services through their device's settings. They can then view available
products.

4.1.5.5 The customer shall be able to view restaurants. During the view process, the user can view
restaurants, offers, types of products, and prices.

4.1.5.6 The customer shall be able to search for restaurants. During the search process, the user can
search for a specific restaurant name or type of product.

4.1.5.7 The customer shall be able to select restaurant meals. During the select process, the user can
add multiple products from one restaurant to their cart.

4.1.5.8 The customer shall be able to view their cart. During the view process, the user can view the
items in their cart, their quantities, and their prices.

4.1.5.9 The customer shall be able to select a payment method. During the select process, the user is
prompted to choose a payment method such as Visa, credit card, cash, or Mada.

4.1.5.10 The customer shall be able to cancel an order. During the cancel process, the user is prompted
to contact technical support to cancel the order. Neither the user nor the meal deliverer can cancel the
order.
 4.1.5.11 The customer shall be able to confirm their order. During the confirm process, the user can
view their receipt and select their home location and payment method.

4.1.5.12 The customer shall be able to communicate with the meal deliverer. During the communication
process, the user can see the name and phone number of the meal deliverer.

4.1.5.13 The customer shall be able to track their order. During the track process, the user can track the
meal delivery online.

4.1.6 Delivery System Functional Requirements 4.1.6.1 The Delivery personnel shall be able to access the
system. Upon registering for the first time, the representative is prompted to provide their name,
password, phone number, nationality, and vehicle model. After that, they can log in with their name and
password. 4.1.6.2 The Delivery personnel shall be able to view order data, including the restaurant
name, customer location, and phone number. 4.1.6.3 The Delivery personnel shall be able to mark the
order as delivered and closed to receive another request.

4.1.7 Sellers System Functional Requirements 4.1.7.1 Sellers shall be able to register with the system.
The system will register the seller's information and create a username and password for them.

4.1.8 Administration System Functional Requirements 4.1.8.1 The administration can browse user
accounts on their interface. User accounts can be viewed for data validation.

4.2 Non-functional requirements

 The system shall be available on iOS and Android.

 Customers shall be required to create a strong password containing both letters and numbers.

 The system must support both Arabic and English languages.

 The system shall be able to handle a growing number of customers and orders.

 The sellers shall be able to provide clear product prices and descriptions.

 Sensitive data must be protected from unauthorized access.

 The system shall be easy to use.

 The colors of the system’s user interface shall be comfortable for the eyes.

 The system should be scalable.

 The system shall support varied payment methods.

‫الجدول األول الى تحت‬

it in case of invalid or disapproved information.

5.2.2 Use Case Scenario: 5.2.2.1 Online Shopping process

 Use Case name: Online Shopping

 Primary actor: customer - Other actors: administration, restaurant, delivery agent
 Description: This use case describes how a customer can search for and purchase
products from the Noun online store.
 Pre-conditions: The customer is registered and logged into their account.
 Actor - System Steps:
1. The customer searches for a desired product.
2. The system displays a list of relevant products.
3. The customer selects the desired product.
4. The system displays the product details (price, description, reviews).
5. The customer adds the product to their cart.
6. The customer proceeds to checkout.
7. The system verifies the customer's information and delivery address.
8. The customer selects a payment method.
9. The system processes the payment.
10. The administration receives the order and verifies the payment.
11. The restaurant prepares the order.
12. The delivery agent picks up the order and delivers it to the customer. Alternative and
Exceptional flows: 2.1 No relevant products found. 7.1 Invalid customer information or
delivery address. 9.1 Payment method not supported or invalid. Post-conditions: The
customer receives the ordered product. The administration updates the order status.
The restaurant updates the order status. The delivery agent updates the order status.