Site Loader
Rock Street, San Francisco

1.
INTRODUCTION

1.1 Purpose

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

           This project is provide overall online facility of customer, user,
administrator and other management system. The manager easily searches the
reservation system, remove and easily exit reservation on the hotel management
system. The management or admin be added revise the hotel and gives it’s all
information about the hotel. In the online management and reservation system
the customer can be easily find its own comfortable room and its satisfied on
the room charges. The manager gets requirements of the customer and provides
its room information and receives the charges.

 

 

1.2
Scope

 

           When we develop a project its
provide some facility or activity. The hotel management and reservation system
are provide that activities:

·        
By using
this facility the user or any customer give online order with a friendly manner
with both sides.

·        
Some
classes are used to control the activities of project and all the data of any
customer.

·        
The
system is managed easily and the flexible of overall project with a secure
environment.

·        
Integrity
and security are built in very strong because the unauthorized accessed are
impossible. Only registered person or user are use it.

·        
This
system has much memory to store customer data and its comments.

·        
That can
be easily access data and store.

·        
Some
feature are added to be generated different kinds of report.

 

1.3
Definitions
and Acronyms

SDD:

Software design document

DBMS:

Database management system

RMOS:

Restaurant menu and ordering system

PHP:

Personal home page

DB:

Data base

SQL:

Sutured query language

UML:

Unified modeling language

 

1.4
Reference Material

          For Design

www.onlineresturent.com

1.5
Overview

The remaining sections of these documents provide general
descriptions, including characteristics of the users of this system, the system
hardware and the functional and data requirements of the system. General
description of the project is discussed in section 2 of this document. These
are show the system description.

 

2.
System Overview

 2.1
Assumptions and dependencies

            Desktop computer, Operating System, Browser and
internet connection is compulsory. Suppose the customer enters the wrong information that the
system provides the message of its wrong information .The system must be save
this report and generate the issue. ORMOS support the platform like all windows
of XP, window 7, window 8. Window 10 does not support all the functionality of
the proposed system that it will provided.

 

2.2
General constraints

Its provide high
performance, user friendly, secure manner provide information and very fast.
This web portal are developed using
PHP web programming language as a front end and My SQL database as a backend.
Front end designing and html coding are done using Dreamweaver

2.3 Design Language

                UML is a unified
modeling language also a graphical language.UML is used for to graphical
representation of the project.  And also
UML diagrams are used these are Entity Relationship diagram, Data Flow
Diagrams, Class Diagrams, Activity Diagrams, Sequence Diagrams and State
Machine Diagrams also used during development of Online restaurant menu and
ordering system.

 

2.4 Technologies Used

Different technologies are used in online buying
foods on hotel, like HTML, CSS, PHP, MY SQL are used. HTML, CSS is used to make
the front-end of the site and MY SQL database and PHP are used for back-end. My
SQL database is used to save the records of customer, products and orders, when
register a new customer on this site, then system save his/her record for later
used when he/she log in. PHP is used for communication between customer and
company.

 

2.5 System Envierment

The
system we develop that Run on any operating system.

 

 

3. SYSTEM ARCHITURE

3.1  Architectural
Design      

       
Architecture  design  describe 
the  following   modules 
that  the  important parts  of 
the  system :

·        
Manager: The manager is an important personality of any
restaurant/company who handles all the administrative works.

·        
Customer: customer purchase the product that produce by
restaurant.

·        
Recipe: This is the menu item list that the restaurant
provides to its customers.

·        
Order: Order is the list of food items and the quantities
that is or is tobe requested from the customer.

 

3.2Decomposition

Define all the modules in detail.

3.2.2 Web architecture

3.2.3 Block Diagram

 

 

 

 

 

 

 

 

 

 

3.2.5 Use Cases

3.3.1
Use case: Manager   Login

3.3.2
Use case: Manager change Login password

3.3.3
Use case: User   Login

3.3.4
Use case: Retrieve password

3.3.5
Use case: User Registration

3.3.6
Use case: Check menu list

3.3.7
Use case: User Feedback

3.3.8
Use case: Search by price

3.3.9
Use case: Search by destination

3.3.10
Use case: Search by specific dish

3.3.11
Use case: Free-text search

3.3.12
Use case: History detail

3.3.13Use
case: Request for Order

3.3.14
Use case: Request for cancels Order

3.3.15
Use case: Table reservations for Events

 

 

3.3.1 Use case: Manager   Login

 

Name

Description

  Actors

           Administrator

Pre
condition

Database file should
be attached properly to system and Administrator form is open.      

Post
condition

After login the
administrator can perform many tasks and view the overall description about
their site .

Goals

Administrator can login to see the available
different food items and details about the site.

Steps

The manager provides the email id and
password. If manager enters correct id and password then he successfully   login to the system and view the details.
 

 

3.3.2 Use case: Manager change Login password

 

 

 

Name

Description

  Actors

           Administrator

Pre
condition

Database file should
be attached properly to system and Administrator form is open.      

Post
condition

After login the
administrator can perform many tasks and view the overall description about
their site .

Goals

Administrator can login to see the available
different food items and details about the site.

Steps

The manager provides the email id and
password. If manager enters correct id and password then he successfully   login to the system and view the details.
 

 

 

3.3.3 Use case: User   Login

 

 

Name

Description

  Actors

User

Pre
condition

Database file
properly attached to system and user form is open.                                          

Post
condition

After login the user can perform
many operations for viewing the overall detail about the site.

Goals

User can login to see the available food
items in the restaurant site with whole descriptions about food.

Steps

The user provides the email id and
password. If user enterscorrect email id and password then he successfully login
to the system and view the details.
 

 

 

3.3.4 Use case: Retrieve password

Name

Description

  Actors

          
User

Pre
condition

Database file
properly attached to system and user form is open.                                          

Post
condition

After retrieve their
password user can loginand perform many tasks and view the overall detail
about the site.

Goals

User can login to see the available
restaurant items and details about the site.

Steps

The user provides the email id and
password. If user enters s correct email id and password then he successfully
login to the system and view the details.
 

 

 

 

3.3.5
Use case: User Registration

 

Name

Description

  Actors

User

Pre
condition

Database file should
be attached properly to system and user form is open.                             

Post
condition

After login the user can
checks that their account successfully registered or not for see web site
details.

Goals

User can login to see the available food
items and details about the site.

Steps

The user provides the email id and
password for own registration. If user enterscorrect email id and password
then he successfully login to the system and view the details.
 

 

3.3.6 Use
case:Check menu list

 

Name

Description

  Actors

          
User

Pre
condition

Database file should
be attached properly to system and user form is open.                             

Post
condition

After login the user can
perform many tasks and view menu list about different types of foods and also
see overall detail about the site.

Goals

User can login to see the available food
items and details about the site.

Steps

The user provides the email id and
password for login their account and see all information 
 

 

 

 

 

3.3.7 Use case: User Feedback

 

Name

Description

  Actors

          
User

Pre
condition

Database file should
be attached properly to system and user form is open.                             

Post
condition

After login the user can
write feedback in feedback option about this site.

Goals

User can login to see the available food
items and details about the site.

Steps

The user provides the email id and
password for login site and
 

 

 

3.3.8 Use case: Search by price

 

 

Name

Description

  Actors

 User

Pre
condition

Database file should
be attached properly to system and user form is open.                             

Post
condition

After login the user can
see   different food item with their
prices.

Goals

User can login to see the available food
items and details about the site.

Steps

The user provides the email id and
password. If userenters correct email id and password then he login to the
system and view the details.
 

 

 

3.3.9 Use case: Search by destination

 

Name

Description

  Actors

User

Pre
condition

Database file should
be attached properly to system and user form is open.                             

Post
condition

After login the user can search
different destinations where restaurant are available in different places
with the help of their mobile application.

Goals

User can login to see the available food
items and details about the site.

Steps

The user provides the email id and
password to login their accounts and search by destinations.
 

 

 

3.3.10 Use case: Search by specific dish

 

Name

Description

  Actors

       
User

Pre condition

Database file should
be properly connected to system and user form is open.                             

Post
condition

After login the user can perform
many operations for see specific dishes in the restaurant system.

Goals

User can login to see the available food
items and details about the site.

Steps

The user provides the email id and
password. If user enters correct email id and password then he login to the
system and view the details.
 

 

 

3.3.11 Use case: Free-text search

 

 

Name

Description

  Actors

 User

Pre condition

User properly connected
to system and user form is open.   

Post
condition

After login the user can
perform many tasks using free-text application providing by the restaurant
for users and also view the overall detail about the site.

Goals

User can login to see the available food
items and details about the site.

Steps

The user provides the email id and
password. If user enters correct email id and password then he login to the
system and view the details.
 

 

3.3.12 Use case: History detail

 

 

Name

Description

  Actors

 User

Pre condition

Database file should
be properly connected to system and user form is open.                             

Post
condition

After login the can see
history of the restaurant.

Goals

User can login to see the available food
items and details about the site.

Steps

The user provides the email id and
password.
Successfully login and see history
details.

 

3.3.13Use case: Request for Order

 

Name

Description

  Actors

          
User

Pre condition

Database file should
be properly connected to system and request form is open.                 

Post
condition

After login the user can
request for order to the restaurant.

Goals

User can login to see the available food
items and details about the site.

Steps

The user provides the email id and
password. User successfully login to the system and request for order.
 

 

3.3.14 Use case: Request for cancels Order

 

 

 

Name

Description

  Actors

          
User

Pre condition

Database file should
be properly connected to system and request form is open.                 

Post
condition

After login user request
for order cancel to the restaurant.

Goals

User can login to see the available food
items and details about the site.

Steps

User provides the email id and
password. If user enters correct email id and password then he login and
cancels orders.
 

 

 

 

 

3.3.15 Use case: Table reservations for Events

Name

Description

  Actors

          
User

Pre condition

Database file should
be properly connected to system and user form is open.                             

Goals

User can login to see the available food items and details about
the site.

Steps

The user provides the email id and
password. If user enters s correct email id and password then he login to the
system and request for reservations.
 

 

 

 

 

 3.4 Class diagram:

Restaurant:

 

3.2.7 Class diagram:

Menu List:

 

 

 

 

 

3.2.8 Class diagram:

Bill:

3.2.9 Class diagram:

Order:

 

3.2.10 Class diagram:

Customer:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3.5 Sequence
diagram

Sequence
Diagram of User Registration and Log in

 

 

 

 

 

 

 

 

 

Prepare
Food:

 

 

           

 

 

 

 

 

 

Sequence Diagram of Supply Food

 

 

 

Sequence Diagram of Place Online Order :

 

 

 

 

 

 

Activity diagram of

Login:

 

 

 

 

 

 

 

 

 

 

 

 

3.6 Activity diagram of

Menu:

 

Activity diagram of

Search items:

 

Activity diagram of

Specific dish:

 

 

State Diagrams

 

3.7 State Diagram of
Customer

 

 

 

 

 

 

 

 

State Diagram of  Server

 

 

 

 

 

 

State Diagram of Order
Operation

 

4. DATA DESIGN

4.1 Data Description

3.3 Design Rationale

We
would like to design a system that is presented for everywhere. We also don’t
want to restrict the user to his/her for restaurant details. That’s why we use
mysql database to store data of users. We use PHP for this system. PHP is the
easy and understanding language and every user mostly like the PHP. The
application which is build is:

Ø  Platform Independent

Ø  Standards based system
application

Ø  Can easily be used

Ø  Database must be used to
store data

 

4.1.1 Data Object:

User:

User Id: Identity number given from the database for
each user. This attribute is unique for any user identification.

Name: User name for login.

Email: E-mail of the user that will be used for the
communication information.

Password: The user’s password.

Login:

User Id: id used for login.id represents uniqueness
of the user.

Country: user country name.

Province: use their province name for login.

Password: The user’s password.

City:  The
user city name.

Address:  The
user address.

 

Admin:

Admin Id: id of the Admin to uniquely identify any user of the site.

Email: E-mail of the admin that will be used for the
communication information.

Password: The admin password.

Product:

Product Id: product id identify unique product. This
attribute is unique for each product.

Product name: Name and surname of the product.

Password: The product password.

Product price: The price of the product.

Description: All description about product defines.

 

Menu:

Menu Id: menu id used for login and see menu. This
attribute is unique for each menu.

 Name: Name of
menu list.

Type: Different types of menu items are available in
Restaurant.

List: Different menu list are also available for
customer.

 

Order:

OrderId: identity number given from the database for
product order. This attribute is unique for each product order.

Date: The date of the order.

Time: The order time.

 

Alert:

Id: identity number given from the database for send
email alert.

Email: E-mail of the alert that will be used for the
communication information.

 

Payment:

Id: identity number given from the database for send
email alert.

Type: E-mail of the alert that will be used for the
communication information.

Pay-amount:

Amount: amount of the product.

 

4.1.2. Relationships and Complete
ER-Diagram:

Type

Id

Id

Name

List

Amount

Pay-amount

Payment

Type

Menu

 

 

4.2 Data Dictionary

User:

Parameter
Types:

ID:
Name:
E-mail:
                 Password:
 

Int
String
Varchar
Char
 

 

 

 

 

Login:

Parameter
Types:

ID:
Country:
                               Province:
                              Password:
City: 
 
Address
:
 

Int
String
String
Char
String
 
Char

 

 

 

 

Admin:

Parameter
Types:

Name:
ID:
E-mail:
Password:
 

String
Int
Char
Char
 

 

 

 

 

Product:

Parameter
Types:

 ID:
Name:
Password:
Price:
 
Description:
 

String
Int
Char
Char
String

 

 

 

 

 

 

 

Menu:

Parameter
Types:

ID:
Name:
Type:
                                   List:
 

Int
String
Varchar
Char
 

 

Order:

Parameter
Types:

ID:
Date:
Time:
 

Int
Char
Varchar
 

 

 

 

 

Alert:

Parameter
Types:

ID:
E-mail

Int
Char
 
 

 

 

 

Payment:

Parameter
Types:

ID:
Type:
Pay-amount
                                   Amount:
 

Int
String
Varchar
Char
 

 

 

5.
COMPONENT
DESIGN

In this
section, we take a closer look at what each component does in a more systematic
way. If Software Design Document you gave a functional description in section
3.2, provide a summary of your algorithm for each function listed in 3.2 in
procedural description language (PDL) or pseudocode. If you gave an OO
description, summarize each object member function for all the objects listed
in 3.2 in PDL or pseudocode. Describe any local data when necessary.

6.
HUMAN
INTERFACE DESIGN

6.1 Overview
of User Interface

Describe the
functionality of the system from the user’s requirements. Explain how the
userwill be able to use your system to complete all the expected features and
the feedbackinformation that
will be displayed for the user.

6.2 Screen
Images

Display
screenshots showing the interface from the user’s perspective. These can be handdrawnor you can use an
automated drawing tool. Just make them as accurate as possible.

(Graph paper works well.)

6.3 Screen Objects and Actions

6.3.1Main page of online
Restaurant system:

This
is the main page of restaurant system. Manager login, employer login and
customer logins are the links of the page.

 

 

 

6.3.2
User Sign in for Restaurant

Usergives his/her email id and password for sign in
restaurant and sees about restaurant.

 

 

 

 

 

 

 

 

 

6.3.3User Feedback       

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Online Reservations

 

 

 

 

 

 

 

Post Author: admin

x

Hi!
I'm Dora!

Would you like to get a custom essay? How about receiving a customized one?

Check it out