Software Requirements Specifications

Web Site
Online Food Delivery System

Submitted in partial fulfillment of the requirements of CS 200

Work done by:

Zaineb Trimeche Manar El Arbi
Sophomore
Group: 11

Section -1: Introduction:

• Purpose:

The purpose of this document is to present a detailed description of the Food

delivery system. The intended audience of this document includes the
customer who wants to order food, the restaurant staff, as well as the meal
deliverer. Other intended audience contains the development team such as
design team, requirements team, requirements analyst…
• Scope:
The system is a website where all people have access to restaurants’ menus. This
website helps full-time workers, sick, elder and handicapped people to be served
at home. The website proposes many restaurants and thus, diverse food and
beverages. It will allow the following functionalities: to create an account, to
search for restaurants, to check menus, to select a specific menu or several at a
time and paying online or when the order is delivered. The restaurant staff will be
alerted when an order is ready; the meal deliverer gets the order from the
restaurant and drives down to the address provided by the customer.
• Definitions and acronyms:
FDS-Food delivery system
• References:
Restaurant staff: workers in the restaurant
Customer: anyone who orders with the FDS
Meal deliverer: the guy who delivers food
• Overview:
Section 2 of the SRS describes in detail the website. Section 3 contains all of the
functional requirements. Whereas, non-functional requirements are listed in the
fourth section. The class diagram is represented in section 5 and the use case
diagram is represented in section 6. Appendices are the last part of the SRS.
Section -2: General Description:

• Product Perspective:
The food delivery system interfaces with 2 other systems; the menu
management system, the web ordering system. The system is a secure space
for all financial transactions.
• Product Functions:
The system groups restaurants that offer delivery services, allows the
customers to consult the website create a new account or open an existing
one, then presenting them with different restaurants to choose from. Once
they pick the one they desire, they click on it to access the menu of that
restaurant; they can view the offered food alongside with its price. After
selecting an item it gets placed into their order. They are provided with the
ability of checking the details of his order before confirming. Finally, they
proceed to payment by entering the details of their credit card and the
address to which the order will be delivered. On the other hand, the
restaurant consults the order details after it has been entered into the
database.
• User Characteristics:
 The main 4 groups of users of the food delivery system are customers,
restaurant staff, restaurant managers, and the meal deliverer.
The Can upload their information, their contacts and the food they
customers wish to receive. They can look for their needs on the web site,
scrolling through menus uploaded by restaurant managers. They
should be able to pay online for their delivery.

The They will receive orders from the Web Ordering System, prepare
restaurant meals, package them for delivery, print delivery instructions, and
staff request delivery. Most of the restaurant Staff will need to be trained
in the use of the computer, the Web browser, and the web Ordering
System.

The The restaurant manager is an employee who is responsible for

restaurant establishing and maintaining menus of the food items available from
manager the restaurant. Some menu items may not be available for delivery.
The restaurant manager will need to edit the menus periodically to
reflect planned food items that are not available or price changes.

Meal He will pick up the food and delivery instructions for each meal and
Deliverer deliver it to the customer. The Meal Deliverers’ primary interactions
with the system will be to reprint the delivery instructions on
occasion and to confirm if the meal has been delivered.

• General Constraints:
This system provides web access for all users functions. The use of the system is
simple, clear and intuitive so that no special trainings are required by any of the
users. Only basic skills are needed .All online financial transactions and the
confidential data of the users will be done in a secure environment.
• Assumptions:
A bank operating system will be available to interface with the food delivery
system.
The restaurants are open for delivering breakfast, lunch, and dinner every company
business day in which employees are expected to be on site.
The operation of the system depends on changes being made in the restaurants
food Inventory System to update the availability of food items as the orders are
accepted.
Section -3: Detailed Document for Users:

• Functional Requirements:
3.1: The system shall provide registration for users to become members.
3.1.1: The system shall allow the users to login with their emails and choose a
password.
3.1.2: The system shall record members’ personal information for future use
after their approval.
3.2: The system shall allow the users to modify their personal information at
any time.

3.3: The system shall Display the menu

3.3.1: The system shall allow customers to Navigate the restaurant’s menu.
3.3.2: The system shall allow customers to select an item from the menu.
3.4: The system shall provide delivery and payment details.
3.5: The system shall Update price for a given food item.

3.6: The system shall retrieve new orders from the database.

3.7: The system shall Mark an order as having been processed.

3.8: The system shall be able to make changes in the menu like adding or
removing food items
3.9: The system shall allow users to make changes in their order
3.10: The system shall allow users to review the order before submitting it
3.11: The system shall allow users to pay using their debit/credit card.
3.11.1: The system shall provide login security for payments and for protection
of personal information.
3.12: The system shall provide payment and delivery details to restaurant
managers
 3.13: The system shall allow users to pay log out.
• Non-Functional Requirements:
3.1: The system shall provide a secure environment for financial transactions
and for the storage of confidential member information.
3.2: The system shall be available at all times
3.3: The system shall be easily used by the customer
• System Architecture:

• System Models:

• Relational Schema:
Customer(cust_id, cust_FirstName, cust_LastName, cust_email, cust_password, #OrderId)

MenuManagementSystem(MenuId, Menu_Name, Price)

RestaurantManager(ManagerId, ManagerPassword, #MenuId, #OrderId)

RestaurantStaff(StaffId, #ManagerId)

MealDelivrer(DelivrerId, #OrderId)

WebOrderingSystem(OrderId, MenuCards, RestaurantsLists, CustomerInfo, PaymentOptions, Alerts)

Payment(PaymentId, PaymentDate, PaymentType, Amount)

Debit(#PaymentId, DebCardNum, DebCardExpiration, DebCardPin)

Credit(#PaymentId, CrCardNum, CrCardExpiration, CrCardPin)

CustomerPayment(#Cust_Id, #PaymentId)

CustMenuAccess(#Cust_Id, #MenuId)

StaffRequest(#DelivrerId, #StaffId)