Food On Click A PROJECT REPORT Submitted by Maheshwari Monalisa M

Food On Click
A PROJECT REPORT
Submitted by
Maheshwari Monalisa M. (160403107001)
Raval Taral J(160403107006)
In fulfillment of the subject PROJECT-I (2170002)
Of
B.E. Semester VII
In
Computer Engineering
1538605257175
center3175

Sankalchand Patel College of Engineering, Visnagar
Gujarat Technological University, Ahmedabad
OCT- 2018
Computer Engineering
INDEX
CHAPTER 1 Introduction 1
1.1 Project summary 1.2 Aim and Objective 1.3 Problem Specification 1.4 PSAR 1.5 PPR 1.6 Plan of Work 1.7 Tools and Technology Used CHAPTER 2 Product Design Engineering 16
2.1 AEIOU Summary 2.2 Ideation 2.3 Product Development 2.4 Empathy Mapping CHAPTER 3 System Analysis and Design 21
3.1 Study of Current System 3.2 Problem & Weakness of Current System 3.3 System Requirements 3.4 Feasibility Study 3.5 UML Diagrams 3.6 Data Dictionary 3.7 Features of new System CHAPTER 4 Conclusion and Future Work 40
References 46

CERTIFICATE
Date:
This is to certify that the project entitled “Food On Click” has been carried out by Maheshwari Monalisa M.(160403107001) , Raval Taral J (160403107006) under my guidance in fulfillment of the subject PROJECT-I(2170002) of Bachelor Of Engineering in Computer Engineering (Semester VII) of Gujarat Technological University, Ahmedabad during the academic year 2018-19.

Internal Guide Head of Department
Name: Mr. Ankur J Goswami
ACKNOWLEDGMENT
I express our sincere gratitude towards our guide MR Ankur J Goswami for his constant help, encouragement, suggestions and inspiration throughout the project work. Without his invaluable advice, suggestions and assistance it would not have been possible for me to complete this project work.

I wish to thank the Computer Engineering Department of Sankalchand Patel College of Engineering, Visnagar for their sympathetic co-operation. Our sincere thanks to all the authors whose literature We have used as a reference of our work. I am very thankful to our classmates, our Family & our Friends who supported throughout the project.

Maheshwari Monalisa M
(160403107001)
Raval Taral J
(160403107006)
INTRODUCTION
Project Overview:
When the customer enters the restaurant, they would surf on the tablet to order them menu.
they could also surf quickly if he has already decided upon what to order.

they would click the item he wants to order and after they are sure they wants each item in the list, they would click confirm.
The confirmed order would be displayed on the display screen in the kitchen.

After the chef has completed preparing the item, it would be notified to the customer.

After the customer has completed eating the food, bill would be directly displayed on his tablet as well as managers system.

Scope & Objective:
Scope:
This project would be very useful for Hotel where regular evaluation of user’srequirement. Further it can also be useful for anyone who requires feedback based on objective type responses. Scope of this project is very broad in terms of other manually taking order.

Objective:
The main purpose behind the proposed system is to provide a comprehensive computerized system, which can capture, collect and analyze the data from these wards and evaluate the impact of the program.

To provide touch screen facilities in hotel.
Problem Specification:
Waiters taking the wrong order.
Language barriers between staff and customers.

Difficulty adding to or changing customer orders.

Orders lost between the waiter and the kitchen.

Required More Staff.

1.4PSAR
PSAR1:-

PSAR2:

PSAR3:

PSAR4:-

PSAR5:-

1.5 PPR:
PPR 1

PPR 2

PPR 3

PPR 4

1.6 Work of Plan:
Work of plan
Month Requirement Gathering Analysis Documentation designing Report Generation
June July August September October 1.7 Tools and Technology:
Software requirements:
Server side:
Web server software Apache Server 2.2
Server side scripting tools PHP 5.3.0
Database tools Mysql Server 5.2.2
Compatible operating system Linux, windows
Client side:
Web browser supporting JavaScript, Enable cookies
Hardware requirements:
Server side :
CPU Core i5 or above.
RAM 2 GB or more.
HARD DISK 40 GB (Min).
Client side :
CPU Core i5 or above
RAM 2GB or more.
Product Design Engineering
2.1: AEIOU Summary:

Explanation:
Activities:
In Activities, I have include what activity is performing in website like authentication, view order, view bill etc.

Environment:
In Environment, I have include in what environment develop website like view video, surfing online etc.

Interactions:
In interactions, I have include which people interact to develop website like login, manage spareparts etc.

Objects:
In objects, I have include which objects are used to develop in website likeclient , Company, and sparepartsetc.
Users:
In users, I have include which users are use website like user, staff,adminetc.

2.2: Ideation:

Explanation:
Into ideation canvas there are four sections such as people, activities, situation/context/location and props. Into people I have described the people involving to our system like admin, staff, customer etc. Into activities I have described the same activities from the AEIOU canvas.
2.3: Product Development:

Explanation:
In product development sheet, I haveincluded purpose, people, product experience, product features, product function, customer revalidation and reject, redesign, retain respect to our website.
2.4: Empathy:
Explanation:
In empathy canvas there are four sections such as user, stakeholders, activities and story boarding. Story boarding contains happy story and sad story. Into user section I have described user of our system like employee and admin. Into stakeholders, I have described the people with whom user do the interaction like client, company HR etc. Into story boarding, we described the two happy and two sad stories before invent our system.

System Analysis and Design
Study Of Current System:
Waiters taking the wrong order.
Language barriers between staff and customers.

Difficulty adding to or changing customer orders.

Orders lost between the waiter and the kitchen.

Required More Staff.

Enquiry And Weakness Of Current System:
Can’t change order
Get wrong order
Issues in payment
System Requirement:
Customer can touches to modify the order after placing the for few minutes.

Customer can Menu descriptions and images has been seen.

Easily Manage Waiting Customer.

No Required more Staff.
Dynamic searching is available
The menu can be modified by the Kitchen manager.

Customer can get an order menu directly through touch the tablet.

Online Payment System.
3.5 UML Diagrams:
3.5.1 Use case Diagram:
Use Case Diagram shows a set of use cases and actors (a special kind of class) and their relationships. Use case diagrams address the static use case view of a system, these diagrams are important in organizing and modeling the behaviors of a system. Use case diagrams are helpful in three areas.

Determining features (requirements). New use cases often generate new requirements as the system is analyzed and the design takes shape.

Communicating with clients. Their notational simplicity makes use case diagrams a good way for developers to communicate with clients.

Generating test cases. The collection of scenarios for a use case may suggest a suite of test cases for those scenarios.

Fig. : 3.1 Usecase Diagram
3.5.2. Activity Diagram:
Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams can be used to describe the business and operational step-by-step workflows of components in a system. An activity diagram shows the overall flow of control .Activity diagrams are constructed from a limited number of shapes, connected with arrows.

Fig. 3.3: Activity Diagram Admin

Fig. 3.4: Activity Diagram staff

Fig. 3.5: Activity Diagram user
3.5.3 Sequence Diagram:
Sequence diagram is an interaction diagram. Interaction diagrams address the dynamic view of a system, besides sequence diagram, the other interaction diagram in UML is the Collaboration diagram. Sequence diagram emphasizes the time ordering of messages between objects in the system, while collaboration diagram emphasizes the structural organization of the objects that send and receive messages. Sequence diagrams and collaboration diagrams are isomorphic, and can be transformed from one into the other. Since either of them contributes to the same extend of understanding of our system, while sequence diagrams give more ideas of time, which is essential for real time systems, only the sequence diagrams are given in this report.

Fig. 3.5: Sequence Diagram

3.5.4 Data Flow Diagram:
A data-flow diagram (DFD) is a graphical representation of the “flow” of data through an information system. DFDs can also be used for the visualization of data processing (structured design).

Fig. 3.6: Context Level DFD
RegistrationRegistration Info.Manage Staff andUSERADMINUser Info.Request For Registration Info.View Registration Info.View Registration Info. menu _category Menu Category Info.View Menu Category Info. Item Type Info.Manage ItemTypeView item type Info.Order_detailOrder detail InfoViewOrderDetailView order detail Info.Bill_detail bill InfoManageBillDetailView bill detail Info.contactcontact Info.Manage ContactView contact Info.Request For View Menu Category Info.View Menu Category Info.Request For View item type Info.View Sub item type Info.Request For View order detail Info.View order detail Info.Request For View bill detail Info.View bill detail Info.Request For View contact Info.View contact Info.Request For View feedback Info.View feedback Info.feedbackfeedback Info.Manage FeedbackView feedback Info.item _typeManageMenuCATEGORY

Fig. 3.7: First Level DFD Admin
StaffRegistrationRegistration Info. StaffUser Info.Request For Registration Info.View Registration Info.View Registration Info.Menu_categorymenu Category Info.View menu Category Info. order detail Info.Manage OrderView order detail Info.bll_detailBill detail InfoManageBillView bill detail Info.Request For View menu Category Info.View menu Category Info.Request For View order detail Info.View order detail Info.Request For View Bill detail Info.View Bill detail Info.order_detailManageCustomer
Fig. 3.8: First Level DFD staff
RegistrationRegistration Info. USERUSERUser Info.Request For Registration Info.View Registration Info.View Registration Info.Menu_categorymenu Category Info.View menu Category Info. Sub Category Info.View ItemTypeView Sub Category Info.Order_masterorderOrder foodconfirmation.bill_detail bill detail InfoView BillDetail View bill detail Info.contactcontact Info.GivecontactView contact Info.Request For View menu Category Info.View menu Category Info.Request For View item type Info.View item type Info.Request For order.View.Request For View bill detail Info.View bill detail Info.Request For View contact Info.View contact Info.Request For View feedback Info.View feedbackInfo.feedbackfeedback Info. Give FeedbackView feedback Info.item_typeViewMenuCategory
Fig. 3.8: First Level DFD User
Data Dictionary:
3.6.1: Registration Table :
Sr.No Field Date Type(Size) Constraint
1 reg_id int(11) Primary Key
2 username varchar(20) Not Null, Unique
3 password varchar(20) Not Null
4 first_name varchar(20) Not Null
5 middle_name varchar(20) Not Null
6 last_name varchar(20) Not Null
7 bith_date Date Not Null
8 gender varchar(6) Not Null
Sr.No Field Date Type(Size) Constraint
9 mobile int(2) Not Null
10 email varchar(50) Not Null
11 seq_que varchar(255) Not Null
12 seq_answer varchar(50) Not Null
13 address varchar(100) Not Null
14 city varchar(50) Not Null
15 state varchar(50) Not Null
16 country varchar(50) Not Null
17 pin_code Int(3) Not null
18 reg_date Date Not Null
3.6.2: MenuItem Table:
Sr.No Field Date Type(Size) Constraint
1 mitem_id int(2) Primary Key
2 mitem_name varchar(50) Not Null
3 mcat_id int(2) Foreign Key
4 itm_typ_id int(2) Foreign Key
5 mitem_rate Int(2) Not Null
6 mitem_img Varchar(50) Not Null
7 mitem_description varchar Not Null
8 is_available int(2) Not Null
Item_description Table :
Sr.No Field Date Type(Size) Constraint
1 itm_des_id int(11) Primary Key
2 mitem_id int(11) Foreign Key
3 itm_img varchar(255) Not Null
4 itm_description Text Not Null
3.6.4: Table_master :-
Sr.No Field Date Type(Size) Constraint
1 tbl_mst_id int(11) Primary Key
2 tbl_no int(2) Not Null
3 tbl_seats int(2) Not Null
4 is_book int(4) Not Null
3.6.5:Order_masteTable:
Sr.No Field Date Type(Size) Constraint
1 ord_mst_id int(2) Primary Key
2 order_no int(2) NotNull
3 ord_mst_date date NotNull
4 ord_mst_time int NotNull
5 tbl_mst_id int(2) Foreign Key
6 reg_id int(2) Foreign Key
7 amount Int(2) NotNull
8 is_pendding int(4) NotNull
3.6.6:Order _detail Table :

Sr.No Field Date Type(Size) Constraint
1 ord_dtl_id int(2) Primary Key
2 ord_mst_id int(2) Foreign Key
3 mitem_id int(2) Foreign Key
4 rate int(2) NotNull
5 qty int(2) NotNull
6 amount int(2) NotNull
7 status int(4) NotNull
8 remark text Null
3.6.7:bill_master Table:
Sr.No Field Date Type(Size) Constraint
1 bil_mst_id int(2) Primary Key
2 bil_mst_date Time NotNull
3 ord_mst_id int(2) Foreign Key
4 amount int(2) NotNull
5 reg_id
int(2) Foreign Key, Null
6 is_paid int(4) NotNull
3.6.8Country table:
Sr.No Field Date Type(Size) Constraint
1 cnt_id Int(2) Primary Key
2 cnt_name Int(2) Foreign Key
3.6.9State table:
Sr.No Field Date Type(Size) Constraint
1 st_id Int(2) Primary Key
2 st_name varchar(20) NotNull
3. cnt_id Int(2) Foreign Key
3.6.10 City table:
Sr.No Field Date Type(Size) Constraint
1 ct_id Int(2) Primary Key
2 ct_name varchar(20) NotNull
3. st_id Int(2) Foreign Key
3.6.11 Feedback table:
Sr.No Field Date Type(Size) Constraint
1 feed_id int(2) Primary key
2 name varchar(50) Not Null
3 email varchar(100) Not Null
4 mobile int(2) Not Null
5 city varchar(50) Not Null
6 feed_date time Null
7 comment text Not Null
3.6.12 Video_category :
Sr.No Field Date Type(Size) Constraint
1 video_cat_id int(2) Primary key
2 video_cat_name varchar(50) Not Null
3.6.13 Video :
Sr.No Field Date Type(Size)
1 video_id int(2)
2 video_cat_id int(2)
3 title varchar(50)
4 video_link text
Contact :
Sr.No Field Date Type(Size) Constraint
1 cont_id Int(2) P.K
2 cont_Date Date Not null
3 cont_name Varchar(20) Not null
4 email Varchar(20) Not null
5 mobile int(10) Not null
6 cont_subject Varchar(30) Not null
7 cont_details text Not null
3.7 Features of New System:
Fast working
Easy to work
Delightful customer service
Reduce staff cost and wait time
Avoid human error
Entertainments during ordering
Provide all languages to understand customer
Feedback
No paper wastage
Also helps the Customer’s to decide a particular
Food item with a positive feedback
Conclusion ; Future Work
Conclusion:
By implementing this system, it will minimize the number of employees at the back of the counter.

Also the system will help to reduce the cost of staff. As there is lot of orders at the restaurants, there is possibility of human errors during calculations or taking orders.

By using this system, such type of errors can be eliminated and controlled up to some level. But by using this system it will be less probable to make such mistakes
Addition to this, this will avoid long queues at the counter due to the speed of execution and number of optimum screens to accommodate the maximum through put.

Future Work:
Design
Coding
Testing
Collecting review from the stakeholders
Updating with respect to the reviews collected
References
Website:
1 www.simplifiedcoding.com2 www.androidhivel.com3 www.journaldev.com