Final Year Project Report

Ghazi Abbas

Roll Number: BL028

Session: 2015-2019

Supervisor: Dr. Malik Saad Missen

A report submitted in partial fulfilment of the degree of

BS in Computer Science (BSCS)

Department of Computer Science and IT

The Islamia University of Bahawalpur
 Food Order Application

Project Title:

Online Food Order Application

Revision History
Date Description Author Comments
<date> <Version 1> <Your Name> <First Revision>
Muhammad Ghazi

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

Signature Printed Name Title Date

Dr. Muhammad Saad Supervisor,DCS&IT 21306 <date>
Missen

ii
Software Requirements Specification
 Food Order Application

Table of Contents

1. Introduction 1
1.1 Purpose Error! Bookmark not defined.
1.2 Scope Error! Bookmark not defined.
1.3 Definitions, Acronyms, and Abbreviations. 1
1.4 References Error! Bookmark not defined.
1.5 Overview Error! Bookmark not defined.
2. The Overall Description 2
2.1 Product Perspective 2
2.1.1 Operations 2
2.1.2 Site Adaptation Requirements 2
2.2 Product Functions 2
2.3 User Characteristics 2
2.4 General Constraints 3
2.5 Assumptions and Dependencies 3
3. Specific Requirements 3
3.1 External Interface Requirements 3
3.1.1 System Interfaces 3
3.1.2 Interfaces 3
3.1.3 Hardware Interfaces 4
3.1.4 Software Interfaces 4
3.1.5 Communications Interfaces 4
3.2 Functional Requirements 4
3.2.1 <Functional Requirement or Feature #1> 4
3.2.2 <Functional Requirement or Feature #2> 4
3.3 Use Cases 5
3.3.1 Use Case #1 5
3.4 Classes / Objects 6
3.4.1 <Class / Object #1> 6
3.4.2 <Class / Object #2> 6
3.5 Non-Functional Requirements 6
3.5.1 Performance 6
3.5.2 Reliability 6

iii
Software Requirements Specification
 Food Order Application

3.5.3 Availability 6
3.5.4 Security 6
3.5.5 Maintainability 6
3.5.6 Portability 6
3.6 Inverse Requirements 6
3.7 Logical Database Requirements 6
3.8 Design Constraints 6
3.8.1 Standards Compliance 6
4. Analysis Models 7
4.1 Sequence Diagrams 7
4.2 Data Flow Diagrams (DFD) 8
4.3 State-Transition Diagrams (STD) 9
5. Supporting Information 9

iv
Software Requirements Specification
 Food Order Application

1. Introduction
The Taste It is an Android application. This application works as a great tool of
time saving as it overcome the paper work , the organization just have to install
this application and start working , it is like a plug & play application. This
application has the attributes like making, canceling, confirming the order and also
saves all the required information about the order, customer and employees.
1.1 Purpose
The main purposes of this application are as follows:
A great tool of time saving.

Easy to maintain & manipulate order.

1.2 Scope
 Only manager is allowed to interact with the admin panel.
 Other employees are not allowed to interact with the system.
 Stock is managed only by the manager.
 Manager can view the orders.
 Customer will download application, sign in, sign up and order food.
 Only manger is able to store the record of employees.
 Manager can easily manipulate all the record as needed.
 It is an online application.

1.3 Definitions, Acronyms, and Abbreviations.

 Manager: is the person who can receive order, update database and manipulate order
and all the data in database as required.
 Customer: is a person who steps into our food order application and order any of his
desired taste.
 Employees: are the peoples who are working under manager.

1.4 References
I am working on my own. We are not getting any help from other source.
1.5 Overview
This application is used for selling our products. The remaining part of this document includes
two sections. The second section consists on functional requirement and dealings with customer.
Additionally this section defines supposition and checks.

SRS Document 1.0 Page 1 of 9 06/21/19 f

 Food Order Application

The third section defines the requirements specification.

.
2. The Overall Description
2.1 Product Perspective
The “Taste IT” is developed for all restaurants (Fast Food etc.). All quantity,
qualities and prices of different foods will be stored in our online database.
Customer will open our “Taste It” and check our menu card and order the food
whatever he wants or what quantity he wants and orders online after that the
manager will receive this order will send a delivery boy with order.
1.1.1 Operations
Manager Login: For collaboration with system.
Add new food items.
Accept and proceed orders.
Customer Login: For ordering the food.
Modify: For pupation in database and employees records.
Logout: For disconnection from the system.

1.1.2 Site Adaptation Requirements

Application will interact with Google FireBase Online Database

2.2 Product Functions

1. Manager must login for interaction with system.
2. Customer orders our app Taste It and will decide that which food he/she wants.
3. Manger will receive the order of customer in admin panel of Taste It.
4. When Manger will store the order of customer in database, click the done button the receipt
will be generated automatically and sends delivery boy with order.

SRS Document 1.0 Page 2 of 9 06/21/19 f

 Food Order Application

2.3 User Characteristics

Manager:
 ID
 Password
Customer (Login to App):
 ID
 Password
2.4 General Constraints

 GUI should be in English and displaying photos of all food items.

 Manager must provide his/her ID to interact with system.
 Manager can manipulate customer’s order and employee’s data.

2.5 Assumptions and Dependencies

1. First one is supposition is that this is android application.
2. Does not need any extra hardware.
3. System is integrated with Google FireBase Online Database (Using Jason)
4. System depends on Android (Front End in XML, Backend in Java).

3. Specific Requirements
3.1 External Interface Requirements
3.1.1 System Interfaces
In the very first step the manager will authenticate his/herself. Then main page will open where
all categories of available foods are in Recycler View of Home. User After selecting food, add in
to cart and checking out of cart a confirmation pop up message will appear.

3.1.2 Interfaces
 First of all screen shows Sign In(For account holder) and Sign Up(For new User) buttons
then move to food page.
 As described above food page will consists of information and photographs about
all the available categories of foods and after clicking on done button a

SRS Document 1.0 Page 3 of 9 06/21/19 f

 Food Order Application

confirmation pop up message will appear.

 When manager/user give ID and password and click the login button the main page
will open and login form will disappear.

3.1.3 Hardware Interfaces

Our system is not so heavy, thus no extra hardware is needed to operate it. Any android device
with internet connection can open application and server is organized online using Google
FireBase Online Database (Using Jason).
Recommended hardware requirements to manage system is a an android device.
3.1.4 Software Interfaces
 Google firebase as database and OS(Android)
3.1.4.1 Google firebase Database
Our System uses Google firebase as its database component. Manager can
manage and update database as required.
3.1.5 Communications Interfaces
 The System will interact with online firebase server.
3.2 Functional Requirements

 Our system provides these facilities.

 Store customer order in database.

 Our system provides a feature to update database in future as required.
 The system saves the record of our daily orders.
 Manager must provide ID and Password before interacting with the
system for authorization purpose.
 System must provide security from unauthorized access.

SRS Document 1.0 Page 4 of 9 06/21/19 f

 Food Order Application

3.3 Use Cases

Login

Receive and manipulate Order

Manage database

Manager
Logout Customer

Place Order

Manager/User login with ID and password

Manipulate employee record Manager has the authority to update or

even delete.

Check daily sale As ordering record is stored with date

we can also check daily sale whenever
we want.

Purchase Foods Customer can purchase food.

Generate bill A bill will be automatically generated

when the order is processed.

Employee detail Every employee detail will be stored in

database

SRS Document 1.0 Page 5 of 9 06/21/19 f

 Food Order Application

3.4 Classes / Objects

This section contains major categories of the “Taste IT”.
3.4.1 <Manager>
3.4.1.1 ID, Password
3.4.1.2 for login for interaction with system
3.4.2 <User>
3.4.2.1 Name, Cell number
3.4.2.2 for storing information of user
3.4.3 <Foods>
3.4.3.1 Category
3.4.3.2 for storing food categories
3.5 Non-Functional Requirements
3.5.1 Performance: Working will be fast.
3.5.2 Reliability: System will be easy to operate.
3.5.3 Availability: The system is easy to use because GUI is provided.
3.5.4 Security: System will restrict unauthorized access.
3.5.5 Maintainability: System will be easy to update as needed.
3.5.6 Portability: System will be easy to use on any Android Device.
3.6 Inverse Requirements
 Food can only be selected from our given categories.
3.7 Logical Database Requirements
 Database must be valid for the system.
 The database must possess all the record of our system.
 Customer is not allowed to interfere with the database.
 There will be different tables in database manager authentication, user records
and food category record.
3.8 Design Constraints
 All fields must be filled correctly
 User’s data will automatically be stored in firebase database on user sign up.
 After completing an operation display a message of record save or error.
 All necessary fields must be filled.

SRS Document 1.0 Page 6 of 9 06/21/19 f

 Food Order Application

4. Analysis Models

4.1 Sequence Diagrams

Manager Database Cook

Order Food
Save Food Order

Place Food Order

Customer

Assemble Order

SRS Document 1.0 Page 7 of 9 06/21/19 f

 Food Order Application

4.2 Data Flow Diagrams (DFD)

Receives
Taste It Data
Places Order Manager
Application/
Customer
Database

Order
Proceeded

Order
Order Delivered Prepared
Delivery Boy Cook

SRS Document 1.0 Page 8 of 9 06/21/19 f

 Food Order Application

4.3 State-Transition Diagrams (STD)

View Food Select Category

Detail (Menu)

Place Order

No
Confirm Order

Yes

Bill Generation/

Cash on delivery

5. Supporting Information
I did not get any help from anyone else.

SRS Document 1.0 Page 9 of 9 06/21/19 f