1

Online Food Ordering System

(i)
(ii)
(iii)
(iv)
(v)

(vi)
(vii)
(viii)

Title of the Project.

Introduction and Objectives of the Project.
Project Category (RDBMS/OOPS/Networking/Multimedia/Artificial Intelligence/Expert
Systems etc.).
Tools / Platform, Hardware and Software Requirement specifications.
Problem Definition, Requirement Specifications (Detailed functional Requirements
and Technical Specifications) , Project Planning and Scheduling (Gantt chart/PERT
chart).
Scope of the solution.
Analysis (DFDs, ER Diagrams/ Class Diagrams etc. as per the project requirements).
A complete structure which includes:

Number of modules and their description to provide an estimation of the students

effort on the project.

Data Structures as per the project requirements for all the modules.

Process Logic of each module.

Implementation methodology

List of reports that are likely to be generated.

(ix)
(x)
(xi)

Implementation of security mechanisms at various levels

Future scope and further enhancement of the project.
Bibliography

Online Food Ordering System

1.

TITLE OF THE PROJECT

ONLINE FOOD ORDERING SYSTEM

Online Food Ordering System

2. INTRODUCTION AND OBJECTIVE OF PROJECT

In todays age of fast food and take-out, many restaurants have chosen to focus on quick preparation
and speedy delivery of orders rather than offering a rich dining experience.
A fast food restaurant also known as quick service restaurant (QSR) within the food service
industry is a specific type of restaurant characterized both by its fast food cuisine and by minimal
table service.
Food served in fast food restaurants is offered from a limited menu, cooked in bulk in advance and
kept hot, is finished and packaged for order and is usually available ready for pickup or to be
delivered though seating may also be provided.
The customers presently spend an average of 60 minutes per day going to the restaurant, selecting
their meals and paying. Some restaurants have the provision of customers making a call to the
restaurant in advance to order a meal to be ready for them for pick or to be delivered to them. Some
of the customers dont always get the selection they want because the restaurants run out of certain
items or because there is no provision of ordering custom meals.
Purpose of the Project
Its main aim is to simplify and improve the efficiency of the ordering process for both customer and
restaurant.It minimizes manual data entry and ensures data accuracy and security during order
placement process.Customers will also be able to view product menus and there ingredients and be
able to have a visual confirmation that the order was place correctly.To enable customers to order
custom meals that isnt in the menu. To enable customers to have a visual confirmation that the
order was placed correctly. To enable the customers to know about food contents before placing
order. To reduce restaurants food wastage. To ensure correct placement of orders through visual
confirmation. Improve efficiency of restaurants staff. Eliminate paper work and increase level of
accuracy. Increase speed of service, sales volume and customer satisfaction.

Problems in Existing System:

Inconvenience of customer needing to have a physical copy of the menu Time consuming

Online Food Ordering System

Lack of visual confirmation that the order was placed correctly Necessity for restaurant to have an
employee answering the phone and taking orders Difficulty in tracking customers past history
Manual work and consumes large volumes of data Lack of data security
Solutions of these Problems
Security of data. Data are well protected for personal use.
Ensures data accuracy during order placement process
Minimized manual data entry
Greater efficiency since data processing is very fast
User friendly and interactive interface with provision for customer to view menus and have

a visual confirmation that the order was place correctly.

Minimized time requirement during the order placement process
Greatly simplifies the ordering process for both customer and restaurant.

Online Food Ordering System

3. PROJECT CATEGORY
RELATIONAL DATABASE MANAGEMENT SYSTEM
[INTRANET/INTERNET]

Online Food Ordering System

4.TOOLS / PLATFORM, HARDWARE AND SOFTWARE

REQUIREMENT SPECIFICATIONS
Project Title

Online Food Ordering System

Operating system

win xp,7

Front end tool

ASP.NET 2010(CODE BEHIND C#)

Bake end tool

SQL SERVER 2008 R2

Documentation tool

MS World 2010,MS Visio 2013,Edraw max5.0

Presentation tool

MS Power Point

Project tool

Microsoft Visual Studio 2010

Project guide
Submitted by
Submitted to

INDIRA GANDHI NATIONAL OPEN

UNIVERSITY[IGNOU]

Online Food Ordering System

Online Food Ordering System

5.

PROBLEM DEFINITION, REQUIREMENT

SPECIFICATIONS

A functional specification (also, functional spec, specs, functional

specifications document (FSD), functional requirements specification, or
Program specification) in systems engineering and software development is
the documentation that describes the requested behavior of an engineering
system. The documentation typically describes what is needed by the
system user as well as requested properties of inputs and outputs (e.g. of
the software system). A functional specification is the more technical
response to a matching requirements document, e.g. the Product
Requirement Document "PRD". Thus it picks up the results of the
requirements analysis stage. On more complex systems multiple levels of
functional specifications will typically nest to each other, e.g. on the system
level, on the module level and on the level of technical details.
In systems engineering a functional specification is a document that clearly
and accurately describes the essential technical requirements for items,
materials, or services including the procedures by which it can be
determined that the requirements have been met. Specifications help avoid
duplication and inconsistencies, allow for accurate estimates of necessary
work and resources, act as a negotiation and reference document for
engineering changes, provide documentation of configuration, and allow for
consistent communication among those responsible for the eight primary
functions of Systems Engineering. They provide a precise idea of the
problem to be solved so that they can efficiently design the system and
estimate the cost of design alternatives. They provide guidance to testers
for verification (qualification) of each technical requirement. [1]

Online Food Ordering System

A functional specification does not define the inner workings of the

proposed system; it does not include the specification of how the system
function will be implemented. Instead, it focuses on what various outside
agents (people using the program, computer peripherals, or other
computers, for example) might "observe" when interacting with the system.
A typical functional specification might state as follows:
When the user clicks the OK button, the dialog is closed and the focus
is returned to the main window in the state it was in before this dialog
was displayed.
Such a requirement describes an interaction between an external agent
(the user) and the software system. When the user provides input to the
system by clicking the OK button, the program responds (or should
respond) by closing the dialog window containing the OK button.
It can be informal, in which case it can be considered as a blueprint or
user manual from a developer point of view, or formal, in which case it
has a definite meaning defined in mathematical or programmatic terms.
In practice, most successful specifications are written to understand
and fine-tune applications that were already well-developed,
althoughsafety-critical software systems are often carefully specified
prior to application development. Specifications are most important for
external interfaces that must remain stable.

Functional specification topics

Purpose
There are many purposes for functional specifications. One of the
primary purposes on team projects is to achieve some form of team
consensus on what the program is to achieve before making the more
time-consuming effort of writing source code and test cases, followed by
a period of debugging. Typically, such consensus is reached after one or
more reviews by the stakeholders on the project at hand after having
negotiated a cost-effective way to achieve the requirements the software
needs to fulfill.

10

Online Food Ordering System

1. To let the developers know what to build.

2. To let the testers know what tests to run.
3. To let stakeholders know what they are getting.
Process
In the ordered industrial software engineering life-cycle (waterfall
model), functional specification describes what has to be implemented.
The next, Systems architecturedocument describes how the functions
will be realized using a chosen software environment. In non industrial,
prototypical systems development, functional specifications are typically
written after or as part of requirements analysis.
When the team agrees that functional specification consensus is
reached, the functional spec is typically declared "complete" or "signed
off". After this, typically the software development and testing team write
source code and test cases using the functional specification as the
reference. While testing is performed, the behavior of the program is
compared against the expected behavior as defined in the functional
specification.

Methods
One popular method of writing a functional specification document
involves drawing or rendering either simple wireframes or accurate,
graphically designed UI screenshots. After this has been completed, and
the screen examples are approved by all stakeholders, graphical
elements can be numbered and written instructions can be added for
each number on the screen example. For example, a login screen can
have the username field labeled '1' and password field labeled '2,' and
then each number can be declared in writing, for use by software
engineers and later for beta testing purposes to ensure that functionality
is as intended. The benefit of this method is that countless additional
details can be attached to the screen examples.

Examples of functional specifications

11

Online Food Ordering System

Advanced Microcontroller Bus Architecture

Extensible Firmware Interface

Multiboot Specification

Real-time specification for Java

Single UNIX Specification

Types of software development specifications

Bit specification (disambiguation)

Design specification

Diagnostic design specification

Product design specification

Software Requirements Specification

6. SCOPE OF THE SOLUTION