Restaurant Order Management System: No Name Enrollment No
Restaurant Order Management System: No Name Enrollment No
Restaurant Order Management System: No Name Enrollment No
management system
no name Enrollment no
1 Bhavsar akshar 002
2 Thakor harsh 012
PROJECT WORK CERTIFICATE
This is to certify that the project report submitted by Name of Project Developer,
having enrollment no. 002/012 , a student of M.Sc. IT Semester- I, Department of
Computer Science, KSV University, Gandhinagar have/has completed his/her project
titled as Project Title satisfactorily.
Acknowledgment
I am grateful to my Internal Guide for providing me valuable guidance for project work
and other domain related information.
objective
Function requirement
ER diagram
Data dictionary
scope
Take order
the waiter will take order and if it is available to make then he will confirm the order
and start to prepare food.
Serve food
when the food Is ready to be served then the waiter will serve the food to customer
Payment
the cashier (admin) will received the payment .
System Architecture, Tools &
Technology
Software requirements:
1.MYSQL server
2.windows 7 or higher
3.dreamviewer software
ER diagaram
Use case diagram: order process
Use case diagram: billing process
USE CASE DESCRIPTION FOR ORDER
PROCESS OF RESTAURANT ORDER
MANAGEMENT SYSTEM
NAME Order process for restaurant order management system
ID Re_01
DESCRIPTION In this process customer give order to the waiter and food will be served by
waiter.
ACTOR Customer , waiter
ORGANIZATIONAL With the use of this functionality organization requires less waiters and work
BENEFITS become faster and expenses of the organization will reduce.
PRECONDITIONS At first stage customer come and customer must give order otherwise
functionality not works.
POST CONDITIONS After the precondition customer give bill.
EXCEPTIONS
USE CASE DESCRIPTION FOR BILLLING
PROCESS OF RESTAURANT ORDER
MANAGEMENT SYSTEM
NAME billing process for restaurant order management system
ID Re_o2
DESCRIPTION In this process payment will be done.
ACTOR Waiter ,admin ,customer
ORGANIZATIONAL BENEFITS With the use of this functionality organization requires less waiters and work
become faster and expenses of the organization will reduce.
PRECONDITIONS In this at first customer eat their food then pay the bill
POST CONDITIONS After pre condition payment successfully done will be display.
EXCEPTIONS
Data Dictionary
Category table :-
Column name Data Size Description Constrain
Cat_id Numeric 5 Id f category Primary key
Name Varchar 15 Name of Not null
category
Description Varchar 100 Information Not null
about
category
Item Table :-
Column name Data Size Description Constrain
Item_id Numeric 5 Id of item Primary key
Cat_id Numeric 5 Id of category Foreign key
Item_name Varchar 15 Name of item Not null
Description Varchar 100 Info about
item
Rate Numeric 4 Rate of item Not null
Unit Numeric 3 No of item
Token Table :-
Order Table :-
Billing Table :-