ACKNOWLEDGEMENT

We take this great opportunity to acknowledge

everyone who has been involved in the creation of
this project. We would firstly like to thank ------------
and ----------- for letting us this great opportunity to
test our skills through the creation of our project as
part our syllabus.

Our sincere thanks and gratitude should go

towards the Principal of our college --------- for their
kind co- operation and attention for the creation of
this project.

Special thanks must go to our college for

allowing us to develop our own ideas and creations
towards the development of our project.

Further, we wish to thank all Teachers, persons,

who knowingly or unknowingly helped us in
completion of this project.

If something is left inadvertently, we are

sorry for that. Thank you.

XYZ

1
 Index
[Link] Title Page no
1. INTRODUCTION
1.1 Introduction to System 03
1.2 Existing System 04
1.3 Proposed System 05
1.3.1 Objectives of System
1.3.2 Scope of System
1.3.3 Need of System

2. ANALYSIS 06
2.1 Feasibility Study 07
2.2 Fact Finding Technique 08
2.3 Hardware Requirement
2.4 Software Requirement
3. SYSTEM DESIGN
3.1 E-R Diagram
3.2 Data Flow Diagram
3.3 Data Dictionary
4. FORM DESIGN
4.1 Screen Shots
4.2 Reports
5. Limitation 34
6. Future Enhancement 35
7. Conclusion 36
8. Bibliography 37

2
 INTRODUCTIO
N

H
OTEL MANAGEMENT SYSTEM is being developed for smooth
running and easy management of hotel. As we normally visit the
hotel many times when we go for outings with family and friends
we observe that how the hotels are.

Then we actually met the receptionist of a hotel and interviewed him and
asked some questions which were required to make a software application
for a hotel. After Interviewing we got an idea what all content should be in
the hotel management software.

So we started to develop an application which can be implemented in hotel.

The system can be handled easily by the staffs working in particular hotel
without much knowledge.

3
 THE EXISTING SYSTEM

T
he current manual system uses paperwork . Booking is done by visit
to the hotel booking office. The guest’s personal details such as
Name, Age, Nationality, and Duration of stay, are the input during
booking in. And these details are maintained manually in a book.

The guest’s file is updated on daily basis if he takes some extra services
from hotel.

The receptionist generates the bills on daily basis for guest. During
checking out of guests, all the bills are generated a day before checkout
date. The guest receives their bills and pays if any balance remaining.

 LIMITATIONS OF AN EXISTING SYSTEM

1. Guest files can easily get lost or mix up with other guest
file documents.

2. Files occupy a large storage space

3. Unnecessary duplication of data.

4. Due to easy access to guest data by unauthorized users, guest data

is extremely unconfident.

5. Searching the guest records is extremely difficult.

6. Guest records are extremely difficult to modify since

modification generates dirty and unpresentable reports.

4
 The Proposed System
 OBJECTIVES OF THE PROPOSED SYSTEM
1. The Proposed System is a computerized system.
2. All records are stored in computer so the manual work is reduced.
3. Modification of data is easier that manual system.
4. Only authorized person can use the system.
5. Enable fast and easy retrieval of guest records and data for fast
reference activities.

 SCOPE OF THE SYSTEM.

The system will cover; booking, accommodation and accounts details.

Moreover, special services such as Laundry and room service will be
provided by the system also.
 NEED OF THE SYSTEM.
 The new system is computerized system.
 Maintenance of data is very easy and work load is reduced.
 The authorized person of the System can fetch the information of
hotel details very easily i.e. authentication is done before accessing
the system.

5
Analysis

6
 Feasibility Study
The objective of feasibility study is to determine whether or not the
proposed system is feasible. The feasibility is determined in term of
following aspects. These are:
 Technical Feasibility
 In this we checked, are we technically feasible to develop the
software using [Link] and SQL SERVER.
 As well as we checked, is the customer technically feasible
to use the software which we are going to develop.
 So considering the above two point’s feasibility study is done.
 As we have the knowledge of the [Link] and SQL server we
are technically feasible as well the customer needs not much
knowledge to handle the software therefore both are feasible.
 Economical Feasibility

 Economical Feasibility is to see how much the cost required

to make the software and is it feasible to make the software in
that cost.
 Also we checked from the customer point of view that, will it be
feasible for customer to buy the software.
 So it’s economically feasible to us, as the application we are
using to develop software is already available for us and as we
are only two people to develop the software no salary needed
to be given.

7
 Fact-finding Techniques

 Fact finding is the process of collection of data and information based

on techniques which contain sampling of existing documents,
research, observation, questionnaires, interviews and joint
requirements planning.
 We have used suitable fact-finding techniques to develop the system.

 Sampling of existing documentation

 Samples of reports.
 Samples of completed computerized system.

 Interview:
 Interview is the most commonly used technique to
collect information from the face-to-face interviews.
 We actually met the receptionist of a hotel and interviewed him
and asked some questions which were required to make a
software application for a hotel and made a written
documentation of it.

8
System Design

9
 E-R Diagram
NameSalary E_Id
Ph_no Name
E_Id
Salary Designation
Ph_no

m
Manager 1 fills details of Employees

IS A E_Id
Name
E_Id Name

1 E_Id
m Assigns workReceptionist
to
RoomBoy Security Man
m m 1 Name
1 1
1

Provides Provides
Charges ServiceName ServiceName
Does Manages Manages Does
m
Laundry Service m
Room ServiceCharges

m m m m
Booking CheckInOut Customer Cancellation
Given To Given To

GuestName
BookingDate CheckInDate
RoomNo
m m GuestId
RoomNo CheckOutDate
Rooms
CancellationDate

RoomNo Status

ChargesRoomType

10
 Data-Flow Diagram
1. Context-level diagram

Receiptionist
Customer
gives Bill Receipt
Check-Out

Confirm Booking Check Room Availibility

0.0
Does Booking
Does Booking
Does Check-In Pays Bills Management Confirm
Lodging System Check-In Does Check-Out Confirm Cance
Generate Bill

Reuest for Cancellation

Does Cancellation

Check Room Availibility Manages Employee

Room Manager

11
 2. First-Level DFD

Manager Room Details Room_Master

Employee Details Employee_Master

New Reservation CheckInOut Details

System Admin Room_Reservation_trans
Cancellation Details Saves
Check_In_Out_Trans

Payment Details Cancellation_Trans

Payroll_Trans

Manager Customer Details

Guest_Master

New Reservation CheckInOut Details

Cancellation Details Room_Reservation_trans
Booking
Saves
Check_In_Out_Trans

Cancellation_Trans

Laundry Service Saves

Laundry_Service_Trans
Room Service Services
Room_Service_Trans

Room_Master

Generates Report Employee_Master

Reports Refers Room_Reservation_trans Check_In_Out_Trans

Gives Report
Laundry_Service_Trans

Room_Service_Trans

Cancellation_Trans

PayRoll_Trans

12
 3. Second-Level DFD

Manager

1.1
Employee Details
Saves
Salary Payroll_Trans
Payment Details

1.2

Room Details Saves

Room Room_Master

Receiptionist

2.1
New Reservation Details
Saves
Booking Room_Reservation_Trans

2.2

Check In/Out Details Saves

Check_In/Out Check_In_Out_Trans

2.3
Cancellation Details Saves
Cancellation Cancellation_Trans

2.4
Billing Details
Saves Check_In_Out_Trans
Billing

13
Receiptionist

3.1

Laundry Service Details Saves

Laundry Service Laundry_Master

3.2

Laundry Billing Saves

Laundry Billing Laundry_Service_Trans

3.3

Room Service details Saves

Room Service Room_Service_Master

3.4

Room Service Billing Details Saves

Room Service Billing Room_Service_Trans

14
 Data
Dictionary

15
1) Name :- CANCELLATION_TRANS

Field Name Data Size Constraints Description

Type
CNL_NO Int 4 Primary Key Cancellation
Number
GUEST_ID Int 4 Foreign Key Guest Id
CNL_DATE Datetime 8 Not Null Cancellation
Date
BOOKING_DATE Datetime 8 Not Null Booking Date
ROOM_NO Int 4 Foreign Key Room
Number

2) Name :- CKECK_IN_OUT_TRANS

Field Name Data Type Size Constraints Description

TRANS_NO Int 4 Primary ey Transaction
Number
GUEST_ID Int 4 Foreign Key Guest Id
GENDER Int 4 Not Null Gender
PIN_CODE Int 4 Not Null Pin Code
EMAIL_ID Text 16 Allow Null Email Id
ALTERNATE_NO Text 16 Allow Null Alternate
Mob
Number
PROOF_CODE Int 4 Foreign Key Id Proof
Name
ID_NUMBER Int 4 Not Null Id Number
DSG_CODE Int 4 Foreign Key Designation
Code
ROOM_NO Int 4 Foreign Key Room No
CHECK_IN_DATE Datetime 8 Not Null Check In
Date
NO_OF_CHILDRENS Int 4 Not Null Number of
Children
NO_OF_ADULTS Int 4 Not Null Number of
Adults
TOTAL_CHARGES Int 4 Not Null Total
Charges
ROOM_CHARGES Int 4 Not Null Room
Charges
CHECK_OUT_STATUS Int 4 Not Null Check Out
Status
CHECK_OUT_DATE Datetime 8 Not Null Check Out
Date

16
3) Name :- DESIGNATION_MASTER

Field Name Data Type Size Constraints Description

DSG_CODE Int 4 Primary Key Designation
Code
DSG_NAME Text 16 Not Null Designation
Name

4) Name :-EMPLOYEE DESIGNATION

Field Name Data Type Size Constraints Description

DSG_CODE Int 4 Primary Key Designation
Code
DSG_NAME Text 16 Not Null Designation
Name

5) Name :-EMPLOYEE_MASTER

Field Name Data Type Size Constraints Description

EMPLOYEE_ID Int 4 Primary Key Designation
Code
EMPLOYEE_NAME Text 16 Not Null Designation
Name
GENDER Int 4 Not Null Gender
BLOOD_GROUP nchar(5) 10 Not Null Employee
Blood Group
ADDRESS nchar(50) 100 Not Null Employee
Address
CITY nchar(20) 40 Not Null City
CONTACT_NO nchar(15) 30 Not Null Contact No.
EMAIL nchar(20) 40 Allow Null Email Id
DSG_CODE Int 4 Foreign Key Designation
Code
DATE_OF_JOINING Datetime 8 Not Null Date of
Joining
BASIC_SALARY Float 8 Not Null Basic Salary
STATUS Int 4 Not Null Active
Status

17
6) Name:- GUEST_MASTER
Field Name Data Type Size Constraints Description
GUEST_ID Int 4 Primary Key Guest Id
GUEST_NAME nchar(30) 60 Not Null Guest Name
GUEST_ADDRESS nchar(50) 100 Not Null Guest
Address
CONTACT_NO nchar(13) 26 Not Null Contact No.

7) Name:-ID_PROOF_MASTER

Field Name Data Type Size Constraints Description

PROOF_CODE Int 4 Primary Key Id Proof
Code
PROOF_DESC Text 16 Not Null Id Proof
Description

8) Name:-ITEM_MASTER

Field Name Data Type Size Constraints Description

ITEM_NO Int 4 Primary Key Item No.
ITEM_NAME nchar(20) 40 Not Null Item Name

9) Name:-LAUNDRY_MASTER

Field Name Data Size Constraints Description

Type
LAUNDRY_NO Int 4 Primary Key Id Proof
Code
LAUNDRY_NAME nchar(30) 60 Not Null Laundry
Name
ADDRESS_WITH_CONTACT nchar(50) 100 Not Null Laundry
Address
with
Contact No.

18
10) Name:-LAUNDRY_SERVICE_MASTER

Field Name Data Size Constraints Description

Type
SERVICE_NO Int 4 Primary Key Laundry Service
No.
SERVICE_NAME Nchar(20) 40 Not Null Laundry Service
Name
CHARGES Float 8 Not Null Laundry Service
Charges

11) Name:-LAUNDRY_SERVICE_TRANS

Field Name Data Size Constraints Description

Type
TRANS_NO Int 4 Primary Key Laundry Service
No.
ORDER_NO Int 4 Not Null Laundry Service
Name
ORDER_DATE Datetime 8 Not Null Laundry Service
Charges
SR_NO Int 4 Not Null Transaction Serial
No.
SERVICE_NO Int 4 Foreign Key Laundry Service
No.
ITEM_NO Int 4 Foreign Key Laundry Item No.
ITM_QTY Int 4 Not Null Laundry Item Qty.
GUEST_ID Int 4 Foreign Key Guest Id
ROOM_NO Int 4 Not Null Room No.
LAUNDRY_NO Int 4 Foreign Key Laundry No.

12) Name:-MONTH_MASTER

Field Name Data Size Constraints Description

Type
MTH_CODE Int 4 Primary Key Month Code
MONTH Nchar(10) 20 Not Null Month Name
MTH_DAYS int 4 Not Null Days in Month

19
13) Name:-PAYROLL_TRANS

Field Name Data Size Constraints Description

Type
PAY_NO Int 4 Primary Key Payment No.
PAY_DATE Datetime 8 Not Null Payment Date
EMPLOYEE_ID Int 4 Foreign Key Employee Id
MTH_CODE Int 4 Foreign Key Month Code
YR_CODE Int 4 Foreign Key Year Code
DAYS_ATTEND Int 4 Not Null Days Attended

14) Name:-ROOM_MASTER

Field Name Data Size Constraints Description

Type
ROOM_NO Int 4 Primary Key RoomNo.
TYPE_ID int 4 Foreign Key Room Type
PERSONS_ALLOWED Int 4 Not Null Allowed
persons/Room
STATUS Int 4 Not Null Availibilty Status

15) Name:-ROOM_RESERVATION_TRANS

Field Name Data Size Constraints Description

Type
TRANS_ID Int 4 Primary Key Transaction Id
GUEST_ID Int 4 Foreign Key Guest Id
TRANSACTION_DATE Datetime 8 Not Null Transaction
Date
BOOKING_DATE Datetime 8 Not Null Booking Date
TYPE_ID Int 4 Foreign Key Room Type Id
ROOM_NO Int 4 Foreign Key Room No.
NO_OF_DAYS Int 4 Not Null No of Booking
Days
NO_OF_PERSONS Int 4 Not Null No. of Persons
for Room
CHECKIN_STATUS Int 4 Not Null Room
Availability
Status

20
16) Name:-ROOM_TYPE_MASTER

Field Name Data Size Constraints Description

Type
TYPE_ID Int 4 Primary Key Room Type Id
ROOM_TYPE Nchar(20) 40 Not Null Room Type
CHARGES Float 8 Not Null Room Charges

17) Name:-YEAR_MASTER

Field Name Data Size Constraints Description

Type
YR_CODE Int 4 Primary Key Year Code
YEAR int 4 Not Null Year

18) Name:-ROOM_SERVICE_MASTER

Field Name Data Size Constraints Description

Type
SERVICE_NO Int 4 Primary Key Year Code
SERVICE_NAME Nchar(20) 40 Not Null Year
CHARGES Int 4 Not Nll Room Service
Charges

19) Name:-ROOM_SERVICE_TRANS

Field Name Data Size Constraints Description

Type
TRANS_NO Int 4 Primary Key Transaction No.
SERVICE_DATE Datetime 8 Not Null Room Service Date
GUEST_ID Int 4 Foreign Key Guest Id
ROOM_NO Int 4 Not Null Guest Room No.
SERVICE_NO Int 4 Primary Key Year Code

21
Form Design

22
 Lodging Management System- Main Menu Form

 Room Type Entry

23
 Room Master Entries

 Customer Information Entries

24
 Laundry Detail Entries

 Laundry Service Entries

25
 Room Service Entries

 Room Reservation Entries

26
 Check In/Out Entries

 Cancellation Entries

27
 Room Services Entries

 Laundry Services Entries

28
 Employee Entries

 Employee Payroll

29
 Guest Master Report

 All Employee Report

 Room Reservation Report

30
 Date Wise Reservation Report

 Guest Wise Reservation Report

 Room Type Master Report

31
 Room Master Report

 Room Service Report

32
 Laundry Master Report

 Laundry Service Report

33
 Limitations of Proposed System

No system can be referred as complete system in all aspects. In spite of

successful executions of testing plan .The problem arises, when the system
is input in the real working environment, the problem that will arise cannot
be visualized and their solution cannot be predetermined to be rectified.

Limitations:

 The designed product is standalone system.

 Online Process is not done.

34
 Future Enhancement
Future scope of the Project:

 Can be a web based system in future.

 Improving system security.
 Improving data backup facility.
 The Customers can be able to Book Rooms online.
 The Customers can make their cancellation of Booked Rooms
online.
 The Customers can make payment online using credit, debit
cards, etc.

35
 Bibliography

 References :


 Text-Book References :

36