<Online Food Ordering>

Software Requirements Specification

<1.0>

<02-May-2017>

Submitted by:

Iqra Ali (2003)

Program:

MCS (2015-2017)

1
 Department of Computer
Science & IT

Glims Institute of Modern Studies

The Islamia University of Bahawalpur

2
Revision History

Date Description Author Comments

<date> <Version 1> <Your Name> <First Revision>

Document Approval
The following Software Requirements Specification has been accepted and approved by the
following:

Signature Printed Name Title Date

<Your Name> Lead Software Eng.

3
 Table of Contents

Chapter 1 ................................................................................................................................................. 6
1. Introduction ..................................................................................................................................... 7
1.1. Introduction to Online Food Ordering .................................................................................... 7
1.2. Purpose.................................................................................................................................... 7
1.3. Scope ....................................................................................................................................... 7
1.4. Definitions, Acronyms, and Abbreviations ............................................................................. 8
Chapter 2 ................................................................................................................................................. 9
2. General Description ...................................................................................................................... 10
2.1. Product Perspective ............................................................................................................... 10
2.2. Product Functions ................................................................................................................. 10
2.3. User Characteristics .............................................................................................................. 10
2.4. General Constraints ............................................................................................................... 11
2.5. Specific Constraints .............................................................................................................. 11
2.6. Assumptions & Dependencies .............................................................................................. 11
2.7. External Interface Requirements ........................................................................................... 11
2.7.1. User Interface ................................................................................................................ 11
2.7.2. Hardware Interface ........................................................................................................ 11
2.7.3. Software Interface ......................................................................................................... 11
2.7.4. Communication Interface (HTTP/HTTPS) ................................................................... 12
Chapter 3 ....................................................................................................................................... 13
3. Requirements and Analysis........................................................................................................... 14
3.1. Functional Requirements ...................................................................................................... 14
3.2. Introduction ........................................................................................................................... 15
3.2.1. Inputs............................................................................................................................. 15
3.2.2. Processing ..................................................................................................................... 15
3.2.3. Outputs .......................................................................................................................... 15
3.2.4. Handling Error .............................................................................................................. 15
3.3. Introduction ........................................................................................................................... 15
3.3.1. Inputs............................................................................................................................. 15
3.3.2. Processing ..................................................................................................................... 15
3.3.3. Outputs .......................................................................................................................... 15
3.4. Use Case................................................................................................................................ 16

4
 3.4.1. System Use Case ........................................................................................................... 16
3.5. Non-Functional Requirements .............................................................................................. 26
3.5.1. Performance .................................................................................................................. 26
3.5.2. Reliability ...................................................................................................................... 26
3.5.3. Availability ................................................................................................................... 26
3.5.4. Security ......................................................................................................................... 26
3.5.5. Maintainability .............................................................................................................. 26

5
Chapter 01
Introduction

6
1. Introduction
Online Food ordering system is a part of e-commerce. Online Food ordering greatly
simplifies the ordering process for both the customer. System presents an interactive and up-
to-date menu with all available options in an easy to use manner. Customer can choose one or
more items to place an order which will land in the Cart. Customer can view all the order
details in the cart before checking out. At the end, customer gets order confirmation details.
Once the order is placed it is entered in the database and retrieved in pretty much real time.
1.1. Introduction to Online Food Ordering
The motivation for designing this website is to motivate the customer. The customers of
today are not only attracted because placing an order online is very convenient but also
because they have visibility into the items offered, price and extremely simplified navigation
for the order.

1.2. Purpose
The purpose of SRS to extract all functional and non-functional requirement, Use-case, build
an analysis model extract entities their attribute and their Relationship, to build an analysis
model comprehensive.
1.3. Scope
Online Food Ordering System is a part of e-commerce. E-commerce or business through net
means distributing, selling, marketing, and servicing of products or services over electronic

7
systems such as the Internet and other computer networks. Thus, if we own a restaurant we
need to upload menu online to attract potential customers.
1.4. Definitions, Acronyms, and Abbreviations
 SRS: System Requirement Specification
 User: Who will interact the system?
 Database: Is used to store the data.
 Admin: Database Administrator can insert, delete, manage and organize data.

8
Chapter 02
General Description

9
General Description
 To increase efficiency and improve services.
 To be able to stand out from competitors in the food service industry.
 The home page of this web interfile provides an avenue where customers will be able
to gather more and reliable information about what the fast food industry really does.
1.5. Product Perspective
Delivery Limited Area: This feature used for limited area in the city.
Searching Facility: This feature used for searching all available items.
Security: This feature provides total security about user data.
Payment Choices: This feature provides the facility to pay money on that time and after
home delivery.
Reliable: This feature provides the reliability of system.
Features Food-Panda KhaoPiyo.pk EatOye!

Delivery Limited Yes Yes Yes

Area

Searching Facility Yes Yes Yes

Security Yes Yes No

Payment Choices Yes No Yes

Reliable No No No

1.6. Product Functions

 The user can search available items.
 User can choose one or more items.
 User can view all order details.
 Admin can manage orders and delivery of food.
 User can get confirmation detail.
1.7. User Characteristics
 The user should know how to use internet.
 The user should have general idea to visit website.

10
  The registered user must provide their information to fulfils the system requirement.
 The registered user must provide accurate data for delivery.
1.8. General Constraints
The general constraint means the requirements of the system and specification of the system.
The system should be useful for the project it competes the project requirement.
Here are some constraints for the given below:
Memory:The memory should be enough for the project database.
Hardware: Not required.
Operating System: For the project of “Online Food Ordering” the operating system should
be Microsoft Window XP, Vista, 7, 8, 8.1, and 10 of any version.
1.9. Specific Constraints
The specific requirements are for the interface the graphical interface is creating for the user.
Where the user can use to access the project by the easy interface. The interface different on
the different system, the system should compatible for the user where he can understand the
system easily. The specific requirement describes the system functionality.
1.10. Assumptions & Dependencies
 Website is online.
 Customers have connection to website.
 Payment method is available.

1.11. External Interface Requirements

1.11.1. User Interface
The Online Food ordering system screen display shall conform to the Process Impact Internet
Application User Interface Standard.The system shall provide a help link from each displayed
HTML page to explain how to use that page. The Web pages shall permit complete
navigation and food item selection using the keyboard alone, in addition to using mouse and
keyboard combinations.
1.11.2. Hardware Interface
Not Required
1.11.3. Software Interface
DBMS
Operating System: Windows (8/10)
Visual studio 2015

11
Web Browser: IE 10 or above, Mozilla FF 31 and above or Google Chrome
Visual studio software is developed to help computer science students to learn about the Web
application designing using ASP.NET from their basic capabilities to build a complete
working application from scratch. Further, it gives insight about how GUI interacts with
server-side language and finally with the database.
1.11.4. Communication Interface (HTTP/HTTPS)
The communication means the user communicates with the system for perform some task.
When the user opens the browser it’s actually communicating with the system. When user
login it communicates with online food site and online search food. User select food and give
payment by any way where he wants actually communicates with the admin of the system.

12
Chapter 03
Specific Requirement

13
2. Requirements and Analysis
2.1. Functional Requirements
Para# Initial Requirements

1 A customer “shall” place order for food.

2 A customer “shall” register himself to the system

3 The system “shall” provide two types of registration process, normal and
privileged

4 Admin “shall” accept, reject and temporarily avoid doing the requests on the basis
of credentials provided.

5 A customer “shall” login to the system and can change his password

6 System “shall” update the customer’s Request

7 System “shall” process different types of updating e.g. updating of his

personal/shipping details, or upgrading of his status from registered to privileged
customer, or updating of his payment methodology

8 A customer “shall” view his details for verification purposes

9 CA “shall “accept, reject and temporarily waive the requests on the basis of
credentials provided.

10 System “shall” search any customer details

11 Both registered and privileged customers “will “order for food.

12 Customer “shall” make payment on food delivery at home.

13 System “shall” generate invoice, confirmation receipt and finally will place order

14 User “shall” view the status of their orders by providing the Order Number

15 Privileged customers “shall “place the request for the updating of their orders if
the orders are not shipped.

14
16 Privileged customer “shall” place the request for the cancellation of the order. But
all these updating and cancellation requests are to be viewed by the Order
Administrator in order to accept, reject, or waive them.

17 An action event "shall" be generated for a corresponding administrator when a

request is placed for updating of orders or customer details etc

18 Corresponding administrator "shall" view his Action List containing different

actions, and correspondingly process these pending actions

19 When the action processing is completed or if the action is just a notification

message then administrator "shall" delete these actions from the action list

2.2. Introduction
A customer “shall” place order for food.
2.2.1. Inputs
 Select food item.
 Place identity.
 Login
2.2.2. Processing
Verify User from Database
2.2.3. Outputs
Show all available food items.
2.2.4. Handling Error
Food item are not available show the message.
2.3. Introduction
Admin “shall” accept, reject and temporarily avoid doing the requests on the basis of
credentials provided.
2.3.1. Inputs
 Accept correct user data.
 View all details provided by user.
2.3.2. Processing
Process and check user order is available.
2.3.3. Outputs
Acknowledgement for order.

15
2.4. Use Case
2.4.1. System Use Case

16
17
Use Case Description

UC-ID UC-01

UC-Name UC-user-login

Description: This use case describes how user can login the system.

Actor User

Pre-Condition:  The user must have a valid username and password.

 The user must be on the webpage of online food ordering

System.

Basic Flow:

1. The user will select the sign in link on the website.

2. The user enters his username.
3. The user enters his password.
4. If the given data is valid then the system jumps it to the next page.
5. The user is ready for doing his work.

Alternative Flow: If the email or password are wrong the system will display SORRY
message.

Post-Condition: User has privilege to perform actions.

18
UC-ID UC-02

UC-Name UC-select/search item

Description: This use case describes how to search and select food items.

Actor User

Pre-Condition:  User must be on the homepage of online food ordering

System.
 User can select or search food items by all listed in the
dropdowns.

Basic Flow:

1. The User clicks on the items.

2. System displays the available items.
3. The User click on the Detail button to view all food details.

Alternative Flow: If required item are not available the system will display SORRY
message.

19
UC-ID UC-03

UC-Name UC-order

Description: This use case describes how user can order food from the system.

Actor User

Pre-Condition:  The user must have a valid username and password.

 The user must be login for order.

Basic Flow:

1. User can view the food item.

2. The user can select the food item.
3. User can add own choice item.
4. Proceed and confirm item.

Alternative Flow: User click on another link of its homepage.

Post-Condition: Order is successful.

20
UC-ID UC-04

UC-Name UC-Logout

Description: This use case describes how users can logout from the system.

Actor User

Pre-Condition: The user must be logged in.

Basic Flow:

1. The user clicks on the logout link.

2. System deletes their session.
3. Then user logout from the system

Alternative Flow: User click on another link of its homepage.

Post-Condition: User has no privilege to perform any actions.

21
 Online Food Ordering

LogIn

View Shipment /
Order

Manage Order

Confrm Order
Admin

Delete User

Delivery Boy

Ship Order /
Deliver Order

22
UC-ID UC-05

UC-Name UC-admin-login

Description: This use case describes how admin can login the system.

Actor Admin

Pre-  The admin must be on the webpage of Online Recruitment

Condition: System.
 The admin must have a valid username and password.

Basic Flow:

1. The admin clicks on the sign in link on the website.

2. The admin enters his username and password and clicks on the Sign In button.
3. If the given data is valid then the system jumps it to the next page.
4. The admin is ready for doing his work.

Alternative Flow: If the email and/or password is wrong the system will display SORRY
message.

Post-Condition: Admin have privilege to perform actions.

23
UC-ID UC-06

UC-Name UC-View/Confirm/Delete

Description: This use case describes how admin can view and confirm order.

Actor Admin

Pre-  The admin can view user details and order.

Condition:

Basic Flow:

1. The admin can view user order details.

2. The admin has authority to delete the user.
3. If the user select item, then admin confirm the order.
4. The admin is ready for doing his work.

Alternative Flow: If the email and/or password is wrong the system will display SORRY
message.

Post-Condition: Admin have privilege to perform actions.

24
UC-ID UC-07

UC-Name UC-Logout

Description: This use case describes how admin can logout from the system.

Actor Admin

Pre-Condition:  The admin must be logged in.

Basic Flow:

1. The admin clicks on the logout link.

2. System deletes their session.
3. Then admin logout from the system

Alternative Flow: Admin click on another link of its homepage.

Post-Condition: Admin have privilege to perform actions.

25
2.5. Non-Functional Requirements
Non-functional requirements should be performing all operations of the system. The
performance of the system can be effective. Some nonfunctional requirements are given here.
2.5.1. Performance
The performance of the system should be effective; it should be meet with the requirements
of the system. When the user opens the site or the other application it should be open quickly.
2.5.2. Reliability
The system should be reliable for the user, the user can buy or sell the product easily, the
system should not be ambiguous. The admin responsibility to make system reliable.
2.5.3. Availability
The availability means the online site should be available for the user. The user anywhere and
anytime wants to order food. The availability of the site can make more users can use of the
site.
2.5.4. Security
The security means the project should be secure, unauthorized person cannot access system.
Just registered user can access the system and order food.
2.5.5. Maintainability
The maintainability of system performed by the admin. Because the admin owner of the site
and all over the management in the owner hand, and the owner can select the and reject the
request of the user.

26
Chapter 04
Analysis Model

27
Class Diagram

Sequence Diagrams

Sequence Diagram#1

This diagram describes how user registers.

28
Sequence Diagram#2

This Sequence diagram describes how the user Login with the system.

29