ONLINE - FOOD - ORDIERING - MANAGEMENT - SYSTEM (1) - For Merge

ONLINE FOOD ORDIERING MANAGEMENT SYSTEM
1. INTRODUCTION
Online food ordering is process of ordering food from a local restaurant or food
cooperative through a webpage or app. Payment can be among others either by credit card or
cash.
A customer will search for a favorite restaurant, usually choose from available items, and
choose delivery or pickup. This online food ordering system intends different types of forms
with different of food varieties provides to user to buy online. User can give order from any
place and pay cash on delivery or either credit card. Ordering is done by a valid customer with
appropriate identity. Hotel/restaurant staffs can edit, delete and create food items, food menu,
price and pictures. There is a separate admin section is available for secure use.
BCA IN WEB SCIENCE Page 1

1.1 PROJECT MODULES
1. Customer login
2. Manager
3. Item
4. Billing.
5. Order.
 Customer login:
Customer should login by providing the details
 Manager:
Manager is an employee who is responsible for managing the orders
 Item:
It contains list of food items or menu
 Billing :
The process of preparing or sending invoices
 Order:
It keeps information about the particular order.

2. SYSTEM ANALYSIS
2.1 Existing system:
Many restaurants stores and maintain their day to day transactions manually.
But some of them are having automated system which is helping them to store the
data. But such restaurants are storing the information about the orders and the customer
information .They don’t have facility to store the information of feedbacks and favorite
order of customers over some period of time
The software which restaurants are using is very costly and their maintains which is very
high
Drawbacks:
 This software is basically used only for reservation means table booking.
So if we want to just order some food or store any feed backs then it won’t be any
helpful.
At last the restaurants have to store themselves which will become no use of software.
 The user interface of the application is also not that much attractive. It is made in .net so
the restaurant must have to install any windows operating system to install this
application.
 Many of the systems will not store the budget details for a long time
 This will create lot of mistakes like misspellings, calculation problems, duplicate entries
etc.

2.2 Proposed System:
The proposed system helps in many ways. It helps to do billing very easily. Account
maintenance also becomes easier. They can keep track of their purchases of inventories, staffs
details, customer’s feedback, sales of foods, and account details etc. The software is provided
with the facilities to find out the favorite food of the customers, and the seasonal foods, or
customers to add or modify and delete their feedbacks and suggestions. It helps in managing data
of different types of orders like party order, home delivery or normal order. Managing data of
daily customers, managing data of staffs, managing data of daily expenses. It eliminates the
drawbacks of existing system and also includes some more features.
Advantages of Proposed System:
 RMS (record management system) will stores all the records permanently and also gives
the raises and deviations in the status of the restaurants in the markets.
 All the records of the current and ex-staffs will be stored in the database.
 All the shift timings of staffs, salary, extra working time and charge etc. are also update
daily.
 Manages can view the kitchen side, floor side and the counter side details simultaneously
and also can get details and updates from various branches.
 Any cancelations of parties are also updated.
 All the expenses per day will update in the database daily.
 All the food order details like the order types (normal, home delivery, party order etc.)
are stored daily.

2.3 Feasibility Analysis:
An initial inspection is to come across whether the request done by the system is feasible.
All systems are viable when it is provided with never ending time and boundless
resource. This circumstance does not exist in realistic world. Therefore it is better to
assess the system feasibility during the initial phase. Feasibility & risk analysis are co-
related. If there exists much risk in a project, then, the chance of developing high quality
software is less. The different feasibilities to be analyzed are as follows:
2.3.1 Performance Analysis:

First the project must run in a well networking environment in order to enhance complete
functionality. Normally, windows XP is used as O.S. Project performance depends on
fast network, number of users, customer reviews and convince offered.
2.3.2 Technical Analysis:

System is said to be favorable when the information meets the technical requirements of
an organization. It checks whether the system work properly when developed& installed,
and also checks if there exists any barriers to implement the system. Apart from these,
there several points to focus on the technical analysis:
Modifications to be made in the system:

Modifications made should be such that, it increased the level of efficiency.
Required skills: Skilled manpower is readily available in the industry with known
languages and platforms used in the project.
Acceptability: An end user must accept the structure of the system.
2.3.3 Economical Analysis:

Cost of the hardware used is less. Many users can access the system at same time as it is
based on the network. For running this system, high performance servers are not required.
Software modules are used to implement the functions. No physical devices are used for
connection which makes it more economical on.
3. SYSTEM DESIGN
3.1 E-R DIAGRAM:

Contact
pay_id number
ID.NO Name
pay type
price
Paid to
BILL MANAGER
Received by
PAYS
Cus_ID cus_id
Name
Order_id
1
PLACES
CUSTOMER 1 N ORDER
price
timing
ord
Address CONTAINS
_id
Price
N
Quantity ITEMS
Item ID
Description
3.2 DATA FLOW DIAGRAM

3.2.1 Level 0:
0.0
Orders for Food order
food Online food
Customer ordering Order
management
Receipt
system Bill
Manager
Report
3.2.2 Level 1:

Orders for 1.0

Food order
food
Processing for
Order
Customer order
Receipt
2.0 Solid 3.0

items
Update sold items Update investing
files
Data base of Inventory database

sold items
Information about delay

4.0
inventory
Generate
Information about solid management report
items and amount
Management
Manager
Report
4 . SYSTEM REQUIRMENTS
4.1 Functional Requirements:

These are the services that describe what the system must do, how the system should react to
particular inputs and how the system should behave in particular situation.
4.2 Non-Functional Requirements:
 These are the constraints on the service offered by the system they include reliability
response time, storage occupancy.
 They may specify system performance, security, availability and other emergent
properties.
4.2.1 Types of Non Functional Requirements:
 Product requirement:
These requirements specify product behavior. It includes portability and
usability requirement.
 Organizational requirement:
These requirements are derived from policies and procedures in the customer’s
and developer’s organization.
 External requirement:
It covers the entire requirements that are derived from the factors external to
the system & its development process. It includes interoperability requirement which
defines how the system interacts with other system in an organization.
4.3 Domain Requirements:

These are derived from the application domain of the system. They usually include
specialized domain terminology. They may be functional or non-functional.
4.4 Hardware requirement

 Processor :800mhz Intel Pentium III or equivalent or new
 Hard Disk :50 mb or more.
 RAM: 512 mb or more
 Mouse: Optical Mechanical Mouse
4.5 Software requirement

 Internal connection: 100mbps
 Operating system : Windows XP(or latest)
 Front-end : java /html
 Back-end: MySQL
5. DATA TABLE

5.1 Customer table:
File name Data type Key Description

Order_id Integer Primary key It contains customer
order id
Cus_id Integer Primary key It contains customer
id
Cus_name varchar Not null It contains customer
name
5.2 Billing Table:
File Name Data Type Key Description

Pay ID Integer Primary key It contains payment id
Price Integer Not null It contains price of the
item
Pay Type Varchar Not null It contains payment
type
5.3 Order Table:

Order ID Integer Primary key It contains order id
Customer ID Integer Foreign key It references customer
id from customer table
Total Price Integer Not null It contains total price
of the ordered item
Timing Integer Not null It contains timing of
the order
5.4 Manager Table:

Manager ID Integer Primary key It contains manager
id.

Contact no Integer Not null It contains contact

number.
Name Varchar Not null It contains name of
the manager.
5.5 Item Table:

Item ID Integer Primary key It contains item id
Quantity Integer Not null It contains quantity of
the item
Price Integer Not null It contains total price
of the ordered item
Description Varchar Not null It contains details of
the item
6.INTERFACE DESIGN
6.1 Customer:


6.2 Order:

6.3 Billing:

6.4 Manager:

6.5 Item:

7. Testing
The general testing process is the creation of a test strategy, creation of a test plan/design and the
execution of tests. Test data are inputs that have been devised to test the system.
7.1 Testing Processes:
 A testing process is a tool or method used to test an application.
 A major part of our project is describing the strategy for testing.
Unit
Testing
Module
Testing
Sub
System
System
Testing
Acceptance
Testing

7.1.1 Unit Testing:
 Individual components are tested to ensure that they operate correctly.

 Each component is tested independently, without referring other system components.
7.1.2 Module Testing:
 It is a collection of dependent components such as an object class, an abstract data type or

some collection of procedures and functions.
 A module encapsulates related components so that it can be tested without referring other
system modules.
7.1.3 Sub-System Testing:
 It involves testing collection of modules which have been integrated into sub-systems.
 The sub-system test process should concentrate on the detection of interface errors.
7.1.4 System Testing:
 The sub-system are integrated to make-up the entire system.

 It is also concerned with validating that the system meets its functional and non-
functional requirements.
7.1.5 Acceptance Testing:
 This is the final stage in the testing process before the system is accepted for operational
use.
 The system is tested with data supplied by the client rather than simulated test data.

7.2 Test Cases
Sl.n Action Input Expected Actual Test Test

o Output Output Result Comments
1 Enter Customer name: Opens Home Opens Home Pass customer login
correct xyz page page is Successfully
customer Password:***
name and
Password
2 Enter Customer name: An error An error pass Customer login
incorrect xzy message message is not
customer Password:**** Should Should Successfully
name and display with display with
Password wrong wrong
Customer Customer
name and name and
Password Password
3 Enter Manager Manager Pass Manager exists
correct Manager name: page should page should
manager xyz open open
name and id id:***
4 Enter Manager name An error An error Pass Manager does
incorrect xzy message message not exists
manager id:**** Should Should
name and id display with display with
wrong wrong
manager manager
name and id name and id
5 Enter 56473 Valid Valid Pass Customer is
correct customer customer registered and
customer id can order item.
6 Enter 854988 A message A message Pass Customer is not
Incorrect Should Should registered and
customer id display with display with cannot order
wrong wrong item.
customer id customer id
7 Enter Valid 3645753 Details of Details of Pass Order successful
Order id order order print receipt.
8 Enter 547457 A message A message Pass Invalid Order id
Invalid Should Should checks the id
Order id display with display with and enters once
wrong Order wrong Order again.
id id

9 Enter valid 346547 Details of Details of pass Payment

payment id payment payment successful
10 Enter 454754 A message A message pass Invalid
Invalid Should Should payment id,
payment id display with display with check the id
wrong wrong and enter
payment id payment id once again.
11 Enter valid 457457 List of items List of items pass Item exists
item id displays displays
12 Enter 346457 A message A message pass Item does
Invalid item Should Should not exists
id display with display with
wrong item wrong item
id id

8.Conclusion And Future Scope:
8.1conclusion:
Therefore, conclusion of the proposed system is based on user’s need and is user centered. The
system is developed in considering all issues related to all user which are included in this
system. Wide range of people can use this if they know how to operate android smart phone.
Various issues related to mess/tiffin services will be solved by providing them a full fledged
system. Thus, implementation of online food ordering system is done to help and solve one of
the important problems of people.
Based on the results of this research, it can be concluded: It helps customer in making order
easily; It gives information needed in making order to customer. The food website application
made for restaurant and mess can help restaurant and mess in receiving orders and modifying its
data and it is also made for admin so that it helps admin in controlling all the Food system.
8.2Future scope:
This food ordering management system project aimed at developing an online food ordering
system which can be used in small places, and medium cities firstly and then on large scale.
It is developed to help restaurants to simplify their daily operational and managerial task as well
as improve the dining experience of customers.
And also helps restaurant develop healthy customer relationship by providing good services.

ONLINE - FOOD - ORDIERING - MANAGEMENT - SYSTEM (1) - For Merge

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ONLINE - FOOD - ORDIERING - MANAGEMENT - SYSTEM (1) - For Merge

Uploaded by

Copyright:

Available Formats

ONLINE FOOD ORDIERING MANAGEMENT SYSTEM

BCA IN WEB SCIENCE Page 1

1.1 PROJECT MODULES

The process of preparing or sending invoices

BCA IN WEB SCIENCE Page 2

BCA IN WEB SCIENCE Page 3

2.2 Proposed System:

Advantages of Proposed System:

BCA IN WEB SCIENCE Page 4

2.3 Feasibility Analysis:

2.3.1 Performance Analysis:

2.3.2 Technical Analysis:

Modifications to be made in the system:

Acceptability: An end user must accept the structure of the system.

2.3.3 Economical Analysis:

BCA IN WEB SCIENCE Page 6

3.2 DATA FLOW DIAGRAM

BCA IN WEB SCIENCE Page 7

BCA IN WEB SCIENCE Page 8

Orders for 1.0

2.0 Solid 3.0

Data base of Inventory database

Information about delay

4.1 Functional Requirements:

BCA IN WEB SCIENCE Page 9

4.2 Non-Functional Requirements:

4.2.1 Types of Non Functional Requirements:

4.3 Domain Requirements:

BCA IN WEB SCIENCE Page 10

4.4 Hardware requirement

4.5 Software requirement

BCA IN WEB SCIENCE Page 11

5.1 Customer table:

File name Data type Key Description

5.2 Billing Table:

File Name Data Type Key Description

5.3 Order Table:

File Name Data Type Key Description

5.4 Manager Table:

File Name Data Type Key Description

BCA IN WEB SCIENCE Page 12

Contact no Integer Not null It contains contact

5.5 Item Table:

File Name Data Type Key Description

BCA IN WEB SCIENCE Page 13

BCA IN WEB SCIENCE Page 14

BCA IN WEB SCIENCE Page 15

BCA IN WEB SCIENCE Page 16

BCA IN WEB SCIENCE Page 17

BCA IN WEB SCIENCE Page 18

7.1 Testing Processes:

 A testing process is a tool or method used to test an application.

 A major part of our project is describing the strategy for testing.

BCA IN WEB SCIENCE Page 19

7.1.1 Unit Testing:

 Individual components are tested to ensure that they operate correctly.

7.1.2 Module Testing:

 It is a collection of dependent components such as an object class, an abstract data type or

7.1.3 Sub-System Testing:

7.1.4 System Testing:

 The sub-system are integrated to make-up the entire system.

7.1.5 Acceptance Testing:

BCA IN WEB SCIENCE Page 20