Mine

Food Delivery App
FOOD DELIVERY APP
The Minor Project Report Submitted to
Rajiv Gandhi Proudyogiki Vishwavidyalaya , Bhopal
towards partial fulfillment of the the degree of
Bachelor Of Technology
In
Computer Science
Guided by: Submitted by:

PROF.Vaishali Pathak Aman Patel
Deepanshu Yadav
Shweta Sen
Computer Science Engineering Department

MAHAKAL INSTITUE OF TECHNOLOGY & MANAGEMENT
Department Of Computer Science & Engineering, Mahakal Institute of Technology & Management ,Ujjain
Food Delivery App
MAHAKAL INSTITUTE OF TECHNOLOGY & MANAGEMENT ,

UJJAIN
RECOMMENDATION
This is to certify that Ms. Shweta Sen , Mr . Deepanshu Yadav ,Mr. Aman
Patel , students of V semester/3 year B.E. (CSE) in the year 2023 of Computer
Science Engineering Department of this institute has completed their work on
“FOOD DELIVERY APP ” for Minor project based on syllabus and has
submitted a satisfactory account of their work in this report which is
recommended for the partial fulfillment of the degree of Bachelor of
Technology in Computer Science.
Project Guide, HOD,

CSE Dept. CSE Dept.
M.I.T.M. Ujjain M.I.T.M. Ujjain
Director,
M.I.T.M. Ujjain
Food Delivery App
MAHAKAL INSTITUTE OF TECHNOLOGY & MANAGEMENT
CERTIFICATE
This is to certify that the Minor Project report entitled “FOOD DELIVERY APP”
submitted by Ms. Shweta Sen , Mr . Deepanshu Yadav , Mr. Aman Patel, student of
B.Tech V Semester, Computer Science Engineering department in the year 2023, is
a satisfactory account of their work based on syllabus which is accepted in partial
fulfillment of degree of Bachelor of Technology in Computer Science Engineering.
Internal Examiner External Examiner
Date Date
Food Delivery App
ACKNOWLEDGEMENT
We would like to express our sincere gratitude to Prof. Mrs. Vaishali Pathak,
Department of Computer Science , whose role as project guide was invaluable
for the project. We are extremely thankful for the keen interest she took in
advising us, for the books and reference materials provided for the moral
support extended to us.
I am also indebted to our Head of the Department (CSE), Prof. Deepali Kelkar
for his unconditional help and inspiration.
Date : 22 Nov 2023 ( AMAN PATEL )
Roll no. : 0714CS211010
( SHWETA SEN )
Roll no. : 0714CS211076
( DEEPANSHU YADAV)
Roll no. : 0714CS211021
Food Delivery App
ANTI PLAGIARISM DECLARATION
 I know that plagiarism means taking and using the ideas, writings, works
or inventions of another as if they were one’s own. I know that
plagiarism not only includes verbatim copying, but also the extensive use
of another person’s ideas without proper acknowledgement (which
includes the proper use of quotation marks). I know that plagiarism
covers this sort of use material found in textual sources and from the
Internet.
 I acknowledge and understand that plagiarism is wrong.
 I understand that my project work must be accurately referenced. I have

followed the rules and conventions concerning referencing, citation and
the use of quotations as set out in the Department Guide.
 This assignment is my own work, or my group’s own unique group

assignment. I acknowledge that copying someone else’s assignment, or
part of it, is wrong, and that submitting identical work to others
constitutes a form of plagiarism.
 I have not allowed, nor will I in the future allow, anyone to copy my
work with the intention of passing it off as their own work.
Food Delivery App
TABLE OF CONTENTS
Topics PageNo.
1. Abstract................................................................................................. 1
2. Introduction ........................................................................................... 2
3. Software Requirement Specification ....................................................... 3
4. System Planning & SDLC……………………………………………...8
5. Constraints of use ................................................................................ 9
6. Implementation…………………………………………………………9
7. Feasibility Study.................................................................................. 11
8. Entity relationship diagram(ERD)…………………………………….12
9. Data flow diagram (DFD) .................................................................... 12
10. Database designed ............................................................................. 15
11. Unified Modeling Language (UML) Diagram………………………..16
12. Source Codes ..................................................................................... 18
13. Screenshots of application……………………………………………21
14. Aim and Objectives…………………………………………………...23
15. Future Scope of Work..................................................................... 23
16. Conclusion .......................................................................................... 23
17. Bibliography…………………………………………………………..24
Food Delivery App
1. ABSTRACT
Online food ordering system is mainly designed primarily function for use in the food
delivery industry. This system will allow hotels and restaurants to increase online food
ordering such type of business. The customers can be selected food menu items just few
minutes. In the modern food industries allows to quickly and easily delivery on customer
place. Restaurant employees then use these orders through an easy to delivery on customer
place easy find out navigate graphical interface for efficient processing.
Our proposed system is an online food ordering system that enables ease
for the customers. It overcomes the disadvantages of the traditional queueing system.
Our proposed system is a medium to order online food hassle free from restaurants as well
as mess service. This system improves the method of taking the order from customer. The
online food ordering system sets up a food menu online and customers can easily place the
order as per their wish. Also with a food menu, customers can easily track the orders. This
system also provides a feedback system in which user can rate the food items
Food Delivery App
2. INTRODUCTION
In a modern generation Online food ordering is a mobility of food deliveryor takeout

from a local restaurant or food cooperative. Now days the rapid growth in the use of internet
and the technologies associated with it, the several opportunities are coming up on the web
or mobile application. This is made possible through the use of electronic payment system.
The payment can be done through the customer’s credit card, debit card. It is possible for
everyone toorder any goods from anywhere the internet and have the goods delivered at
his/her home. All types made be internet le transaction ads to the economic of digital cash,
the necessary tool for this process telecommunication with customers.
The system will become an important tools use for restaurant to improve the management
aspect by use of computer system to connected each and every food ordering transaction
instead of data record on it. In addition, it can also provide efficiency for the restaurant by
reducing time consuming, minimize human errors or delivery and providing good quality
and service to customers. In terms of the integrity and availability of the system provided, it
can be concluded that this system is a suitable solution
Food Delivery App
3. SOFTWARE REQUIREMENT SPECIFICATION (SRS)
3.1 Introduction
3.1.1 Purpose
The purpose of this SRS is to outline both the functional and non-functional
requirements of the subject Restaurant food ordering system. In addition to said
requirements, the document also provides a detailed profile of the external interfaces,
performance considerations and design constraints imposed on the subsequent
implementation. The document should act as a foundation for efficient and well-managed
project completion and further serve as an accurate reference in the future.
3.1.2 Document Conventions
RFOS- restaurant Food Ordering System
SRS - Software Requirements Specification
DBMS Database Management System
LAN Local Area Network
IP Internet Protocol
TCP Transmission Control Protocol
UDP User Datagram Protocol
IEEE 802.11 Wireless Local Area Network Standard
3.1.3 Intended Audience and Reading Suggestions
The primary audience of this SRS document will be the development team employed to
implement the specified Restaurant food ordering system. It will not only provide an
extensive capacity for project planning and progress assessment but it will further assist with
stake holder interactions. The secondary document audience comprises the stakeholders of
the project, that is, restaurateurs and associated staff. To this audience group, this SRS
should convey and confirm the required functionality and represent a contractual agreement
between the involved parties.
3.1.4 Project Scope
In current formal dining environments, some form of physical static menu is utilized to
convey the available food and beverage choices to customers. Said menus are generally
paper based and hence impose restrictions on the textual real estate available and the ability a
Food Delivery App
restaurateur has to update them. The related concepts are encompassed by the general scope
of the Restaurant food Ordering System. It is to the replacement of paper-based menus using
an electronic format.
3.1.5 References
C. Larman, APPLYING UML AND PATTERNS An Introduction to Object-Oriented

Analysis and Design and Iterative Development, 3rd ed., Massachusetts: Pearson Education,
2005.D. Carrington, CSSE3002 Course Notes, School of ITEE University of Queensland,
2008IEEE Recommended Practice for Software Requirements Specifications, IEEE Standard
830, 1998.
3.2 Overall Description
3.2.1 Product Perspective
The software described in this SRS is the software for a complete Restaurant food ordering
system. The system merges various hardware and software elements and further interfaces
with external systems. it relies on a number of external interfaces for persistence and
unhandled tasks ,as well as physically interfacing with humans.
3.2.2 Product Features
The Restaurant food ordering system interfaces with an existing payment system, including
a cash register and software accessible credit system, in order to quickly and easily handle
customer billing. The payment system should be operable such that it can return information
to the RFOS system as to whether payment was successful or failed.
3.2.3 User Classes and Characteristics
There are three separate user interfaces used by the RFOS software, each related to an
interfaced physical hardware device . These three user interfaces are the Surface Computer
UI ,Tablet UI and Display UI.
3.2.4 Operating Environment
The Surface Computer UI is the interface used by restaurant customers. This interface uses
the surface computer paradigm - users interact with the system by dragging 'objects' around
on the fla tscreen touch-sensitive display .The Tablet UI is designed to run on a small,
wireless-enabled touch-screen tablet PC, to be used by waiters to accommodate customer
needs. The Display UI provides kitchen staff with simple functionality related to ordered
items.
Food Delivery App
3.2.5 Design and Implementation Constraints
The RFOS should be written in an object-oriented language with strong GUI links and a
simple, accessible network API. The primary candidate tool chains are Java/Swing, C++/Qt
and Python/Qt. The system must provide a capacity for parallel operation and system design
should not introduce scalability issues with regard to the number of surface computers,
tablets or displays connected at any one time .The system must be reliable enough to run
crash and glitch free more or less indefinitely, or facilitate error recovery strong enough such
that glitches are never revealed to its end-users.
3.2.6 User Documentation
The end-users of the RFOS fall into three primary categories, unskilled, partly skilled and
highly skilled.
3.2.7 Assumptions and Dependencies
The SRS assumes that none of the constituent system components will be implemented as
embedded applications .It is further assumed that tablet PCs of sufficient processing
capability and battery life will be utilized.
3.3. System Features
Functional requirements are listed first, according to their relationship to the overall system
,customers, waiters, chefs and supervisors.
Customer
A customer shall be able to engage their menu by double tapping the activated surface
computer in their table. A customer shall be able to add an item to a pending order by
dragging the item from the engaged menu onto the order. A customer shall be able to remove
an item from a pending order by dragging the item off the order .A customer shall be able to
add a special dietary requirement to an order by dragging the requirement from the engaged
menu onto the order .When in billing mode, a surface computer shall display a
representation of a bankcard payment for each customer.
Waiter
A waiter assigned to a table shall be alerted via their wireless tablet when: An order is
placed from that table An item ordered by that table is rejected by the kitchen An item
ordered by that table is ready to be served The table has requested waiter assistance. A
tablet shall allow a waiter to accept , reject and modify an order placed by a customer
through a surface computer. A tablet shall allow a waiter to process a payment using cash or
a bankcard.
Food Delivery App
Chef
A chef shall be able to accept or reject a customer’s order item through a display.A chef
shall be able to indicate that a customer’s order item is ready to be served through a display.
Supervisor
A supervisor shall be able to abort/purge a table's account/meals from the active system with
no expectation of payment. A supervisor shall be able to issue a refund for one or more items
to a customer
3.4 External Interface Requirements
3.4.1 User Interfaces
This interface uses the surface computer paradigm - users interact with the system by
dragging 'objects' around on the flat screen touch-sensitive display. For the RFOS, users can
manipulate objects such as items of food, dietary requirements, tips and menus on the
surface of their table. Such objects can be moved into static objects such as meals and
payments to perform various functions. In addition to this object manipulation paradigm, a
limited system menu is necessary. Users will summon their restaurant menu, which is
combined with a system/command menu, using an easy touch gesture, a double-tap on the
touch surface, and dismiss it with a similar gesture or by tapping a close button GUI
element.
3.4.2 Hardware Interfaces
These devices are the surface computers, the wireless tablets and the touch displays. All
three devices must be physically robust and immune to liquid damage and stains. The
devices(with the possible exception of displays) must also have good industrial design
aesthetics, as they are to be used in place of normal restaurant tables and notepads and will
be in direct contact with customers.
3.4.3 Software Interfaces
The RFOS will interface with a Database Management System (DBMS) that stores the
information necessary for the RMOS to operate. The DBMS must be able to provide, on
request and with low latency, data concerning the restaurant's menu, employees (and their
passwords) and available dietary requirements.
Food Delivery App
3.4.4 Communications Interfaces
The RFOS will interface with a Local Area Network (LAN) to maintain communication with
all its devices. It should use a reliable-type IP protocol such as TCP/IP or reliable-UDP/IP
for maximum compatibility and stability. All devices it will interface with should contain
standard Ethernet compatible, software accessible LAN cards to maintain communication
between the server and the surface computers, tablets, displays and the external payment
system.
3.5 Other Nonfunctional Requirements
This subsection presents the identified non-functional requirements for the subject RFOS.
The subcategories of non-functional requirements given are performance, safety, securtity
requirements.
3.5.1 Performance Requirements
The server shall be capable of supporting an arbitrary number of surface computers, tablets
and displays, that is, it shall provide no limit on how many devices are in the system .The
server shall be capable of supporting an arbitrary number of active customer payments, that
is, no payments shall be lost under any circumstances.
3.5.2 Safety Requirements
The system shall log every state and state change of every surface computer, tablet and
display to provision recovery from system failure. The system shall be capable of restoring
itself to its previous state in the event of failure(e.g. a system crash or power loss).The
system shall be able to display a menu at all times to facilitate manual order taking should
the need arise. The system shall utilize periodic 30-second keep-alive messages between
tablets and the server to monitor tablet operational status.
3.5.3 Security Requirements
A waiter password used for tablet login must have a bit-strength of at least 64 bits. A waiter
password used for tablet login must be changed every three months. A waiter shall only be
able to log into one tablet at any given instance of time. A waiter that attempts to log into a
second tablet while already logged into.
3.5.4 Software Quality Attributes
The software shall be capable of supporting an arbitrary number of surface computers,

tablets and displays, that is, it shall provide no limit on how many devices are in the system.
It shall7 be capable of supporting an arbitrary number of active meals/orders, that is, no
meals/orders shall be lost under any circumstances.
Food Delivery App
4. SYSTEM PLANNING & SDLC
We have chosen “Iterative Life Cycle Model” for developing this application, because an
iterative life cycle model does not attempt to start with a full specification of requirements.
Instead, development begins by specifying and implementing just part of the software, which
can then be reviewed in order to identify further requirements. This process is then repeated,
producing a new version of the software for each cycle of the model.
Here is the diagram of the iterative life cycle model which depicts its working flow.
Design0 Design1 Design n
Implement0 Implement1 ………. Implement n
Analysis 0 Analysis1 Analysis n
Few advantages for choosing the SDLC are –
 In iterative model we are building and improving the product step by step. Hence, we
can track the defects at early stages. This avoids the downward flow of the defects.
 Testing and debugging in smaller iteration is easy.
 In iteration model we can get the reliable user feedback. When presenting sketches
and blueprints of the product to user for their feedback, we are effectively asking
them to imagine how the product will work.
 Progress can be measured.
 In iterative model less time is spent on documentation and more time is given for
designing.
 Risk are identified and resolved during iteration; and each iteration is an easily
managed milestone. It supports changing requirements.
Food Delivery App
5. CONSTRAINTS OF USE
 Admin and user must remember login id and password.

 User need to have a personal computer or cell phone with internet connection
6. IMPLEMENTATION
6.1 Software Platform
6.1. 1 Front -end Design: HTML, CSS, Bootstrap
Hypertext Markup Language (HTML) is the standard markup language for creating web
pages and web applications. With Cascading Style Sheets (CSS) and JavaScript, it forms
a triad of cornerstone technologies for the World Wide Web. Web browsers receive
HTML documents from a web server or from local storage and render the documents
into multimedia web pages. HTML describes the structure of a web page semantically
and originally included cues for the appearance of the document.
Cascading Style Sheets (CSS) is a style sheet language used for describing the
presentation of a document written in a markup language like HTML.CSS is a
cornerstone technology of the World Wide Web, alongside HTML and JavaScript.CSS is
designed to enable the separation of presentation and content, including layout, colors,
and fonts. This separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable multiple web pages to
share formatting by specifying the relevant CSS in a separate. CSS file, and reduce
complexity and repetition in the structural content.
Bootstrap is a free and open-source front-end library for designing websites and web
applications. It contains HTML- and CSS-based design templates for typography, forms,
buttons, navigation and other interface components, as well as optional JavaScript
extensions. Unlike many web frameworks, it concerns itself with front-end development
only.
6.1.2 Client side validation: JavaScript, jQuery
Java Script often abbreviated as JS, is a high-level, interpreted programming language. It

is a language which is also characterized as dynamic, weakly typed, prototype-based and
multi-paradigm. Alongside HTML and CSS, JavaScript is one of the three core
technologies of the World Wide Web. JavaScript enables interactive web pages and thus
is an essential part of web applications. The vast majority of websites use it, and all
major web browsers have a dedicated JavaScript engine to execute it.
Food Delivery App
JQuery is a cross-platform JavaScript library designed to simplify the clientside scripting

of HTML. It is free, open-source software using the permissive MIT License. Web
analysis indicates that it is the most widely deployed JavaScript library by a large
margin.
6.1.3 Server side validation : Ajax
Ajax is not a single technology. Ajax is a set of Web development techniques using
many Web technologies on the client side to create asynchronous Web applications.
With Ajax, Web applications can send and retrieve data from a server asynchronously (in
the background) without interfering with the display and behavior of the existing page.
By decoupling the data interchange layer from the presentation layer, Ajax allows Web
pages, and by extension Web applications, to change content dynamically without the
need to reload the entire page.
6.1.4 Database : MySQL
MySQL is an open source relational database management system. For proprietary use,
several paid editions are available, and offer additional functionality. In this project
MySQL has been used to store, update, retrieve and delete related to user’s data and
other additional data about projects.
6.1.5 Web Server : Apache
The Apache HTTP Server, colloquially called Apache, is a free and opensource cross-
platform web server, released under the terms of Apache License 2.0. Apache is
developed and maintained by an open community of developers under the auspices of the
Apache Software Foundation.. The Apache HTTP Server is crossplatform; as of 1 June
2017 92% of Apache HTTPS Server copies run on Linux distributions. Version 2.0
improved support for non-Unix operating systems such as Windows and OS/2. Old
versions of Apache were ported to run on OpenVMS and NetWare.
6.2 Hardware Platform

Intel Corporation (commonly known as Intel) is an American multinational corporation
and technology company headquartered in Santa Clara, California. It is one of the world's
largest semiconductor chip manufacturers by revenue,[3][4] and is one of the developers of
the x86 series of instruction sets found in most personal computers (PCs). Incorporated in
Delaware,[5] Intel ranked No. 45 in the 2020 Fortune 500 list of the largest United States
corporations by total revenue for nearly a decade, from 2007 to 2016 fiscal years.[6] Intel
supplies microprocessors for most computer system manufacturers. Intel also manufactures
motherboard chipsets, network interface controllers and integrated circuits, flash memory,
graphics chips, embedded processors and other devices related to communications and
Food Delivery App
computing. Intel (Integrated electronics) was founded on July 18, 1968, by semiconductor
pioneers Gordon Moore (of Moore's law), Robert Noyce (1927–1990), Arthur Rock (venture
capitalist) and is associated with the
7 . FEASIBILITY STUDY
A feasibility study is an analysis of how successfully a project can be completed,
accounting for factors that affect it such as economic, technological and operational.
Project managers use feasibility studies to determine potential positive and negative
outcomes of a project before investing a considerable amount of time and money into it.
During the stage of our feasibility study, we had to undergo the following steps as
described under:
 Identify the origin of data at different levels of the system.
 Identify the expectation of end user from the finished product/system.
 Analyze the drawback(s) of the existing system.
 Technical feasibility study:

It lays out details on how a good or service will be delivered, which includes
transportation, business location, technology needed, materials and labour.
 Financial feasibility study:

It is a projection of the amount of funding or startup capital needed, what sources
of capital can and will be used and what kind of return can be expected on the
investment.
 Organizational feasibility study:

It is a definition of the corporate and legal structure of the business; this may
include information about the founders, their professional background and the skills
they possess necessary to get the company off the ground and keep it operational.
Food Delivery App
8. ENTITY RELATIONSHIP DIAGRAM
9. DATA FLOW DIAGRAM (DFD)
 Level 0
Food Delivery App
 Level 1
 Level 2
Food Delivery App
 Level 3
Food Delivery App
10 . Da ta ba se De s ig n
Food Delivery App
11. UNIFIED MODELING LANGUAGE (UML) DIAGRAM
11.1 Use case Diagram
Fig. Usecase Diagram of food ordering app
Food Delivery App
11.2 Activity Diagram
Food Delivery App
12. SOURCE CODE

12.1 Select state()
12.2 Register User()
Food Delivery App
12.3 Login user()
12.4 Active User()
Food Delivery App
12.6 Get Post()
12.7 Resend OTP()
12.8 My Post()
Food Delivery App
13. SCREENSHOTS OF APPLICATION

13.1 Homepage
13.2 Settings Dropdown
Food Delivery App
13.2 Menu
13.4 Delivery information
Food Delivery App
14. AIM & OBJECTIVES

 The very first thing keeping in our mind we are developing this project is to
gather all the college members, starting from administrative level to the basic
clerical section into a single frame.
 Our aim is to convey all the notice(s), event(s), corrigendum(s) etc. and
moreover what is going around the college.
 To grow the teacher and student relationship stronger. Last but not the least 24
X 7 connectivity with college campus.
15. FUTURE SCOPE OF WORK

The tremendous popularity of using the social media networking could never have been
realized before. In fact, social media have become an important tool of marketing in true
sense of customer orientation. But this kind of social networking site which can access only
for college campus not from outside the college will make a dramatic changes inside the
college campus.
 The scope of Food delivery app is widening and today it offers a strong support to
the Restaurant owner in providing the much desired touch of concern.
 The bright future prospect of college networking is also proven with the fact that the
technology is integrated in mobile phones as well.
 The project is developing with the power of interpersonal communication on a
globalized outlook.
16. CONCLUSION
Our project is only a humble venture to satisfy the needs to manage their project work.
Several user friendly coding have also adopted. This package shall prove to be a powerful
package in satisfying all the requirements. The objective of software planning is to provide a
frame work that enables the manager to make reasonable estimates made within a limited
time frame at the beginning of the software project and should be updated regularly as the
project progresses.
Food Delivery App
18 .BIBLIOGRAPHY
 www.wikipedia.com
 www.w3school .com
 www.stackoverflow.com
 www.tutorialspoint.com
 www.javapoint.com
 www.youtube.com
 http://php.net/manual/en/function.ucfirst.php
 https://www.w3schools.com/howto/howto_google_fonts.asp
 https://www.iconfinder.com

Mine

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mine

Uploaded by

Copyright:

Available Formats

Food Delivery App

FOOD DELIVERY APP

The Minor Project Report Submitted to

Rajiv Gandhi Proudyogiki Vishwavidyalaya , Bhopal

towards partial fulfillment of the the degree of

Guided by: Submitted by:

Computer Science Engineering Department

MAHAKAL INSTITUTE OF TECHNOLOGY & MANAGEMENT ,

Project Guide, HOD,

MAHAKAL INSTITUTE OF TECHNOLOGY & MANAGEMENT

B.Tech V Semester, Computer Science Engineering department in the year 2023, is

a satisfactory account of their work based on syllabus which is accepted in partial

fulfillment of degree of Bachelor of Technology in Computer Science Engineering.

Internal Examiner External Examiner

MAHAKAL INSTITUTE OF TECHNOLOGY & MANAGEMENT

Date : 22 Nov 2023 ( AMAN PATEL )

Roll no. : 0714CS211010

Roll no. : 0714CS211076

Roll no. : 0714CS211021

MAHAKAL INSTITUTE OF TECHNOLOGY & MANAGEMENT

ANTI PLAGIARISM DECLARATION

 I acknowledge and understand that plagiarism is wrong.

 I understand that my project work must be accurately referenced. I have

 This assignment is my own work, or my group’s own unique group

3. Software Requirement Specification ....................................................... 3

4. System Planning & SDLC……………………………………………...8

5. Constraints of use ................................................................................ 9

8. Entity relationship diagram(ERD)…………………………………….12

9. Data flow diagram (DFD) .................................................................... 12

10. Database designed ............................................................................. 15

11. Unified Modeling Language (UML) Diagram………………………..16

12. Source Codes ..................................................................................... 18

13. Screenshots of application……………………………………………21

14. Aim and Objectives…………………………………………………...23

15. Future Scope of Work..................................................................... 23

16. Conclusion .......................................................................................... 23

In a modern generation Online food ordering is a mobility of food deliveryor takeout

3. SOFTWARE REQUIREMENT SPECIFICATION (SRS)

3.1.2 Document Conventions

RFOS- restaurant Food Ordering System

SRS - Software Requirements Specification

DBMS Database Management System

LAN Local Area Network

TCP Transmission Control Protocol

UDP User Datagram Protocol

IEEE 802.11 Wireless Local Area Network Standard

3.1.3 Intended Audience and Reading Suggestions

3.1.4 Project Scope

C. Larman, APPLYING UML AND PATTERNS An Introduction to Object-Oriented

3.2 Overall Description

3.2.1 Product Perspective

3.2.2 Product Features

3.2.3 User Classes and Characteristics

3.2.4 Operating Environment

3.2.5 Design and Implementation Constraints

3.2.6 User Documentation

3.2.7 Assumptions and Dependencies

3.3. System Features

3.4 External Interface Requirements

3.4.1 User Interfaces

3.4.2 Hardware Interfaces

3.4.3 Software Interfaces