RESTAURANT WEB

APPLICATION
Made by : Akash koshta
Shivalik singh
Prateek khandelwal

1
 INTRODUCTION

PROBLEM DESCRIPTION

People have difficulty deciding what to eat at restaurants.

Existing services make it easier ever to make an educated decision
on where to eat, thanks to user based reviews and ratings. What
these services have not been able to do, however is aid in the next
step .
 What cuisine you chose to eat once you sit down at your chosen restaurant ?
 What if you found yourself in a restaurant with a menu that is not familiar
to you and does not contain photos?

2
APPROACH USED :
 Object oriented -

3
EXISTING APPROACH

 One can order anything he wants only when he comes to the

restaurant in person, select what he wants to order from the menu
and take the parcel or dine-in at the restaurant itself.
 Not having a way to reach the restaurant is a big problem, the
restaurant may be very far away but it does have one of the best
food items and you want it right away, you can not always get the
menu on the websites, and some restaurants may not provide their
menu directly over a call. You may have to go to that restaurant to
get the desired dishes.
4
SOFTWARE PROCESS MODEL USED

 It is very well known about the requirements of the product thus it

was very obvious to use the WATERFALL MODEL.

5
 SYSTEM REQUIREMENT SPECIFICATIONS
(USE CASE DIAGRAM OF THE CUSTOMER MENU
MANAGEMENT SYSTEM )

6
 USE CASE
The end-users of the CMMS fall into three primary categories, unskilled, partly skilled and highly skilled.

 Unskilled User
The users of the surface computers are walk-in customers and should therefore be assumed to have no relevant prior skills or
education other than basic abilities to operate an automated system; no more complex than a parking meter or vending machine.

 Partly skilled User 

The users of the tablets and displays are waiters and chefs respectively and they should be able to use the system and further be
able to train others with minimal training themselves. They must be able to explain all elements of the user interfaces except the
server. Supervisors also fall into the same category, though they will have to learn other sections of the system (refunds etc.); these
should not be of notably greater complexity than the standard functions. This class of user would be expected to have at
leastcompleted high-school education or equivalent.
 
 Highly skilled User
The initial installation and configuration of hardware and the constituent CMMS system components (especially the server) is
guaranteed to require someone with notable computer experience, including extensive experience with network and operating
systems to complete it.

7
 SYSTEM REQUIREMENTS

Hardware Software
 Development End  Development End -
Heavy processor laptop Cuda ,Cunn setup for training on
Nvidia Gpu(Nvidia TitanX)RAM - GPU
8GB Python with installed library
 Deployment End - ( Tensorflow, Numpy , h5py ,
Intel i5 or higher compatible Opencv)
processor laptops  Deployment End -

Nvidia Gpu ( Optional) Python with installed library

RAM - 4GB ( Tensorflow, Numpy , tkinter, 8
Opencv)
CLASS DIAGRAM

9
ACTIVITY DIAGRAM

10
 DESIGN
System design: In this phase a complete
flow diagram of the working system is
designed. This flow diagram will show the
details of all the events like actions to be
performed for an event.

11
 USER INTERFACE DESIGN
 UI design: In this phase the UI or the user
interface of the project is developed. That is, the
designing of the web page which the user will use
to interact.

12
 METHOD
 The homepage displays the image of the restaurant, and it
provides the menu options, specials and the map. There is a signup
option and a login option for the user to login, the restaurant’s
phone no is also displayed.
 When the menu page is clicked on, different kinds of food
categories pop up eg soup, chicken, lunch etc. When an individual
category is selected, there is a unique id for every item in each
category.
 In signup page, the user fills the form and can also save his
favourite dishes.

13
 APPLICATION
 This project is proposed to save time in modern era where people are
mostly busy. This project aims to provide hassle free and convenient
way for people to order food online to be a part of growing digital
India by using internet.

14
SWOT ANALYSIS

15
 SWOT ANALYSIS

STRENGTHS WEAKNESSES

People have difficulty deciding what to eat at restaurants.  Requires internet connection.
Existing services make it easier ever to make an educated
decision on where to eat, thanks to user based reviews and  No waiter service available.
ratings. What these services have not been able to do, however
is aid in the next step

16
 SWOT ANALYSIS

OPPORTUNITIES THREATS
 In conventional cake stores and coffee shops, a static menu is
utilized to show the available food and beverage choices to
customers. These menus are generally paper based and
therefore impose restrictions on the prices available and a
responsibility to update them. This document specifies the
requirements for a restaurant paper menu and ordering
replacement strategy to alleviate the problems associated with
the current method. Three related concepts are encompassed  Unskilled user tend to disrupt the working of
by the general scope of the Customer Menu Management website.
System (CMMS). The first pertains to the replacement of
paper-based menus using an electronic format, the second
relates to an electronic strategy for the front office handling or
cashiering of a customer’s order and the third surrounds the
process of transferring said electronic orders to the kitchen for
preparation. It should be noted that while the suggested
strategy incorporates the use of various hardware components,
the primary focus of the presented SRS relates to the
constituent software elements.
17
 CONCLUSION

The main objective of the application is to help Computer Science students

understands the basics of Java, JavaScript and HTML. The following results have been
achieved after completing the system and relate back to the system’s objective-
•Should allow Computer Science students to browse through the code and application: This can be
achieved when students are able to run and install the application. When they run the application, they
can browse through the implementation of different objects.
•Should allow users to browse through different product categories: This is achieved through an
easy to use graphical interface menu options.
• Should allow users to save items to the cart and view detailed information about the order: The users
can add any number of items to the cart from any of the available food categories by simply clicking the
Add to Cart button for each item. Once item is added to the cart, user is presented with detailed order to
review or continue shopping.
• Should allow the user to CheckOut the item(s): This is achieved using the “Proceed to checkout
button” in the cart initially and then “CheckOut” button at last step after “review Order” step.. Button is
disabled when there are no items in the cart.
18
 FUTURE WORK

 The online food ordering system for restaurants is a trend which is

growing at a fast pace. Major Restaurants today just for the
convenience factor and increasing revenue are listing their services
even online. This is due to the fact that adoption for the mobile
technology has increased in leaps and bounds in the world.
 Phone orders and booking rates have declined extraordinarily these
days. Mobile apps developed to dedicatedly provide food ordering is
now a raging trend for all mobile users. With more than 2 billion
mobile users an app is today the best way to promote the restaurant.

19
 REFERENCES

 IEEE Std 830-1998 (Revision of IEEE Std 830-1993) IEEE

Recommended Practice for Software Requirements Specifications 
 Software Engineering: A Practitioner's Approach, 8/eRoger S
Pressman, R.S. Pressman & Associates, Inc Bruce R. Maxim,
University of Michigan
 Software Engineering, 9/e Ian Sommerville

 Software Engineering HandbookJessica Keyes

 Software Requirements, 3/e Karl Wiegers and Joy Beatty

 Systems Analysis and Design, 9/eGary B. Shelly and Harry J.

20
Rosenblatt
21