CONTENTS

1. Introduction 5
1.1.Synopsis
1.2.Objectives
1.3.Tools

2. Requirement analysis 12
2.1.System environment
2.2.Preliminary investigation
2.3.Functional Requirement
2.4.System Requirement Specification
2.5.Design

3. Project overview 25
3.1.System Designing
3.2.Code Designing
3.3.Input Designing

4. ER diagram 15
5. Data flow diagram(DFD) 14
6. Php 20
7. HTML 21
8. CSS 22
9. SQL lite 24
10.Testing 33
11.Coding 51
12.Conclusion 52
 ABSTRACT

The purpose of this project is to devlop and online food

ordering system. It is a system that enable customer to place
their food order online at any time at any place. The reason to
devlop this system is due to the issue facing by food industry.
These issue are such as peak hour-long queue issues,
increase of take away than visitors, speed major request of
food management, limited promotion and quality control of food
management. Therefore, this system enhance the speed and
standardization of taking order from the cutomer and supply it
to the staff in the kitchen accordingly. Beside that it provide
user friendly web pages and effective advertising medium to
the new product of the online food ordering restaurant to the
customer at reasonable price.
 ACKNOWLEDGEMENT

I would like to express my sincere gratitude to several individuals and

organization for supporting me throughout the completion of my project.
First, I wish to express my sincere gratitude to my mentor (Mr.
Dharmendra sharma) for her enthusiasm patience, insightful
comments, helpful information, practical advices and unceasing ideas
that have helped me tremendously at all times in my Project and writing
of these thesis. Her immense knowledge, profound experience and
professional expertise in Backend has enabled me to complete this
project successfully. Without her support and guidance, this project
would not have been possible. I am also thankful to our respected HOD
mr. Shashi Pratap Singh and all faculty members for loving inspiration
and timely guidance. I also wish to express my sincere thanks to the
Department of Computer science & Information technology of VIKRANT
UNIVERSITY for accepting this project. Thanks for all your
encouragement!

Ankit yadav(0936CS221021)

Akansha Chauchan(0936CS221009)

Chanchal Kannojiya(0936CS221035)

Durgesh Rana(0936CS221043)
Introduction of the Project Online Food Ordering System:

The "Online Food Ordering System" has been developed to override the problems
prevailing in the practicing manual system. This software is supported to eliminate
and, in some cases, reduce the hardships faced by this existing system. Moreover,
this system is designed for the particular need of the company to carry out
operations in a smooth and effective manner.

The application is reduced as much as possible to avoid errors while entering the
data. It also provides error message while entering invalid data. No formal
knowledge is needed for the user to use this system. Thus, by this all it proves it is
user-friendly. Online Food Ordering System, as described above, can lead to error
free, secure, reliable and fast management system. It can assist the user to
concentrate on their other activities rather to concentrate on the record keeping.
Thus, it will help organization in better utilization of resources.

Every organization, whether big or small, has challenges to overcome and managing
the information of Category, Food Item, Order, Payment, Confirm Order. Every
Online Food Ordering System has different Food Item needs; therefore, we design
exclusive employee management systems that are adapted to your managerial
requirements. This is designed to assist in strategic planning and will help you
ensure that your organization is equipped with the right level of information and
details for your future goals. Also, for those busy executives who are always on the
go, our systems come with remote access features, which will allow you to manage
your workforce anytime, at all times. These systems will ultimately allow you to
better manage resources.
Abstract of the Project Online Food Ordering System:

The purpose of Online Food Ordering System is to automate the existing

manual system by the help of computerized equipment’s and full-fledged computer
software, fulfilling their requirements, so that their valuable data/information can be
stored for a longer period with easy accessing and manipulation of the same. The
required software and hardware are easily available and easy to work with.

Online Food Ordering System, as described above, can lead to error free,
secure, reliable and fast management system. It can assist the user to concentrate
on their other activities rather to concentrate on the record keeping. Thus it will help
organization in better utilization of resources. The organization can maintain
computerized records without redundant entries. That means that one need not be
distracted by information that is not relevant, while being able to reach the
information.

The aim is to automate its existing manual system by the help of

computerized equipment’s and full-fledged computer software, fulfilling their
requirements, so that their valuable data/information can be stored for a longer
period with easy accessing and manipulation of the same. Basically the project

Input Data and Validation of Project on Online Food Ordering System

 All the fields such as Food Item, Customer, Confirm Order are validated and
does not take invalid values
 Each form for Food Item, Category, Payment can not accept blank value fields
 Avoiding errors in data
 Controlling amount of input
 Integration of all the modules/forms in the system.
 Preparation of the test cases.
 Preparation of the possible test data with all the validation checks.
 Actual testing done manually.
 Recording of all the reproduced errors.
 Modifications done for the errors found during testing.
Features of the project Online Food Ordering System:

 Client-Side
 Admin Panel
 Filter Food Items
 Filter Restaurants
 Order Foods
 Add to cart system
 View personal orders
 Restaurant Management
 Food Category Management
 Food Menu Management
 Manage Food Orders
 Cancel Orders
 Customer Management
Software Requirement Specification

The Software Requirements Specification is produced at the culmination of

the analysis task. The function and performance allocated to software as part of
system engineering are refined by establishing a complete information description, a
detailed functional and behavioral description, an indication of performance
requirements and design constraints, appropriate validation criteria, and other data
pertinent to requirements.

The proposed system has the following requirements:

 System needs store information about new entry of Food Item.
 System needs to help the internal staff to keep information of Category and
find them as per various queries.
 System need to maintain quantity record.
 System need to keep the record of Customer.
 System need to update and delete the record.
 System also needs a search area.
 It also needs a security system to prevent data.
Identification of need:

The old manual system was suffering from a series of drawbacks. Since
whole of the system was to be maintained with hands the process of keeping,
maintaining and retrieving the information was very tedious and lengthy. The records
were never used to be in a systematic order. there used to be lots of difficulties in
associating any particular transaction with a particular context. If any information was
to be found it was required to go through the different registers, documents there
would never exist anything like report generation. There would always be
unnecessary consumption of time while entering records and retrieving records. One
more problem was that it was very difficult to find errors while entering the records.
Once the records were entered it was very difficult to update these records.

The reason behind it is that there is lot of information to be maintained and

have to be kept in mind while running the business .For this reason we have
provided features Present system is partially automated (computerized), actually
existing system is quite laborious as one has to enter same information at three
different places.

Following points should be well considered:

 Documents and reports that must be provided by the new system: there can
also be few reports, which can help management in decision-making and cost
controlling, but since these reports do not get required attention, such kind of
reports and information were also identified and given required attention.
 Details of the information needed for each document and report.
 The required frequency and distribution for each document.
 Probable sources of information for each document and report.
 With the implementation of computerized system, the task of keeping records
in an organized manner will be solved. The greatest of all is the retrieval of
information, which will be at the click of the mouse. So the proposed system
helps in saving the time in different operations and making information flow
easy giving valuable reports.
Feasibility Study:
After doing the project Online Food Ordering System, study and analyzing all
the existing or required functionalities of the system, the next task is to do the
feasibility study for the project. All projects are feasible - given unlimited resources
and infinite time.
Feasibility study includes consideration of all the possible ways to provide a solution
to the given problem. The proposed solution should satisfy all the user requirements
and should be flexible enough so that future changes can be easily done based on
the future upcoming requirements.
A. Economical Feasibility
This is a very important aspect to be considered while developing a project.
We decided the technology based on minimum possible cost factor.
 All hardware and software cost has to be borne by the organization.
 Overall we have estimated that the benefits the organization is going to
receive from the proposed system will surely overcome the initial costs and
the later on running cost for system.

B. Technical Feasibility
This included the study of function, performance and constraints that may
affect the ability to achieve an acceptable system. For this feasibility study, we
studied complete functionality to be provided in the system, as described in the
System Requirement Specification (SRS), and checked if everything was possible
using different type of frontend and backend plaformst.

C. Operational Feasibility
No doubt the proposed system is fully GUI based that is very user friendly and
all inputs to be taken all self-explanatory even to a layman. Besides, a proper
training has been conducted to let know the essence of the system to the users so
that they feel comfortable with new system. As far our study is concerned the clients
are comfortable and happy as the system has cut down their loads and doing.
System Design of Online Food Ordering System

In this phase, a logical system is built which fulfils the given requirements. Design
phase of software development deals with transforming the client’s requirements into
a logically working system. Normally, design is performed in the following in the
following two steps:

1. Primary Design Phase:

In this phase, the system is designed at block level. The blocks are created on
the basis of analysis done in the problem identification phase. Different blocks
are created for different functions emphasis is put on minimizing the
information flow between blocks. Thus, all activities which require more
interaction are kept in one block.
2. Secondary Design Phase:
In the secondary phase the detailed design of every block is performed.

The general tasks involved in the design process are the following:

1. Design various blocks for overall system processes.

2. Design smaller, compact and workable modules in each block.
3. Design various database structures.
4. Specify details of programs to achieve desired functionality.
5. Design the form of inputs, and outputs of the system.
6. Perform documentation of the design.
7. System reviews.
User Interface Design

User Interface Design is concerned with the dialogue between a user and the

computer. It is concerned with everything from starting the system or logging into the

system to the eventually presentation of desired inputs and outputs. The overall flow

of screens and messages is called a dialogue

The following steps are various guidelines for User Interface Design:

1. The system user should always be aware of what to do next.

2. The screen should be formatted so that various types of information,

instructions and messages always appear in the same general display area.

3. Message, instructions or information should be displayed long enough to

allow the system user to read them.

4. Use display attributes sparingly.

5. Default values for fields and answers to be entered by the user should be

specified.

6. A user should not be allowed to proceed without correcting an error.

7. The system user should never get an operating system message or fatal

error.
Preliminary Product Description:

The first step in the system development life cycle is the preliminary
investigation to determine the feasibility of the system. The purpose of the
preliminary investigation is to evaluate project requests. It is not a design study nor
does it include the collection of details to describe the business system in all respect.
Rather, it is the collecting of information that helps committee members to evaluate
the merits of the project request and make an informed judgment about the feasibility
of the proposed project.

Analysts working on the preliminary investigation should accomplish the

following objectives:

 Clarify and understand the project request

 Determine the size of the project.
 Assess costs and benefits of alternative approaches.
 Determine the technical and operational feasibility of alternative approaches.
 Report the findings to management, with recommendations outlining the
acceptance or rejection of the proposal.

 Benefit to Organization

The organization will obviously be able to gain benefits such as savings in

operating cost, reduction in paperwork, better utilization of human resources and
more presentable image increasing goodwill.

 The Initial Cost

The initial cost of setting up the system will include the cost of hardware
software (OS, add-on software, utilities) & labor (setup & maintenance). The same
has to bear by the organization.
  Running Cost

Besides, the initial cost the long term cost will include the running cost for the
system including the AMC, stationary charges, cost for human resources, cost for
update/renewal of various related software.

 Need for Training

The users along with the administrator need to be trained at the time of
implementation of the system for smooth running of the system. The client will
provide the training site.

We talked to the management people who were managing a the financial

issues of the center, the staff who were keeping the records in lots of registers and
the reporting manager regarding their existing system, their requirements and their
expectations from the new proposed system. Then, we did the system study of the
entire system based on their requirements and the additional features they wanted to
incorporate in this system.

Reliable, accurate and secure data was also considered to be a complex task
without this proposed system. Because there was no such record for keeping track
of all the activities, which was done by the Online Food Ordering System on the daily
basis.

The new system proposed and then developed by me will ease the task of the
organization in consideration. It will be helpful in generating the required reports by
the staff, which will help them to track their progress and services.

Thus, it will ease the task of Management to a great extent as all the major
activities to be performed, are computerized through this system.
Project Category

Relational Database Management System (RDBMS) : This is an RDBMS based

project which is currently using MySQL for all the transaction statements. MySQL is
an opensource RDBMS System.

Brief Introduction about RDBSM :

A relational database management system (RDBMS) is a database management

system (DBMS) that is based on the relational model as invented by E. F. Codd, of
IBM's San Jose Research Laboratory. Many popular databases currently in use are
based on the relational database model.

RDBMSs have become a predominant choice for the storage of information in new
databases used for financial records, manufacturing and logistical information,
personnel data, and much more since the 1980s. Relational databases have often
replaced legacy hierarchical databases and network databases because they are
easier to understand and use. However, relational databases have been challenged
by object databases, which were introduced in an attempt to address the object-
relational impedance mismatch in relational database, and XML databases.
Implementation Methodology:
Model View Controller or MVC as it is popularly called, is a software design pattern
for developing web applications. A Model View Controller pattern is made up of the
following three parts:
 Model - The lowest level of the pattern which is responsible for maintaining
data.
 View - This is responsible for displaying all or a portion of the data to the user.
 Controller - Software Code that controls the interactions between the Model
and View.
MVC is popular as it isolates the application logic from the user interface layer and
supports separation of concerns. Here the Controller receives all requests for the
application and then works with the Model to prepare any data needed by the View.
The View then uses the data prepared by the Controller to generate a final
presentable response. The MVC abstraction can be graphically represented as
follows.
MVC (Model View Controller Flow) Diagram

DATA FLOW DIAGRAMS

Project Planning:

Software project plan can be viewed as the following:

1) Within the organization: How the project is to be implemented? What are

various constraints (time, cost, staff)? What is market strategy?

2) With respect to the customer: Weekly or timely meetings with the customer
with presentation on status reports. Customers feedback is also taken and
further modification and developments are done. Project milestones and
deliverables are also presented to the customer.

For a successful software project, the following steps can be followed:

 Select a project

o Identifying project’s aims and objectives

o Understanding requirements and specification

o Methods of analysis, design and implementation

o Testing techniques

o Documentation

 Project milestones and deliverables

 Budget allocation

o Exceeding limits within control

 Project Estimates

o Cost

o Time

o Size of code

o Duration

 Resource Allocation
 o Hardware

o Software

o Previous relevant project information

o Digital Library

 Risk Management

o Risk avoidance

o Risk detection

PHP

PHP (Hypertext Preprocessor) is a popular server-side scripting language primarily

used for web development. It's embedded into HTML to create dynamic web pages.
Unlike client-side languages like JavaScript, PHP runs on the server, meaning it
generates the HTML that gets sent to the user's browser.

Here are some key points about PHP:

1. Server-Side: PHP scripts are executed on the server, not in the browser. This
makes it ideal for generating dynamic content based on user input, interacting
with databases, and handling sessions or cookies.

2. Embedded in HTML: PHP code is usually embedded within HTML using <?
php ….?> tags. This allows you to easily mix PHP with HTML to generate
content dynamically.

3. Database Interaction: PHP is widely used to interact with databases, most

commonly MySQL. It can retrieve, insert, and update data in a database and
use that data to generate dynamic web pages.

4. Open-Source: PHP is free to use and open-source, with a large community

that contributes to its development. It's supported by many hosting providers.

5. Wide Usage: Many popular websites and platforms, like WordPress and
Facebook (early on), use PHP to power their backends.
 6. Frameworks: There are many PHP frameworks, such as Laravel, Symfony,
and CodeIgniter, that make development faster by providing reusable
components and best practices.

HTML

HTML or Hyper Text Markup Language is the standard markup language used to create
web pages.

HTML was created in 1991 by Tim Berners-Lee at CERN in Switzerland. It was designed to
allow scientists to display and share their research.

HTML is written in the form of HTML elements consisting of tags enclosed in angle brackets
(like <html>). HTML tags most commonly come in pairs like <h1> and </h1>, although
some tags represent empty elements and so are unpaired, for example <img>. The first tag in
a pair is the start tag, and the second tag is the end tag (they are also called opening tags and
closing tags).

The purpose of a web browser is to read HTML documents and compose them into visible or
audible web pages. The browser does not display the HTML tags, but uses the tags to
interpret the content of the page. HTML describes the structure of a website semantically
along with cues for presentation, making it a markup language rather than a programming
language.

HTML elements form the building blocks of all websites. HTML allows images and objects
to be embedded and can be used to create interactive forms. It provides a means to create
structured documents by denoting structural semantics for text such as headings, paragraphs,
lists, links, quotes and other items. It can embed scripts written in languages such as Java
Script which affect the behavior of HTML web pages.

HTML is descriptive markup language. Library of various markup languages is defined in

various browsers.
HTML 5

HTML5 will be the new standard for HTML. The previous version of HTML, HTML 4.01,
came in 1999. The web has changed a lot since then. HTML5 is still a work in progress.
However, the major browsers support many of the new HTML5 elements and APIs.
HTML5 is cooperation between the World Wide Web Consortium (W3C) and the Web
Hypertext Application Technology Working Group (WHATWG).

WHATWG was working with web forms and applications, and W3C was working with
XHTML 2.0. In 2006, they decided to cooperate and create a new version of HTML.
Some rules for HTML5 were established:
a) New features should be based on HTML, CSS, DOM, and JavaScript
b) Reduce the need for external plug-ins (like Flash)
c) Better error handling
d) More markup to replace scripting
e) HTML5 should be device independent
f) The development process should be visible to the public

Cascading Style Sheets (CSS) is a style sheet language used for describing the look and
formatting of a document written in a markup language. While most often used to style web
pages and user interfaces written in HTML and XHTML, the language can be applied to any
kind of XML document, including plain XML, SVG and XUL. CSS is a cornerstone
specification of the web and almost all web pages use CSS style sheets to describe their
presentation.

CSS can also allow the same markup page to be presented in different styles for different
rendering methods, such as on-screen, in print, by voice (when read out by a speech-based
browser or screen reader) and on Braille-based, tactile devices. It can also be used to allow
the web page to display differently depending on the screen size or device on which it is
being viewed. While the author of a document typically links that document to a CSS file,
readers can use a different style sheet, perhaps one on their own computer, to override the one
the author has specified.
Cost estimation of the project:

Software cost comprises a small percentage of overall computer-based system cost.

There are a number of factors, which are considered, that can affect the ultimate
cost of the software such as - human, technical, Hardware and Software availability
etc.

The main point that was considered during the cost estimation of project was its
sizing. In spite of complete software sizing, function point and approximate lines of
code were also used to "size" each element of the Software and their costing.

The cost estimation done by me for Project also depend upon the baseline metrics
collected from past projects and these were used in conjunction with estimation
variables to develop cost and effort projections.

We have basically estimated this project mainly on two bases -

1) Effort Estimation - This refers to the total man-hours required for the
development of the project. It even includes the time required for doing
documentation and user manual.

2) Hardware Required Estimation - This includes the cost of the PCs and the
hardware cost required for development of this project.
Tools/Platform, Hardware and Software Requirement specifications:

Software Requirements:

Name of component Specification

Operating System Windows11, Windows XP, Windows7,
Linux
Language php
Database SQL lite Server
Browser Any of Mozilla, Opera, Chrome etc.

Web Technologies Html, CSS, JavaScript, php

Hardware Requirements:

Name of component Specification

Processor Pentium III 630MHz
RAM 128 MB
Hard disk 20 GB
Monitor 15” color monitor
Keyboard 122 keys
Project Profile

There has been continuous effort to develop tools, which can ease the
process of software development. But, with the evolving trend of different
programming paradigms today’s software developers are really challenged to deal
with the changing technology. Among other issues, software re-engineering is being
regarded as an important process in the software development industry. One of the
major tasks here is to understand software systems that are already developed and
to transform them to a different software environment. Generally, this requires a lot
of manual effort in going through a program that might have been developed by
another programmer. This project makes a novel attempt to address the issued of
program analysis and generation of diagrams, which can depict the structure of a
program in a better way. Today, UML is being considered as an industrial standard
for software engineering design process. It essential provides several diagramming
tools that can express different aspects/ characteristics of program such as

Use cases: Elicit requirement from users in meaningful chunks. Construction

planning is built around delivering some use cases n each interaction basis for
system testing.

Class diagrams: shows static structure of concepts, types and class. Concepts how
users think about the world; type shows interfaces of software components; classes
shows implementation of software components.

Interaction diagrams: shows how several objects collaborate in single use case.

Package diagram: show group of classes and dependencies among them.

State diagram: show how single object behaves across many use cases.

Activity diagram: shows behavior with control structure. Can show many objects
over many uses, many object in single use case, or implementations methods
encourage parallel behavior, etc.
 The end-product of this project is a comprehensive tool that can parse any
vb.net program and extract most of the object oriented features inherent in the
program such as polymorphism, inheritance, encapsulation and abstraction.

What is UML?

UML stands for Unified Modeling Language is the successor to the wave of
Object Oriented Analysis and Design (OOA&D) methods that appeared in the late
80’s. It most directly unifies the methods of Booch, Rumbaugh (OMT) and Jacobson.
The UML is called a modeling language, not a method. Most methods consist at
least in principle, of both a modeling language and a process. The Modeling
language is that notation that methods used to express design.

Notations and meta-models:

The notation is the graphical stuff; it is the syntax of the modeling language. For
instance, class diagram notation defines how items are concepts such as class,
association, and multiplicity is represented. These are:

Class Diagram: The class diagram technique has become truly central within object-
oriented methods. Virtually every method has included some variation on this
technique. Class diagram is also subject to the greatest range of modeling concept.
Although the basic elements are needed by everyone, advanced concepts are used
less often. A class diagram describes the types of objects in the system and the
various kinds of static relationship that exist among them. There are two principal
kinds of static relationship:

 Association
 Subtype
Class diagram also show the attributes and operations of a class and the constraints
that apply to the way objects are connected.
Association: Association represent between instances of class. From the
conceptual perspective, association represents conceptual relations between
classes. Each association has two roles. Each role is a direction on the association.
A role also has multiplicity, which is a indication of how many object may participate
in the given relationship.

Generalization: A typical example of generalization evolves the personal and

corporate customer of a business. They have differences but also many similarity.
The similarities can be placed in generalization with personal customer and
corporate customer sub type.

Aggregation: aggregation is the part of relationship. It is like saying a car has

engine and wheels as its parts. This sounds good, but difficult thing is considering,
what is the difference is aggregation and association.

Interaction: interaction diagrams are models that describes how groups of objects
collaboration in some behavior.

Typically, an interaction diagram captures the behavior a single use cases.

The diagram shows a number of example objects and the messages that are passed
between these objects in use cases. These are following approaches with simple
use case that exhibits the following behavior.

Objects can send a message to another. Each message is checks with given
stock item. There are two diagrams: Sequence and Collaboration diagram.

Package Diagram: One of the oldest questions in software methods is: how do you
break down a large system into smaller systems? It becomes difficult to understand
and the changes we make to them.

Structured methods used functional decomposition in which the overall

system was mapped as a function broken down into sub function, which is further
broken down into sub function and so forth. The separation of process data is gone,
functional decomposition is gone, but the old question is still remains. One idea is to
group the classes together into higher-level unit. This idea, applied very loosely,
appears in many objects. In UML, this grouping mechanism is package. The term
package diagram for a diagram that shows packages of classes and the
dependencies among them.

A dependency exists between two elements if changes to the definition of one

element may cause to other. With classes, dependencies exist for various reasons:
one class sends a message to another; one class has another as part of its data;
one class mentions another as a parameter to an operation. A dependency between
two packages exists; and any dependencies exist between any two classes in the
package.

State diagram: State diagram are a familiar technique to describe the behavior of a
system. They describe all the possible states a particular object can get into and how
the objects state changes as a result of events that reach the objects. In most OO
technique, state diagrams are drawn for a single class to show the lifetime behavior
of a singe object. There are many form of state diagram, each with slightly different
semantics. The most popular one used in OO technique is based on David Harel’s
state chart.
GANTT CHART

It is also known as Bar chart is used exclusively for scheduling purpose. It is a

project controlling technique. It is used for scheduling. Budgeting and resourcing
planning. A Gantt is a bar chart with each bar representing activity. The bars are
drawn against a time line. The length of time planned for the activity. The Gantt
chart in the figure shows the Gray parts is slack time that is the latest by which a
task has been finished.

Specification

Design Database Part

Design GUI Modulation

Part
CODE DATABASE
PART

CODE GUI BLACK BOX

TESTING

PART
INTEGRATE AND TEST

IMPLEMENTATION

WRITE USER MANUAL

GANTT CHART REPRESENTATION

Use Case Model of the Project:

The use case model for any system consists of “use cases”. Use cases
represent different ways in which the system can be used by the user. A simple way
to find all the use case of a system is to ask the questions “What the user can do
using the system?” The use cases partition the system behavior into transactions
such that each transaction performs some useful action from the users’ point of view.

The purpose of the use case to define a piece of coherent behavior without
reveling the internal structure of the system. An use case typically represents a
sequence of interaction between the user and the system. These interactions
consists of one main line sequence is represent the normal interaction between the
user and the system. The use case model is an important analysis and design
artifact (task).Use cases can be represented by drawing a use case diagram and
writing an accompany text elaborating the drawing.

In the use case diagram each use case is represented by an ellipse with the
name of use case written inside the ellipse. All the ellipses of the system are
enclosed with in a rectangle which represents the system boundary. The name of the
system being moduled appears inside the rectangle. The different users of the
system are represented by using stick person icon. The stick person icon is normally
referred to as an Actor. The line connecting the actor and the use cases is called the
communication relationship. When a stick person icon represents an external system
it is annotated by the stereo type<<external system>>.
Dataflow Diagram:

Data flow diagram is the starting point of the design phase that functionally
decomposes the requirements specification. A DFD consists of a series of bubbles
joined by lines. The bubbles represent data transformation and the lines represent
data flows in the system. A DFD describes what data flow rather than how they are
processed, so it does not hardware, software and data structure.

A data-flow diagram (DFD) is a graphical representation of the "flow" of

data through an information system. DFDs can also be used for the visualization of
data processing (structured design). A data flow diagram (DFD) is a significant
modeling technique for analyzing and constructing information processes. DFD
literally means an illustration that explains the course or movement of information
in a process. DFD illustrates this flow of information in a process based on the
inputs and outputs. A DFD can be referred to as a Process Model.

The data flow diagram is a graphical description of a system’s data and how to

Process transform the data is known as Data Flow Diagram (DFD).

Unlike details flow chart, DFDs don’t supply detail descriptions of modules that
graphically describe a system’s data and how the data interact with the system. Data
flow diagram number of symbols and the following symbols are of by DeMarco.
Erdiagram:
There are seven rules for construct a data flow diagram.

i) Arrows should not cross each other.

ii) Squares, circles and files must wears names.
iii) Decomposed data flows must be balanced.
iv) No two data flows, squares or circles can be the same names.
v) Draw all data flows around the outside of the diagram.
vi) Choose meaningful names for data flows, processes & data stores.
vii) Control information such as record units, password and validation
requirements are not penitent to a data flow diagram.

Additionally, a DFD can be utilized to visualize data processing or a structured

design.

This basic DFD can be then disintegrated to a lower level diagram demonstrating
smaller steps exhibiting details of the system that is being modeled.

On a DFD, data items flow from an external data source or an internal data store to
an internal data store or an external data sink, via an internal process. It is common
practice to draw a context-level data flow diagram first, which shows the interaction
between the system and external agents, which act as data sources and data sinks.
On the context diagram (also known as the Level 0 DFD’), the system's interactions
with the outside world are modeled purely in terms of data flows across the system
boundary. The context diagram shows the entire system as a single process, and
gives no clues as to its internal organization.

This context-level DFD is next "exploded", to produce a Level 1 DFD that shows
some of the detail of the system being modeled. The Level 1 DFD shows how the
system is divided into sub-systems (processes), each of which deals with one or
more of the data flows to or from an external agent, and which together provide all
of the functionality of the system as a whole. The level 1 DFD is further spreaded
and split into more descriptive and detailed description about the project as level 2
DFD.The level 2 DFD can be a number of data flows which will finally show the
entire description of the software project.
About ER Diagram:

Entity Relationship Diagram

E-R Model is a popular high level conceptual data model. This model and its
variations are frequently used for the conceptual design of database application and
many database design tools employ its concept.

A database that confirms to an E-R diagram can be represented by a collecton of

tables in the relational system. The mapping of E-R diagram to the entities are:

 Attributes

 Relations

o Many-to-many

o Many-to-one

o One-to-many

o One-to-one

 Weak entities

 Sub-type and super-type

The entities and their relationshops between them are shown using the following
conventions.

 An entity is shown in rectangle.

 A diamond represent the relationship among number of entities.

 The attributes shown as ovals are connected to the entities or relationship

by lines.

 Diamond,oval and relationships are labeled.

 Model is an abstraction process that hides super details while
highlighting details relation to application at end.
 A data model is a mechanism that provides this abstraction for
database application.
 Data modeling is used for representing entities and their relationship in
the database.
 Entities are the basic units used in modeling database entities can
have concrete existence or constitute ideas or concepts.
 Entity type or entity set is a group of similar objects concern to an
organization for which it maintain data,
 Properties are characteristics of an entity also called as attributes.
 A key is a single attribute or combination of 2 or more attributes of an
entity set is used to identify one or more instances of the set.
 In relational model we represent the entity by a relation and use tuples
to represent an instance of the entity.
 Relationship is used in data modeling to represent in association
between an entity set.
 An association between two attributes indicates that the values of the
associated attributes are independent.
Security Testing of the Project

Testing is vital for the success of any software. no system design is ever perfect. Testing is
also carried in two phases. first phase is during the software engineering that is during the
module creation. second phase is after the completion of software. this is system testing
which verifies that the whole set of programs hanged together.

White Box Testing:

In this technique, the close examination of the logical parts through the software are tested
by cases that exercise species sets of conditions or loops. all logical parts of the software
checked once. errors that can be corrected using this technique are typographical errors,
logical expressions which should be executed once may be getting executed more than
once and error resulting by using wrong controls and loops. When the box testing tests all
the independent part within a module a logical decisions on their true and the false side are
exercised , all loops and bounds within their operational bounds were exercised and internal
data structure to ensure their validity were exercised once.

Black Box Testing:

This method enables the software engineer to device sets of input techniques that fully
exercise all functional requirements for a program. black box testing tests the input, the
output and the external data. it checks whether the input data is correct and whether we are
getting the desired output.

Alpha Testing:

Acceptance testing is also sometimes called alpha testing. Be spoke systems are developed
for a single customer. The alpha testing proceeds until the system developer and the
customer agree that the provided system is an acceptable implementation of the system
requirements.

Beta Testing:

On the other hand, when a system isto be marked as a software product, another process
called beta testing is often conducted. During beta testing, a system is delivered among a
number of potential users who agree to use it. The customers then report problems to the
developers. This provides the product for real use and detects errors which may not have
been anticipated by the system developers.

Unit Testing:

Each module is considered independently. it focuses on each unit of software as

implemented in the source code. it is white box testing.

Integration Testing:

Integration testing aims at constructing the program structure while at the same constructing
tests to uncover errors associated with interfacing the modules. modules are integrated by
using the top down approach.

Validation Testing:

Validation testing was performed to ensure that all the functional and performance
requirements are met.

System Testing:

It is executing programs to check logical changes made in it with intention of finding errors. a
system is tested for online response, volume of transaction, recovery from failure etc.
System testing is done to ensure that the system satisfies all the user requirements.
Implementation and Software Specification Testings

Detailed Design of Implementation

This phase of the systems development life cycle refines hardware and software
specifications, establishes programming plans, trains users and implements extensive
testing procedures, to evaluate design and operating specifications and/or provide the basis
for further modification.

Technical Design

This activity builds upon specifications produced during new system design, adding detailed
technical specifications and documentation.

Test Specifications and Planning

This activity prepares detailed test specifications for individual modules and programs, job
streams, subsystems, and for the system as a whole.

Programming and Testing

This activity encompasses actual development, writing, and testing of program units or
modules.

User Training

This activity encompasses writing user procedure manuals, preparation of user training
materials, conducting training programs, and testing procedures.

Acceptance Test

A final procedural review to demonstrate a system and secure user approval before a
system becomes operational.

Installation Phase

In this phase the new Computerized system is installed, the conversion to new procedures is
fully implemented, and the potential of the new system is explored.
System Installation

The process of starting the actual use of a system and training user personnel in its
operation.

Review Phase

This phase evaluates the successes and failures during a systems development project, and
to measure the results of a new Computerized Transystem in terms of benefits and savings
projected at the start of the project.

Development Recap

A review of a project immediately after completion to find successes and potential problems
in future work.

Post-Implementation Review

A review, conducted after a new system has been in operation for some time, to evaluate
actual system performance against original expectations and projections for cost-benefit
improvements. Also identifies maintenance projects to enhance or improve the system.

THE STEPS IN THE SOFTWARE TESTING

The steps involved during Unit testing are as follows:

a. Preparation of the test cases.

b. Preparation of the possible test data with all the validation checks.
c. Complete code review of the module.
d. Actual testing done manually.
e. Modifications done for the errors found during testing.
f. Prepared the test result scripts.

The unit testing done included the testing of the following items:

1. Functionality of the entire module/forms.

2. Validations for user input.
3. Checking of the Coding standards to be maintained during coding.
4. Testing the module with all the possible test data.
5. Testing of the functionality involving all type of calculations etc.
6. Commenting standard in the source files.

After completing the Unit testing of all the modules, the whole system is integrated with all its
dependencies in that module. While System Integration, We integrated the modules one by
one and tested the system at each step. This helped in reduction of errors at the time of the
system testing.

The steps involved during System testing are as follows:

 Integration of all the modules/forms in the system.

 Preparation of the test cases.
 Preparation of the possible test data with all the validation checks.
 Actual testing done manually.
 Recording of all the reproduced errors.
 Modifications done for the errors found during testing.
 Prepared the test result scripts after rectification of the errors.

The System Testing done included the testing of the following items:

1. Functionality of the entire system as a whole.

2. User Interface of the system.
3. Testing the dependent modules together with all the possible test data scripts.
4. Verification and Validation testing.
5. Testing the reports with all its functionality.

After the completion of system testing, the next following phase was the Acceptance Testing.
Clients at their end did this and accepted the system with appreciation. Thus, we reached
the final phase of the project delivery.

There are other six tests, which fall under special category. They are described below:

 Peak Load Test: It determines whether the system will handle the volume of activities that
occur when the system is at the peak of its processing demand. For example, test the
system by activating all terminals at the same time.
 Storage Testing: It determines the capacity of the system to store transaction data on a
disk or in other files.
 Performance Time Testing: it determines the length of time system used by the system to
process transaction data. This test is conducted prior to implementation to determine how
System Analysis:

System analysis is a process of gathering and interpreting facts, diagnosing

problems and the information about the Online Food Ordering System to recommend
improvements on the system. It is a problem solving activity that requires intensive
communication between the system users and system developers. System analysis
or study is an important phase of any system development process. The system is
studied to the minutest detail and analyzed. The system analyst plays the role of the
interrogator and dwells deep into the working of the present system. The system is
viewed as a whole and the input to the system are identified. The outputs from the
organizations are traced to the various processes. System analysis is concerned
with becoming aware of the problem, identifying the relevant and decisional
variables, analyzing and synthesizing the various factors and determining an optimal
or at least a satisfactory solution or program of action. A detailed study of the
process must be made by various techniques like interviews, questionnaires etc. The
data collected by these sources must be scrutinized to arrive to a conclusion. The
conclusion is an understanding of how the system functions. This system is called
the existing system. Now the existing system is subjected to close study and
problem areas are identified. The designer now functions as a problem solver and
tries to sort out the difficulties that the enterprise faces. The solutions are given as
proposals. The proposal is then weighed with the existing system analytically and the
best one is selected. The proposal is presented to the user for an endorsement by
the user. The proposal is reviewed on user request and suitable changes are made.
This is loop that ends as soon as the user is satisfied with proposal. Preliminary
study is the process of gathering and interpreting facts, using the information for
further studies on the system. Preliminary study is problem solving activity that
requires intensive communication between the system users and system developers.
It does various feasibility studies. In these studies a rough figure of the system
activities can be obtained, from which the decision about the strategies to be
followed for effective system study and analysis can be taken.

defines each data term encountered during the analysis and design of a new system.
Data elements can describe files or the processes.
Screenshot of the Project
Online Food Ordering
System
 Code of the Project
Online Food Ordering
System
Php connection code:
<?php

include("connection/connect.php");

error_reporting(0);

session_start();

if(isset($_POST['submit']))

$username = $_POST['username'];

$password = $_POST['password'];

if(!empty($_POST["submit"]))

$loginquery ="SELECT * FROM users WHERE username='$username' &&

password='".md5($password)."'"; //selecting matching records

$result=mysqli_query($db, $loginquery); //executing

$row=mysqli_fetch_array($result);

if(is_array($row))

$_SESSION["user_id"] = $row['u_id'];

header("refresh:1;url=index.php");

else

$message = "Invalid Username or Password!";

?>
Login Code:
<?php

session_start();

session_destroy();

$url = 'login.php';

header('Location: ' . $url);

?>

<header id="header" class="header-scroll top-header headrom">

<nav class="navbar navbar-dark">

<div class="container">

<button class="navbar-toggler hidden-lg-up" type="button" data-toggle="collapse" data-

target="#mainNavbarCollapse">&#9776;</button>

<a class="navbar-brand" href="index.php"> <img class="img-rounded" src="images/icn.png"

alt=""> </a>

<div class="collapse navbar-toggleable-md float-lg-right" id="mainNavbarCollapse">

<ul class="nav navbar-nav">

<li class="nav-item"> <a class="nav-link active" href="index.php">Home <span

class="sr-only">(current)</span></a> </li>

<li class="nav-item"> <a class="nav-link active" href="restaurants.php">Restaurants

<span class="sr-only"></span></a> </li>

Logout code:
<?php

if(empty($_SESSION["user_id"]))

echo '<li class="nav-item"><a

href="login.php" class="nav-link active">Login</a> </li>

<li class="nav-item"><a
href="registration.php" class="nav-link active">Register</a> </li>';

else
 {

echo '<li class="nav-

item"><a href="your_orders.php" class="nav-link active">My Orders</a> </li>';

echo '<li class="nav-

item"><a href="logout.php" class="nav-link active">Logout</a> </li>';

?>

</ul>

</div>

</div>

Database connection code:

<?php

//main connection file for both admin & front end

$servername = "localhost"; //server

$username = "u390119634_onlinefood"; //username

$password = "Ankit@8966"; //password

$dbname = "u390119634_onlinefood"; //database

// Create connection

$db = mysqli_connect($servername, $username, $password, $dbname); // connecting

// Check connection

if (!$db) { //checking connection to DB

die("Connection failed: " . mysqli_connect_error());

?>
 Sql query Code

-- phpMyAdmin SQL Dump

-- version 4.6.5.2

-- https://www.phpmyadmin.net/

--

-- Host: 127.0.0.1

-- Generation Time: May 27, 2022 at 03:22 PM

-- Server version: 5.6.21

-- PHP Version: 5.6.3

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

SET time_zone = "+00:00";

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;

/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;

/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;

/*!40101 SET NAMES utf8mb4 */;

--

-- Database: `onlinefoodphp`

--

-- --------------------------------------------------------

--
-- Table structure for table `admin`

--

CREATE TABLE `admin` (

`adm_id` int(222) NOT NULL,

`username` varchar(222) NOT NULL,

`password` varchar(222) NOT NULL,

`email` varchar(222) NOT NULL,

`code` varchar(222) NOT NULL,

`date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

-- Dumping data for table `admin`

--

INSERT INTO `admin` (`adm_id`, `username`, `password`, `email`, `code`, `date`) VALUES

(1, 'admin', 'CAC29D7A34687EB14B37068EE4708E7B', 'admin@mail.com', '', '2022-05-27 13:21:52');

-- --------------------------------------------------------

--

-- Table structure for table `dishes`

--

CREATE TABLE `dishes` (

`d_id` int(222) NOT NULL,

`rs_id` int(222) NOT NULL,

`title` varchar(222) NOT NULL,

`slogan` varchar(222) NOT NULL,

`price` decimal(10,2) NOT NULL,

`img` varchar(222) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

-- Dumping data for table `dishes`

--

INSERT INTO `dishes` (`d_id`, `rs_id`, `title`, `slogan`, `price`, `img`) VALUES

(1, 1, 'Yorkshire Lamb Patties', 'Lamb patties which melt in your mouth, and are quick and easy to make.
Served hot with a crisp salad.', '14.00', '62908867a48e4.jpg'),

-- Table structure for table `remark`

CREATE TABLE `remark` (

`id` int(11) NOT NULL,

`frm_id` int(11) NOT NULL,

`status` varchar(255) NOT NULL,

`remark` mediumtext NOT NULL,

`remarkDate` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

-- Dumping data for table `remark`

--

INSERT INTO `remark` (`id`, `frm_id`, `status`, `remark`, `remarkDate`) VALUES

(1, 2, 'in process', 'none', '2022-05-01 05:17:49'),

-- Indexes for table `admin`

--

ALTER TABLE `admin`

ADD PRIMARY KEY (`adm_id`);

--

-- Indexes for table `dishes`

--
ALTER TABLE `dishes`

ADD PRIMARY KEY (`d_id`);

--

-- Indexes for table `remark`

--

ALTER TABLE `remark`

ADD PRIMARY KEY (`id`);

--

-- Indexes for table `restaurant`

--

ALTER TABLE `restaurant`

ADD PRIMARY KEY (`rs_id`);

--

-- Indexes for table `res_category`

--

ALTER TABLE `res_category`

ADD PRIMARY KEY (`c_id`);

--

-- Indexes for table `users`

--

ALTER TABLE `users`

ADD PRIMARY KEY (`u_id`);

--

-- Indexes for table `users_orders`

--

ALTER TABLE `users_orders`

ADD PRIMARY KEY (`o_id`);

--

-- AUTO_INCREMENT for dumped tables

--

--

-- AUTO_INCREMENT for table `admin`

--

ALTER TABLE `admin`

MODIFY `adm_id` int(222) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

--

-- AUTO_INCREMENT for table `dishes`

--

ALTER TABLE `dishes`

MODIFY `d_id` int(222) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=17;

--

-- AUTO_INCREMENT for table `remark`

--

ALTER TABLE `remark`

MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=13;

--

-- AUTO_INCREMENT for table `restaurant`

--

ALTER TABLE `restaurant`

MODIFY `rs_id` int(222) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;

--

-- AUTO_INCREMENT for table `res_category`

--

ALTER TABLE `res_category`

MODIFY `c_id` int(222) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;

--

-- AUTO_INCREMENT for table `users`

--

ALTER TABLE `users`

MODIFY `u_id` int(222) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=7;

--

-- AUTO_INCREMENT for table `users_orders`

--

ALTER TABLE `users_orders`

MODIFY `o_id` int(222) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=10;

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;

/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

 CONCLUSION

RESTRO (Food ordering System) has been computed

successfully and was also tested successfully by taking
"Test Cases". It is user friendly, and has required options,
which can be utilized by the user to perform the desired
operations. Food ordering System is developed using
HTML, CSS, JS as front end and PHP, MySQL as back end
on windows environment. The goals that are achieved by
the software are: • User friendly • Simplification of the
operations • Portable and flexible for further enhancement
• Less processing time and getting required information