TABLE OF INDEX

1. Project Title 2

2. Introduction 3

3. Objective 4

4. Project Category 5

5. Purpose & Scope 6

6. Survey of Technologies 7

7. Requirement and Analysis 8

7.1 Problem Definition 8

7.2 Requirement Specification 8

7.3 Planning AndScheduling 9

7.4 Hardware & Software Requirement Specification 10

7.5 Module Description 11

8. System Development Life Cycle 13

9. Data Flow Diagram(DFD) 14

10. Use Case Diagram 17

11. Entity Relationship Diagram(ERD) 18

12. Data structure 19

13. Process Logic 21

14. Testing 23

15. Limitation 23

16. Industry/ Client Interface 24

17. Scope of Future Application 24

18. Bibliography 25
 *
1. PROJECT TITLE
“ECOMMERCE FOR FOOD ORDERING” is title of my project. This system

is a web based portal developed in OOPS & RDBMS platform. It will allow

online enquiry related to store billing & management.

2. INTRODUCTION

The “ECOMMERCE FOR FOOD ORDERING” has been initiated for many

different reasons. This is very effective platform for manage food business online

with effective bill management. To perform this effectively user need to register

with this system. After successful registration they will verified by the admin.

After successfully verification user can put their food requirement and we fulfill

their test. We are the best and taking care of their test requirement.

Basically, this system provide an online interface where user can visit and choose

menu as per requirement and order online to interested menu item. Our system is

already connected with delivery system so ordered item can be delivered within

30 minutes at registered address. Payment mode may be cash on delivery, after

implementation with bank payment gateway it will also done by using credit card,

debit card as well as net banking.

Developed By – 2
 3. OBJECTIVE

With the help of this proposed project we can able to full fill the following

objectives:

 This is very cost effective billing management system.

 Through this system online food management become easy.

 It reduces the efforts and problem over offline approach.

 It allows a large no of user simultaneously with food requirement in

specific area.

 User can also share their feedback with us.

 We can also send information to the respective user via mail or sms.

 It provides more secure platform with user friendly environment.

 It is beneficial for every person.

 It is very effective medium for quick food management.

 It can be easily access by anyone.

Developed By – 3
 4. PROJECT CATEGORY

“ECOMMERCE FOR FOOD ORDERING” is an OOPS and RDBMS based

system. So Project Category is OOPS/RDBMS. Where following platform will

used:

 Front End : PHP

 Back End / RDBMS : My Sql

 Internet Technology : HTML, Java Script, CSS

 Web Server : APACHE

Benefits of Using RDBMS

Using an RDBMS for this project offers several advantages:
 Data Integrity: Ensures that data is consistent, accurate, and stored in a structured way.
 Scalability: Can handle large volumes of transactions and data, essential for growing user bases.
 Security: RDBMS offers built-in security features like access control, encryption, and backup
capabilities to protect sensitive data.
 Efficient Queries: SQL queries are optimized for fast data retrieval, ensuring smooth user experiences.

Project Title: E-commerce Food Ordering System using RDBMS

Introduction
The E-commerce Food Ordering System is a dynamic and user-friendly web application designed to facilitate
the online ordering of food from various restaurants. This system enables customers to browse menus, place
orders, and make payments, all while ensuring smooth and secure transactions. The system is built using
Relational Database Management Systems (RDBMS), which ensures data consistency, security, and
scalability.
The goal of this project is to provide an efficient and comprehensive solution for both food vendors and
customers, offering an interface that streamlines the ordering process. By leveraging an RDBMS like MySQL or
PostgreSQL, the application benefits from well-structured data storage, optimized queries, and robust data
integrity.
Project Scope
The scope of the E-commerce Food Ordering System covers various aspects, including:
 Customer Registration and Authentication: Customers can register and log in securely to manage
their orders.
 Menu Browsing: Users can browse through menus of different restaurants, filter items by categories,
and search for specific food items.
 Order Placement: Customers can add food items to the cart, modify the cart, and proceed to checkout.
 Payment Integration: Integration with secure payment gateways for processing payments.
Developed By – 4
  Order Tracking: After the order is placed, users can track the status of their orders in real-time.
 Admin Panel: Restaurant managers and administrators can manage orders, update menus, and track
customer feedback.
Database Design
The backend of the Food Ordering System is structured using an RDBMS, which stores and manages all
relevant data. Below is a high-level overview of the database design for the system:
1. Users Table
This table stores information about customers and admin users.
 user_id (PK): Unique identifier for each user.
 username: User's login name.
 password: Encrypted password for authentication.
 email: User’s email address.
 phone_number: Contact number.
 role: Role of the user (Customer or Admin).
2. Restaurants Table
This table holds information about different food vendors.
 restaurant_id (PK): Unique identifier for each restaurant.
 restaurant_name: Name of the restaurant.
 location: Physical location of the restaurant.
 contact_number: Restaurant’s contact details.
3. Menu Table
This table stores the food items available at each restaurant.
 menu_item_id (PK): Unique identifier for each food item.
 restaurant_id (FK): Links to the restaurant offering the item.
 item_name: Name of the food item.
 item_description: Description of the food item.
 item_price: Price of the item.
 item_category: Category (e.g., starters, mains, desserts, drinks).
 availability_status: Whether the item is available for ordering.
4. Orders Table
This table stores information about customer orders.
 order_id (PK): Unique identifier for each order.
 user_id (FK): Links to the user placing the order.
 restaurant_id (FK): The restaurant from which the order was placed.
 order_date: Date and time when the order was placed.
 total_price: Total price of the order.
 order_status: Status of the order (e.g., Pending, In Progress, Delivered, Cancelled).
5. Order_Items Table
This table stores the individual items that make up each order.
 order_item_id (PK): Unique identifier for each order item.
 order_id (FK): Links to the order.
 menu_item_id (FK): Links to the menu item ordered.
 quantity: Quantity of the menu item ordered.
 item_price: Price of the menu item at the time of the order.
6. Payment Table
This table records payment details for each order.
Developed By – 5
  payment_id (PK): Unique identifier for each payment.
 order_id (FK): Links to the order being paid for.
 payment_date: Date and time when payment was made.
 payment_amount: Total payment amount.
 payment_status: Status of the payment (e.g., Successful, Failed, Pending).
 payment_method: Payment method used (e.g., Credit Card, PayPal, etc.).
7. Reviews Table
This table stores customer feedback for orders and food items.
 review_id (PK): Unique identifier for each review.
 user_id (FK): Links to the user who wrote the review.
 order_id (FK): Links to the order being reviewed.
 rating: Rating of the order (1-5).
 comment: Text feedback left by the customer.
System Flow
1. User Registration and Login: Users can register an account with the system, providing details such as
name, email, and password. They can then log in to place orders.
2. Menu Browsing: Once logged in, users can browse through the available restaurants and their menus.
They can filter food items by category or search for specific dishes.
3. Order Placement: Users can add food items to their cart, modify the cart, and review the order before
proceeding to checkout. At checkout, they enter their delivery address and make the payment.
4. Payment and Confirmation: After the payment is processed, the user receives an order confirmation,
and the restaurant prepares the food for delivery.
5. Order Tracking: Customers can track their order status in real-time, from preparation to delivery.
6. Order Feedback: Once the order is delivered, users can leave feedback and rate the service and food
quality.

Developed By – 6
 5. PURPOSE AND SCOPE

Purpose:

The purpose of “ECOMMERCE FOR FOOD ORDERING”is to provide tasty

food availability to each and everyone at best price with best support.

Scope:

The scope of this proposed system i.e. “ECOMMERCE FOR FOOD

ORDERING” is very broad. We try to connect many vendors and person who

involved in food business So that we are able to serve many societies. Currently

our main focus is to implement in New Delhi area only. After successful

implementation we moved for next region.

Developed By – 7
 6. SURVEY OF TECHNOLOGIES
For preparing this proposed project (i.e. “ECOMMERCE FOR FOOD

ORDERING”) there are so many technologies available in the current market.

But after lots of survey & discussion we found that following platform is suitable

for this proposed project:

Server-side programming Language : PHP

Web Server Platform : APACHE

Backend Database Platform : My Sql

Client-side programming Platform : Java Script

Other Tools / Languages used : HTML & CSS

Developed By – 8
 7. REQUIREMENTS AND ANALYSIS

7.1 PROBLEM DEFINATION

“ECOMMERCE FOR FOOD ORDERING” is introduced as a web based

project for tasty food management system. Following are the problem area to

implement this project.

 New User details & information Management

 Registered user management

 Food Menu management

 Keep test record to our regular customer

 Timely delivery management

 Payment Management

 Database management

 Site management with seo technique

 Invoice& Bill management

7.2 REQUIREMENT SPECIFICATION

“ECOMMERCE FOR FOOD ORDERING” is an online/web based project. It

is designed according to the following groups/modules:

 User Registration Module

 Menu Management Module

 Invoice & Billing Module

Developed By – 9
  Delivery Module

 Payment Module

 Admin Module

 Feedback Module

7.3 PLANNING AND SCHEDULING

Planning and scheduling technique for this project I choose Gantt chart. It is a

graphical representation of the duration of tasks against the progression of time.

Task achieved 1 2 3 4 5 6 7 8
( in weeks)
Analysis

Requirement
Gathering
Design

Coding

Testing

Implementation

Maintenance

Developed By – 10
 7.4. TOOLS AND PLATFORM

Platform Used Minimum Requirement Recommended Requirement

Processor Dual core processor Core i3
RAM 1 GB 2 GB
Operating System Windows XP Windows 2007

Hard Disk 120 GB 250 GB or more

Display 800 X 600 1024 X 768
Mouse/Key Board Usb/ps2 Compatible with System
Database My SQL My SQL
Software Tools PHP PHP
Web Server APACHE APACHE
Browser IE 8.0 IE 8.0, Mozilla Firefox ,Google
Chrome

Developed By – 11
7.5 MODULE DESCRIPTION

Following module used in proposed project as per mention in requirement

specification:

1. User Registration Module

2. Menu Management Module

3. Invoice & Billing Module

4. Delivery Module

5. Payment Module

6. Admin Module

7. Feedback Module

1. User Registration Module:

The basic purpose of this module is to provide an interface for new user who

wants to register with this system and fulfill their food requirement. They have

needed to just order their requirement as per mention menu. They can send order

via order menu, mail, call, smsetc but they must be mention user id. After order

we deliver food as per registered address and fulfill the payment responsibility.

2. Menu Management Module: This module includes menu details with their

price list. It is also available on website so that user can easily view, choose and

post their requirement.

3. Invoice & Billing Module:This system help to generating the effective

invoice and bill for manage the system.

Developed By – 12
4. Delivery Module:This module designed for manage the food delivery

process smoothly from tasty food processing house to the user/customer address.

5. Payment Module: This module is initiated to manage the payment record

properly. Payment may be online or cash on delivery as per requirement.

6. Admin Module:This system is properly managed and handled by admin of

this system. This module is introduced for manage all the things in proper

manner.

7. Feedback Module:This module is designed for collect the customer and

user feedback properly. With the help of feedback we can enhance our tasty food

quality.

Developed By – 13
 8. SYSTEM DEVELOPMENT LIFE CYCLE

There are several life cycle models available in the industries, which has been

tested and implemented over a long period of time. SDLC is beneficial to develop

any project because it describes how programs are developed. Following are some

model which is used in SDLC Phase of the Project/System.

 Waterfall Model

 Prototype Model

 Spiral Model

 Fourth Generation Techniques

 Object – Based Methods

We can choose any above mention model to develop “ECOMMERCE FOR

FOOD ORDERING” for required application and desired result, but after

detailed studying and lots of research it was decided to develop this proposed

projecton the basis of the Spiral Model because it is easy to implement and

manage it effectively. So, that I Choose Spiral Model for Proposed System i.e.

“ECOMMERCE FOR FOOD ORDERING”

Developed By – 14
 9. DATA FLOW DIAGRAM

Food Menu Invoice & Bill

Management

New User

MANAGER/Admin
Of this system
Registered
User

Delivery Payment

Admin

Figure 1: Data Flow Diagram-Level 0

Developed By: 15
 1.0
New User User
User Details System
Registration
System

2.0
Menu
Registered Management MenuDetails System
User System

3.0
Delivery Delivery
Management
Delivery Details System
System

4.0
Payment PaymentMan Payment Details System
agement
System

5.0
Invoice & Bill Invoice & Bill
Module invoice Details System
Management
Figure 2: Data flow diagram-Level 1

Developed By – 16
 2.1
User
Registration
Verification
System

New User /
Registered User Login Management System

2.2
User Login
Management
System

Figure 3: Data flow diagram-Level 2

Developed By – 17
10. USE CASE DIAGRAMS

Registration

Login

Add-Update
Details

Order &
Delivery

Manage User
Admin
User

Send details

Feedback

Support

Payment

Figure 4: Use Case Diagram

Developed By – 18
 11. ENTITY- RELATIONSHIP DIAGRAM

Contact no
User Id
Email id

User Name Address

User

Payment m
Mode
Invoice
details Register

Invoice id
Admin Id

Order id Admin
1 Password
1
MANAGER/Admin 1
date 1
Of this system
Registered
Invoice & Bill Login & Manage
User
Management
amount 1 m
1 User Id
Password
User id
1
1

m
Perform
Order id
m User id

date m
Order Delivery Delivery detail

amount
Payment
Date & time
User id address
Payment id User detail

date amount

Figure 5: Entity Relationship Diagram (ERD)

Developed By – 19
12. DATA STRUCTURE

New User Table:

Sl. Field Name Data Type Description

No.
1. User Name Varchar(20) User Name
2. User Id Varchar(20) Id of user
3. Contact no Varchar(10) User contact no
4. Email id Varchar(20) Email id of user(Primary Key)
5. Address Varchar(50) Registered address of user

RegisteredUser Table:

Sl. Field Name Data Type Description

No.
1. User Id Varchar(10) User Id(Primary Key)
2. Password Varchar(10) User valid password

Admin Table:

Sl. Field Name Data Type Description

No.
1. Admin Id Varchar(10) Admin Id(Primary Key)
2. Password Varchar(10) Admin valid password

Order Table

Sl. Field Name Data Type Description

No.
1. Order id Varchar(10) Order id (Primary Key)
2. Date Varchar(10) Date of order
3. Amount Varchar(5) Amount of current order
4. User Id Varchar(10) Order by user

Developed By – 20
Payment Table

Sl. Field Name Data Type Description

No.
1. Payment id Varchar(10) Payment id(Primary Key)
2. Date Varchar(10) Date of order
3. Amount Varchar(5) Amount of current order
4. User Id Varchar(10) Order by user/ user detail

Delivery Table

Sl. Field Name Data Type Description

No.
1. User id Varchar(10) user id for delivery(Primary Key)
2. Delivery detail Varchar(50) Delivery detail
3. Date & time Varchar(15) Date & time of delivery
4. Address Varchar(50) Address of delivery

Invoice & Bill Table

Sl. Field Name Data Type Description

No.
1. Order id Varchar(10) Order id(Primary Key)
2. Date Varchar(10) Date of order
3. Amount Varchar(5) Amount of current order
4. User Id Varchar(10) Order by user
5. Invoice Id Varchar(10) Invoice Id

6. Invoice Details Varchar(10) Invoice Details

7. Payment Varchar(10) Payment

Developed By – 21
 13. PROCESS LOGIC
“ECOMMERCE FOR FOOD ORDERING” is a web based platform by which

user are able to manage their food requirement effectively using web based

medium. It is designed on the basis of following Module:

1. User Registration Module

2. Menu Management Module

3. Invoice & Bill Management

4. Delivery Module

5. Payment Module

6. Admin Module

7. Feedback Module

1. User Registration Module:

The basic purpose of this module is to provide an interface for new user who

wants to register with this system and fulfill their food requirement. They have

needed to just order their requirement as per mention menu. They can send order

via order menu, mail, call, smsetc but they must be mention user id. After order

we deliver food as per registered address and fulfill the payment responsibility.

2. Menu Management Module: This module includes menu details with their

price list. It is also available on website so that user can easily view, choose and

post their requirement.

3. Invoice & Billing Module:This system help to generating the effective

invoice and bill for manage the system.

Developed By – 22
4. Delivery Module:This module designed for manage the food delivery

process smoothly from tasty food processing house to the user/customer address.

5. Payment Module: This module is initiated to manage the payment record

properly. Payment may be online or cash on delivery as per requirement.

6. Admin Module:This system is properly managed and handled by admin of

this system. This module is introduced for manage all the things in proper

manner.

7. Feedback Module:This module is designed for collect the customer and

user feedback properly. With the help of feedback we can enhance our tasty food

quality.

Developed By – 23
 14. TESTING

Testing is the necessary part of any project for successful implementation and

working. In “ECOMMERCE FOR FOOD ORDERING” we can use various

test models as per requirement. But right now it is on process. So, after proposal

& development we do proper testing work to make this system successful.

Future test method may be:

1. Unit Testing
2. System Testing
3. Acceptance Testing
4. Black-box Testing
5. White-box Testing
6. Grey-box Testing
As specialized testing following method also used:

1. Volume Testing
2. Stress Testing
3. Performance Testing
4. Interface Testing
5. Security Testing
6. Debugging

All above test will be done during development of the proposed project.

Developed By – 24
 15. LIMITATION

1. The main problem to successful this project is converting all food order &

menu in online medium.

2. E billing management is really tuff.

3. Sometimes it difficult to deliver the order on time.

4. We have to advertise this system so that user can know about this and use

this.

5. For this we need to make seocompatible websites

16. INDUSTRY/ CLIENT INTERFACE

Are you doing this project for any Industry/Client? Mention Yes/No. If Yes,

Mention the Name and Address of the Industry or Client.

Are you doing this project for any Industry/Client? Yes No

Developed By – 25
 17. SCOPE OF FUTURE APPLICATION

“ECOMMERCE FOR FOOD ORDERING” is fast growing platform for user

who wants to manage their tasty food requirement with web based easiest &

convenient system. After successful implementation and right approach by the

software developer it becomes most popular food order and management system.

Developed By – 26
 18. BIBLIOGRAPHY

BOOKS & WEBSITES

 Project Guide Booklet IGNOU

 PHP Dreamtech Press

 My Sql Wrox Publication

 Professional PHP Wrox Publication

 Introduction to Software Engineering IGNOU

 Software Engineering Roger S. Pressman

 Software Engineering Techmax Publication

Developed By – 27