ACS COLLEGE OF
ENGINEERING
DATABASE MANAGEMENT
SYSTEM REVIEW
BY
MONISH.M
SYED SUFIYAN
PRAJWAL.C
TITLE OF THE
PROJECT:
Online Food Ordering
System
AGENDA
➢ Project Introduction
➢ Literature Survey
➢ Methodology and Technologies Used
➢ Initial Implementation and Progress
➢ Work Plan and Timeline
➢ Expected Outcome
PROBLEM STATEMENT:
• The traditional method of ordering food, which relies
heavily on physical interaction between customers and
restaurants, is inefficient, time-consuming, and prone to
errors. Customers face challenges such as long waiting
times, miscommunication during order placement, and lack
of transparency in order tracking.
• From the restaurant's perspective, manual order
management leads to difficulties in handling large volumes of
orders, maintaining accurate records, and minimizing errors.
This results in decreased customer satisfaction and
operational inefficiencies.
MOTIVATION BEHIND CHOOSING THE PROJECT:
• Growing Demand for Online Services
• Convenience and Efficiency
• Customer-Centric Solution
• Scalability and Future Potential
• Encouraging Digital Transformation
• Learning Opportunity
• Real-World Application
OBJECTIVE AND SCOPE:
• Objective:To develop an Online Food Ordering System that simplifies the
food ordering process by providing a digital platform for customers and
restaurants. The system aims to enhance user experience, automate order
management, ensure secure data handling, and enable real-time updates.
• Scope:-
• Customer Module: Browse menus, place orders, track delivery, and pay
online.
• Restaurant Module: Manage menus, process orders, and monitor sales.
• Admin Module: Oversee user accounts, maintain system operations, and
ensure data integrity.
• Database Management: Securely store and manage customer, order, and
payment data.
• Future Extensions: Support for delivery integrations, personalized
recommendations, and global scalability.
LITERATURE SURVEY:
Existing Solutions:Many online food ordering systems already exist, such as
Zomato,Swiggy,Uber Eats, and smaller college-level DBMS projects. These
systems generally include features like:
• User registration and login
• Menu browsing and order placement
• Online payment
• Delivery tracking
• Restaurant management dashboards
Limitations of Existing Solutions:
• Poor Database Design in Student Projects
• Lack of Role-Based Access
• No Real-Time Reporting or Analytics
• No Scalability Planning
RESEARCH PAPERS AND REFERENCES REVIEWED :
• In existing research and online food ordering systems, many use
basic or poorly designed databases. These systems often face
issues like:
• Data duplication and inconsistency.
• Lack of relationship between entities (like users, orders, and
restaurants).
• Poor handling of concurrent transactions (when multiple users
place orders at the same time).
• Limited features for generating useful reports.
How Our Project is Different or Better :
• Better database design:
We create a clean and organized database that avoids repeating data and keeps
everything connected properly (like customers, restaurants, orders, and food items).
• Different user roles:
Our system allows different types of users—like admin, customers, restaurant
owners, and delivery staff—to access only what they need using role-based access.
• Reports and analytics:
Our system can run useful reports, like which food is ordered the most or how many
orders were placed in a day, using advanced SQL queries.
• Faster and future-ready:
We use indexing to make data searches faster and design the system so it can grow
in the future without problems.
• Secure data handling:
We protect user data by using password encryption and safe data storage methods.
METHODOLOGY AND TECHNOLOGIES USED:
Proposed approach to solving the problem:
We aim to build a user-friendly online platform where customers can
browse menus, place orders, and make payments, while restaurant
owners and delivery staff manage their tasks efficiently.
Our focus is on efficient database design, which helps manage large
volumes of data like user info, orders, food items, etc., without
confusion or errors.
User → Frontend (UI) → Backend (Processes Request) → Database
(Stores or Retrieves Data)
BLOCK
DIAGRAM
Tools, Programming Languages and Frameworks Used:
• Frontend: HTML, CSS, JavaScript (for building the web interface)
• Backend: PHP (for handling logic and server-side communication)
• Database: MySQL (for managing all the system data)
• Tools: XAMPP(for local server setup), phpMyAdmin (for managing the
database)
Hardware and Software Requirements:
• Hardware:
• A computer with at least 4GB RAM and internet access
• Software:
• Code editor (e.g., VS Code)
• Local server (e.g., XAMPP)
• MySQL Server
• Web browser (e.g., Chrome or Firefox)
MODULES OR PROTOTYPES DEVELOPED:
• User Registration and Login Module
• Restaurant and Menu Management Module (Admin Panel)
• Food Browsing and Cart Module (Customer Side)
• Basic Order Placement Module:
CHALLENGES FACED ANDHOW THEY ARE BEING ADDRESSED:
• Designing a Proper Database Schema
• Managing Multiple User Roles
• Data Integrity and Validation
• Connecting Frontend to Backend and Database
• User Session and Cart Handling
ER-
DIAGRAM:
THANK YOU
