Food Ordering System

Project Report submitted in fulfilment of the requirements

for the award of the degree of

Master of Computer Application

(MCA)
by
Shubhanshu Pandey
Roll No: 2284200206

Under the Guidance of

Mr. Atul Kumar Uttam

Assistant Professor, GLA University, Mathura
.

Department of Computer Engineering &

Applications
Institute of Engineering & Technology

GLA University
Mathura- 281406, INDIA
May, 202 4
 Department of Computer Engineering and Applications
GLA University, Mathura
17km Stone, NH-2, Mathura-Delhi Road, P.O.–Chaumuhan, Mathura–281406(U.P.), India

Declaration

I hereby declare that the work which is being presented in the MCA Project
“Food Ordering System”, in fulfilment of the requirements for the award of
the Master of Computer Applications and submitted to the Department of
Computer Engineering and Applications of GLA University, Mathura, is an
authentic record of my own work carried under the supervision of Mr. Atul
Kumar Uttam, Assistant Professor, GLA University Mathura
The contents of this project report, in full, have not been submitted to
any other Institute or University for the award of any degree.

Sign ______________________
Name of Candidate: Shubhanshu Pandey
University Roll No.: 2284200206
 CERTIFICATE

This is to certify that the above statements made by the candidate are
correct to the best of our knowledge and belief.

External Supervisor
(Mr. Atul Kumar Uttam)
GLA University, Mathura

____________________________ ___________________________
Project Coordinator Head of Department (MCA)
(Mr. Atul Kumar Uttam) (Dr. Shashi Shekhar)
Assistant Professor
Dept. of Computer Eng. & App.

Date:
 CERTIFICATE

This is to certify that Shubhanshu Pandey (2284200206) has

completed the project entitled “Food Ordering System” from
January to April at GLA University , Mathura under my
supervision in partial fulfilment of the requirement for the award of
the degree of Masters of Computer Application (MCA 4 th Semester)
to the best of my knowledge, the same has not been submitted in
any other university for the purpose of pursuing any other
professional degree.

Supervisor
(Mr. Atul Kumar Uttam)
GLA University, Mathura

____________________________ ___________________________
Project Coordinator Head of Department (MCA)
(Mr. Atul Kumar Uttam) (Dr. Shashi Shekhar)
Assistant Professor HOD (Dept. Of CEA)
Dept. of Computer Eng. & App.
Date:

ACKNOWLEDGEMENT
The satisfaction which accompanies the successful completion of the project is
incomplete without the mention of a few names. We take this opportunity to
acknowledge the efforts of the many individuals who helped us to make this
project possible.

Firstly, I would like to express our heartfelt appreciation and gratitude to our
project guide Mr. Atul Kumar Uttam(Assistant Professor, GLA University
Mathura). His vision and execution aimed at creating a structure, definition
and realism around the project and fostered the ideal environment for us to
learn and do. This project is a result of his teaching, encouragement, and
inputs in the numerous meetings she had with us, despite her busy schedule.

I would also like to extend our immense gratitude to respected Head of

Department (MCA) Dr. Shashi Shekhar who allowed us to have an industrial
internship. The experience was a novel one and we would like to thank all the
people, who have lent their valuable time for the completion of the report.

Sign _ ____________________

Name of Candidate: Shubhanshu Pandey

University Roll No.: 2284200206
 Table of Contents
Declaration ..................................................................................................... I
Certificate ...................................................................................................... II
Certificate of Approval ................................................................................... III
Acknowledgement .......................................................................................... IV
List of Figures ................................................................................................ VII
List of Tables .................................................................................................. VIII

1. INTRODUCTION ....................................................................................... 1
Objective .............................................................................................................. 1
Scope .................................................................................................................. 1-2

2. THEORITICAL BACKGROUND .............................................................. 3

3. DEFINITION OF PROBLEM ..................................................................... 4

4. FEASIBILITY STUDY ................................................................................. 5

Technical Feasibility ................................................................................................... 5
Economical Feasibility ................................................................................................ 5
Operational Feasibility ................................................................................................ 6

5. SYSTEM ANALYSIS ................................................................................. 7

Identification of Need .................................................................................................. 8
Preliminary Investigation ............................................................................................ 9

6. SYSTEM DESIGN DOCUMENTATION ................................................... 10

Primary Design Phase .................................................................................................. 10
Secondary Design Phase .............................................................................................. 10

7. METHODOLOGY ADOPTED, SYSTEM IMPLEMENTATION &

DETAILS OF SOFTWARE & HARDWARE USED .................................. 11-
14

8. SCREEN SHOTS .................................................................................... 15-

22

V
9. CODING ................................................................................................. 23-
29

10. TESTING ................................................................................................ 30-36

11. SYSTEM SECURITY & MAINTENANCE ........................................ 37-

38

12. VARIOUS TYPES OF REPORTS/MODULES ..............................................

39

13. FUTURE SCOPE ....................................................................................... 40

14. BIBLIOGRAPHY ........................... ......................................................... 41

VI

LIST OF FIGURES

• Fig 7.1 Methodology Adopted ....................................................................................... 11

• Fig 7.2 Software Details ................................................................................................. 14
• Fig 7.3 Hardware Details ................................................................................................ 14
• Fig 8.1 Home Page ......................................................................................................... 15
• Fig 8.2 Registration Page ............................................................................................... 15
• Fig 8.3 Login Page ......................................................................................................... 16
• Fig 8.4 Restaurants Page ................................................................................................ 16
• Fig 8.5 Add To Cart Page ............................................................................................... 17
• Fig 8.6 User Order Status Page ...................................................................................... 17
• Fig 8.7 Admin Dashboard Page ..................................................................................... 18
• Fig 8.8 User Details ........................................................................................................ 18
• Fig 8.9 Add User Details Form ...................................................................................... 19
• Fig 8.10 All Store Page .................................................................................................. 19
Fig 8.11 Add Category Page .......................................................................................... 20
• Fig 8.12 Add Restaurant Page ........................................................................................ 20
• Fig 8.13 All Menu Page ................................................................................................. 21
• Fig 8.14 Add Menu Page ................................................................................................ 21
• Fig 8.15 All Orders Page ................................................................................................ 22
• Fig 9.1 Index Page .......................................................................................................... 23
• Fig 9.2 Login Page ......................................................................................................... 23
• Fig 9.3 Logout Page ....................................................................................................... 24
• Fig 9.4 Connection Page................................................................................................. 24
• Fig 9.5 Registration Page ............................................................................................... 25
• Fig 9.13 Admin Index Page ............................................................................................ 29
• Fig 9.14 Dashboard Page ................................................................................................ 29

VII

LIST OF TABLES
• Table 8.16 Database Structure at phpMyAdmin ............................................................. 22
• Table 9.6 Admin Table................................................................................................... 25
• Table 9.7 Admin Code Table ......................................................................................... 26
• Table 9.8 Dishes Table ................................................................................................... 26
• Table 9.9 Restaurant Table ............................................................................................. 27
• Table 9.10 Restaurant Category Table ........................................................................... 27
• Table 9.11 Users Table ................................................................................................... 28
• Table 9.12 Users Orders Table ....................................................................................... 28

VIII
 1. OBJECTIVE

The main objective of the Project on Online Food Ordering Management System is to manage
the details of Food Item, Category, Customer, Order, Confirm Order. It manages all the
information about Food Item, Payment, Confirm Order, Food Item. The project is totally built at
administrative end and thus only the administrator is guaranteed the access. The purpose of the
project is to build an application program to reduce the manual work for managing the Food
Item, Category, Payment, Customer. It tracks all the details about the Customer, Order, Confirm
Order.

1.1. SCOPE
It may help collecting perfect management in detail. In a very short time, the collection will be
obvious, simple and sensible. It will help a person to know the management of passed year
perfectly and vividly. It also helps in current all works relative to Online Food Ordering System.
It will be also reduced the cost of collecting the management & collection procedure will go on
smoothly.
Our project aims at Business process automation, i.e. we have tried to computerize various
processes of Online Food Ordering System.

• In computer system the person must fill the various forms & number of copies of the
forms can be easily generated at a time.

• In computer system, it is not necessary to create the manifest, but we can directly print it,
which saves our time.

• To assist the staff in capturing the effort spent on their respective working areas.
• To utilize resources in an efficient manner by increasing their productivity through
automation.
1
• The system generates types of information that can be used for various purposes.
• It satisfies the user requirement.
• Be easy to understand by the user and operator.
• Be easy to operate.
• Have a good user interface.
• Be expandable.

2
2. Theoretical Background
• Provides the searching facilities based on various factors. Such as Food Item, Customer,
Order, Confirm Order
• Online Food Ordering System also manage the Payment details online for Order details,
Confirm Order details, Food Item.
• It tracks all the information of Category, Payment, Order etc.

• Manage the information of Category.

• Shows the information and description of the Food Item, Customer

• To increase efficiency of managing the Food Item, Category.

• It deals with monitoring the information and transactions of Order.

• Manage the information of Food Item.

• Editing, adding and updating of Records is improved which results in proper resource
management of Food Item data.
• Manage the information of Order.

• Integration of all records of Confirm Order.

3
3. Definition of Problem
 • 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.

4
4. Feasibility of Study:
After doing the project Online Food Ordering System, study and analysing 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.

4.1. Economic 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.

4.2. 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 platforms.

5
4.3 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.

6
 5. 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 analysed. 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, analysing, 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

7
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.

5.1. 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.

8
 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), existing system is quite laborious as one must enter same

information at three different places.

5.2. Preliminary Investigation:

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.

9
 6. System Design:
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:

6.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.

6.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.

10
 7. Methodology Adopted and System 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.

Fig.7.1. Methodology Adopted

System Implementation:

1. 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.

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

3. 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.

4. Programming and Testing

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

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

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

12
 8. 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.

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

9. 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.

10. Development Recap

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

11. 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.

13
Software Requirements
Name of component Specification
Operating System Windows 10
Language PHP
Database SQL
Browser Any Mozilla, Opera, Chrome
etc.

Web Technologies HTML, CSS, Bootstrap,

JQuery

Fig.7.2. Software Details

Hardware Requirements

Name of component Specification

Processor Pentium III

630MHz

RAM 128 MB

Hard disk 20 GB

Monitor 15” color monitor

Keyboard 122 keys

1
Fig.7.3. Hardware Details 4
 Screenshot

Fig.8.1 Home Page

Fig.8.2.Registration Page

15
Fig.8.3. Login page

Fig.8.4. Restaurants page

16

fig.8.5. Add to cart page

 Fig.8.6. User order status page

17

Fig.8.7. Admin dashboard page

Fig.8.9. Users details

18

Fig.8.10. Add User details form

Fig.8.11. All store page

19
Fig.8.12. Add Category Page

Fig.8.13.Add Restaurant page

20
Fig.8.13. All Menu page

Fig.8.14. Add menu page

21
 Fig.8.15.All Orders Page

Fig.8.16.Database structure at phpmyadmin

22
8. Coding

10.1 Code for Index.php Page

Fig.9.1. Index page

10.2 Code for Login Page

Fig.9.2. Login Page

23
10.3 Code for Logout Page

Fig.9.3.Logout page

10.4 Code for Connection Page

Fig.9.4. Connection Page

24
10.5 Code for Registration Page

Fig.9.5. RegistrationPage

10.6 SQL Queries for Table creation

Fig.9.6. Admin Table

25
Fig.9.7.Admin Code table

Fig.9.8. Dishes Table

26
Fig.9.9. Restaurant Table

Fig.9.10. Res. Category Table

27
 Fig.9.11.Users Table

Fig.9.12. Users Orders Table

28
 Fig.9.13. Admin index page

Fig.9.14. Dashboard Page

29
 9. TESTING:

.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.

10.1.1 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.

10.1.2 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.
 30

10.1.3 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.

10.1.4 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.

10.1.5 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.

10.1.6 Integration Testing:

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

the top down approach.

10.1.7 Validation Testing:

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

31

10.1.8 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.

10.2 Implementation and Software Specification Testings

10.2.1 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.

10.2.2 Technical Design

This activity builds upon specifications produced during new system design, adding detailed
technical specifications and documentation.
 10.2.3 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.

10.2.4 Programming and Testing

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

32

10.2.5 User Training

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

10.2.6 Acceptance Test

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

10.2.7 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.

10.2.8 System Installation

The process of starting the actual use of a system and training user personnel in its operation.
 10.2.9 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.

10.2.10 Development Recap

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

33

10.2.11 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.

10.3 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.

10.4 The unit testing done included the testing of the following items:
1. Functionality of the entire module/forms.
2. Validations for user input.

Checking of the Coding standards to be maintained during coding.

3. Testing the module with all the possible test data.
4. Testing of the functionality involving all type of calculations etc.
5. Commenting standard in the source files.

34
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.

10.5 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.

10.6 The System Testing done included the testing of the following items:
1. Functionality of the entire system.
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.

36
 10.7 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
long it takes to get a response to an inquiry, make a backup copy of a file, or send a
transmission and get a response.

• Recovery Testing: This testing determines the ability of user to recover data or re-start
system after failure. For example, load backup copy of data and resume processing
without data or integrity loss.

• Procedure Testing: It determines the clarity of documentation on operation and uses of

system by having users do exactly what manuals request. For example, powering down
system at the end of week or responding to paper- out light on printer.

• Human Factors Testing: It determines how users will use the system when processing
data or preparing reports.
10. SYSTEM SECURITY & MAINTENANCE

System maintenance in software engineering is the alteration of a software product after delivery
to correct faults, to improve performance or other attributes.

37
A common approach of maintenance is that it merely involves fixing defects. However, one
study indicated that over 80% of maintenance effort is used for non- corrective actions. This
perception is perpetuated by users submitting difficulty reports that are functionality enhances to
the system.

The key software maintenance problems are both managerial and technical. Key management
problems are alignment with customer priorities, staffing, which organization does maintenance,
estimating costs. Key technical problems are limited understanding, impact analysis, testing,
maintainability measurement.

Software maintenance is a very broad activity that contains error correction.

, enhancements of capabilities, deletion of obsolete capabilities and optimization
. Because change is inevitable, mechanisms must be developed for evaluation, controlling, and
making changes.

An integral part of software is the maintenance one, which needs an accurate maintenance plan
to be prepared during the software development. It should specify how users will appeal
modifications or report issues. The purpose of the maintenance process is to sustain the
capability of a system to give a service.

Security System

Security covers a lot of areas, the most crucial of which is protecting your office systems from
internet born attacks. They can come in many forms, and many.
believe that “hackers” are the primary problem. While hacking certainly exists and its quite
common –many small business networks having hundreds of hack attempts per day that you may
not even know are happening – the more common form of infiltration is from the step of inside
employees. We can examine your systems, deploy protective software, and educate you on the

38
ways that you can protect your business, computers, and data from prying eyes and modern –day
vandals.

39
11. VARIOUS TYPES OF REPORTS / MODULES

Report:

• It generates the report on Food Item, Category, Payment.

• Provide filter reports on Customer, Order, Confirm Order.
• You can easily export PDF for the Food Item, Payment, Order.
• Application also provides excel export for Category, Customer, Confirm Order.

• You can also export the report into csv format for Food Item, Category, Confirm Order.
Modules:
• Food Item Management Module: Used for managing the Food Item details.
• Confirm Order Module: Used for managing the details of Confirm Order.
• Payment Module: Used for managing the details of Payment.
• Category Management Module: Used for managing the information and details of the
Category.

• Customer Module: Used for managing the Customer details.

• Order Module: Used for managing the Order information’s.
• Login Module: Used for managing the login details.
• Users Module: Used for managing the users of the system.

40
12. FUTURE SCOPE

The online food ordering system is one of the most profitable marketing strategies for restaurant
businesses. Online food ordering platforms also prevents missed orders due to busy phone lines
or a lack of resources to monitor the phone. The face of the restaurant industry has shifted from
the traditional dine-in culture to takeaways, online ordering, and home deliveries. Restaurants are
quickly incorporating mobile food ordering apps in their restaurant management systems to
streamline the entire order taking process.
As we all know that food is the basic need in every human life, for which everyone is struggling.
Yet even after their efforts, if people are still not happy with their sustenance, then the effort
given behind it is completely useless. The reasons might be the people are occupied with their
busy schedules, they either can’t be able to cook or not having time to make food and order their
food from outside.

41
13. BIBLIOGRAPHY

UML

https://en.wikipedia.org/wiki/Unified_Modeling_Language

jQuery

https://www.jquery.com/

Bootstrap

https://www.getbootstrap.com/

Google

https://www.google.com/

W3school

https://www.w3school.com/

Unacademy

https://www.unacadamy.com/

YouTube

https://www.youtube.com/

41