Presentation on

Miniproject
Cyber Hotelier

Mahaveer Institute of Science & Technology

L. RajaSekhar
07E35A1201
IT IV Year

K. Mahesh Kumar
06E31A1218
IT IV Year.

Cyber Hotelier

Introduction
Past Decades
Semi-automated System
Proposed System
Requirements
Design
Snapshots
Conclusion.

Introduction

 A literature survey is carried out in

the initial phase of the project. The
basic process is divided into two
steps.
1. Understanding the Existing
system.
2. Features of proposed system.

Cyber Hotelier

Introduction
Past Decades
Semi-automated System
Proposed System
Requirements
Design
Snapshots
Conclusion.

Past Decades
There existed only manual system.
Manual system involves paper work in the
form of maintaining various files and manuals.
Reservation, Billing, Cancellation, Maintenance
is a Manual process and a lot of risk involved.

Cyber Hotelier

Introduction
Past Decades
Semi-automated System
Proposed System
Requirements
Design
Snapshots
Conclusion.

Next

Semi-automated

Semi-automated system is a stand alone

system or a LAN based system
Booking is in the form of e-mail.
Email contains the requested booking dates and the number of rooms required, along with the
customer contact details.

Disadvantages of Manual Process

Time consuming.

No instantaneous updates of i. room status.

ii. user details.

Communication was not clear.

risk of loosing it easily.

Authentication and authorization.

No validations.

Disadvantages of Semi-automated
Sys.
Reservation through email.
Room amendment is not an easy task.

Cyber Hotelier

Introduction
Past Decades
Semi-automated System
Proposed System
Requirements
Design
Snapshots
Conclusion.

Proposed System
Some system is required to know about
the hotel information and can reserve
rooms throughout the globe irrespective of
the location.
Cyber Hotelier is a web-based system
focusing on automating the hotel
management system and providing room
reservations through online.

Project Model
Our project follows Waterfall Model.
It is divided into 6 phases.
1. Requirements phase.
2. Analysis phase.
3. Design phase.
4. Coding phase.
5. Testing phase.
6. Deployment phase.

Cyber Hotelier

Introduction
Past Decades
Semi-automated System
Proposed System
Requirements
Design
Snapshots
Conclusion.

Requirements customer
perspective:

Registration.
Reservation: Online and Central.
Cancellation.
Services.
Restaurant.
Billing.

Software Requirements
OS
ServicePack
Windows NT4.6
6
Windows 2000
Windows XP
Windows 2003

4
2
1

Microsoft visual studio 2005.

Front End
Back End

(ASP. Net with c# language)

SQL server 2000

Hardware Requirements
Processor
Primary Memory (RAM)
512 SD
Secondary Memory (Hard Disk)
Monitor
(Color)
Keyboard
Standards
Mouse
Compatible

: P3+ or AMD
: 256 MB or
: min 10 GB
: VGA
: 105
: Any

Cyber Hotelier

Introduction
Past Decades
Semi-automated System
Proposed System
Requirements
Design
Snapshots
Conclusion.

Design
Object oriented design
The UML language is for
Visualizing
Specifying
Constructing
Documenting.

Class Diagram
guest
name
address
fromdate
todate
phoneno
email
username
password

house keeping executive

restaurant manager

username
password

billno
username
password
bill generated()
process the request()
forward the request()

ask for room address()

allot room()
forward bill()

1..n
1..n

1..n

Administrator
username
password

1..n

receptionist
username
password
process is generated()
bill is requested()
request for food service()
request for cleaning()
request for other services()
forward the bill()
login successful()
check in()
check out()
submit details()
prepares the final bill()

check the stock availability()

purchase order is palced()
outward generation is completed()
submits the inventory details()
login successful()

1..n

Open registration()
login()
verify password()
Submission the form()
Check the details()
Allot the manager id()
Open registration()
Submission the form()
Check the details()
Allot the Housekeeping id()
allot receptionist id()
allot guest id()
request for modification()
request for cancellation()
1

administrator interface
start interface()
login()
room enquiry()

Registration form
name
address
phoneno
email
username
password
start interface()

Interfaces
user interface

Manager

start interface()

username
password
Issue the form()
Fill the form()
Forward id()

frontdesk interface
start interface()

Reservation form
start interface()

Use case Diagram

Registration/Login

Reserv ation
administrator

Manager

cancellation/Modif ication

Serv ices

Receptionist

Front-desk

Restaurant

Guest
Billing

Check Report

House keeping

Inv entory

HouseKeeping
Executiv e

Service
phon

Status

Dept

Date

email

addres
name

Room no

Ref no.
Guest

Amount
Room service

Request

Reservation

Makes

Ref no
Pays

todate

room type

Fromdat
advance

Payment

Room no

room no

Payment mode
Total due

Bill no
Paid amount

Payment date

ER DIAGRAM

Cyber Hotelier

Introduction
Past Decades
Semi-automated System
Proposed System
Requirements
Design
Snapshots
Conclusion.

Home page:

Login page:

Registration page:

User Login page:

Room Reservation page:

Room Reservation page: (contd)

Receptionist Login page:

Guests Information page:

Receptionist Login page:

House Keeping Executive Login Page:

Manager Login page:

Admin Registration page:

5.4. DATA BASE DESIGNS

5.4.1 Login Details Table:
Column
Name

Data Type

Constraints

Username

Varchar(50)

Primary key

Password

Varchar(50)

Not null

Roles

Varchar(50)

Not null

5.4.2 Registered Users Table:

Column
Name

Data type

Constraints

Username

Varchar(50)

Primary key

Password

Varchar(50)

Not null

Dob

Varchar(50)

Not null

Email

Varchar(50)

Not null

Address

Varchar(MAX)

Not null

Phone

Varchar(50)

Not null

Secques

Varchar(50)

Not null

5.4.3 Room Details Table:

Column
Name

Data Type

Constraints

Roomno

Varchar(50)

Primary key

Floor

Varchar(50)

Not null

Roomtype

Varchar(50)

Not null

Charge

Float

Not null

Status

Varchar(50)

Not null

5.4.4 Guest Information Table:

Column Name

Data type

Constraints

Refno

Int

Primary key

Name

Varchar(50)

Not null

Address

Varchar(MAX)

Not null

Phone

Varchar(50)

Not null

Mobile

Varchar(50)

Not null

Email

Varchar(50)

Not null

Camefrom

Varchar(50)

Not null

Goingto

Varchar(50)

Not null

Adults

Int

Not null

Child

Int

Not null

Cyber Hotelier

Introduction
Past Decades
Semi-automated System
Proposed System
Requirements
Design
Snapshots
Conclusion.

Conclusion
Reduces the manual work & minimizes time.
The system is secured as it provides restricted
access to various user types by authentication .
We expect in future to implement this system in
wireless Communication.
Ex: In Mobiles.

-----Queries??