Final Report Document

Abstract
This is the final report document for developed hotel management system for Gayana hotel
Tangalle.It consists of the milestones in development of finalized hotel management system.
As previously mentioned current manual system used by hotel, caused for decrement in growth
of success and efficiency of the hotel.
Iterative waterfall method was used as the software development life cycle. Coding was handled
through an Object-oriented approach. Above mentioned methodologies made project work load
light and provided the ease of developing. The system was evaluated by several people regarding
user levels of the developed system. Results of the evaluation helped for further maintenance of
the product. Fully functional Gayana Hotel Management System will fulfil the main objectives
and all the events of the hotel.
Project Report
Acknowledgement
We would like to express our very great appreciation to our supervisor Ms. K.B.A.B.Chathurika
for her valuable and constructive suggestions during the planning and development of this
project. Her willingness to give her time so generously has been very much appreciated. Advice
given by other academic lecturers has been a great help in building the software solution.
Also we obliged to staff members of Gayana hotel, for the valuable information provided by
them in their respective fields. We are grateful for their cooperation during the period of
developing the system
Assistance provided infinity software development crew was greatly appreciated. Their
contribution was worth a lot, in making this development a reality
Project Report
ii
Declaration
We declare that the this project report or part of it was not a copy of a document done by any
organization, university any other institute or a previous student project group at SLIIT and was
not copied from the Internet or other sources.
Project Details
Project Title
Hotel Management System
Project ID
ITP-14-MTR-03
Group Members
Reg. No
IT13117474
Name
IT13128050
Prasad Lakmal D.H.

Madushanka A.S.S.
IT13118082
Charitha D.G.
IT13118150
Wijesinghe A.M.
IT13087234
Piumal Dinuka W.
IT13060954
Ranathunga B.S.
IT13110062
Shyamal W.A.I.
Project Report
Signature
iii
Table of Contents
Abstract ........................................................................................................................................... i
Acknowledgement ......................................................................................................................... ii
Declaration.................................................................................................................................... iii
Table of Contents ......................................................................................................................... iv
List of Figures .................................................................................................................................v
List of Acronyms and Abbreviations ...........................................................................................v
1. Introduction ..............................................................................................................................1
1.1
1.2
1.3
Problem Statement....................................................................................................................... 1
Product Scope .............................................................................................................................. 3
Project Report Structure .............................................................................................................. 3
2. Methodology .............................................................................................................................4
2.1
2.2
2.3
2.4
Requirements and Analysis ......................................................................................................... 4

Design .......................................................................................................................................... 6
Implementation ............................................................................................................................ 8
Testing ....................................................................................................................................... 25
3. Evaluation ...............................................................................................................................26
3.1
3.2
3.3
Assessment of the Project results .............................................................................................. 26

Lessons Learned ........................................................................................................................ 27
Future Work .............................................................................................................................. 27
4. Conclusion ..............................................................................................................................28
5. References ...............................................................................................................................29
Appendix A: Design Diagrams ...................................................................................................30
Appendix B: Test Results ............................................................................................................47
Project Report
iv
List of Figures
Figures
Page
2.1.1. Use Case Diagram..
2.2.1 ER Diagram.................................................
List of Acronyms and Abbreviations
H.M.S. Hotel Management System
Project Report
ITP-14-MTR-03 Hotel Management System
1. Introduction
1.1 Problem Statement
Currently Gayana hotel is using a manual system to handle hotel processes. When a guest make a
reservation, all the reservation details (including guest details) are recorded in a file and those files
are stored in a special cabinet. Calculations of bills and inventory items are done by manually too.
As the current system is a file based one, management of the hotel has to put much effort on
securing those files. They can be easily get damaged by a fire, insects or even by a natural disaster
like tsunami. Keeping files takes much time and wastes much precious man hours. Although we
cant trust the accuracy of calculations done by manually, its not a surprise of encountering
problems. If we want to check for a previous room record or a reservation detail, management will
be in a great problem. Its a tough and time taking process to search for a record in a file
If we summarize all the drawbacks of manual hotel management system we can mention as follows
It is much time consuming.
Often the data are lost and the employee or manager is not aware of this.
Lots of Manual labor is required for manual record keeping.
Data is not always reliable as it is hand written and some human errors might have occurred
example wrong telephone number among other.
Difficulty of searching and retrieving records.
Slow process of reservation.
Low in security.
Files are prone to theft unauthorized modification due to low data security levels and
standards.
Retrieval of guest records is extremely difficult.
Above mentioned teasers caused for the decline of efficiency of the hotel and caused for many
inconveniences in performing daily tasks at hotel.
Project Report
The manual handling of hotel management system has always been a difficult task.
Administering the smallest of the requirements of the guests to the basic needs the Hotel
Management System have to put a lot of energy in controlling and executing the day-today work
along with the miscellaneous items? However, the introduction of the hotel management software
has diminished the possibilities of error and limitation of the staff to provide a specific service on
any given time
Project Report
1.2 Product Scope
The introducing software, Hotel Management System which is implemented for Hotel Gayana will
automate the major operations of the hotel. The Reservation System is to keep track in room and
hall reservation and check availability. The Room Management System is for manage all room types
room services. The Inventory Control System will keep track in all inventories of the hotel and guest
details will handled by guest management. Administration department will monitor the all .There is
three End Users for HMS. The End Users are Owner, Manager and Receptionist. Owner can access
to all system functionalities without any restrictions. Manager can access to all system
functionalities with limited restrictions. Receptionist can only access to the Reservation
management section. To keep restrictions for each End User levels HMS can create different Login
functions
1.3 Project Report Structure

This project report for the creation of the system for Gayana hotel management system is completely
designed according to the standards of IEEE, document standards. It will give the reader a friendlier
environment to understand the content of it. If this project is used for further development in the
future, this kind of document standard will also give a perfect approach to the development team
also, to understand the system well and work of the modifications they want to achieve.
Project Report
2. Methodology
2.1 Requirements and Analysis
Requirement gathering in the particular project was mainly done through conducting interviews
with different kinds of people of management hierarchy of the company. Though most of the
information were gathered from the interviews from the owner, the developing team conducted few
interviews with the hotel staff members of different levels to get a wide idea of the company. In this
situation, they were enthusiastic and supported us by giving relevant information. Referring to
previous hotel records was another way to gather requirements of hotel. Formal system is well
defined by the forms, reports, policy manuals and organization charts. Above mentioned tactic
helped a lot in providing a clear view of the hotel management system. Majorly we found the users
of the system after interviews. It promote the user roles of the system. Intention of building the
system was clearly understood after this phase of software life cycle. Further analysis revealed
where and when the system will be used.
After gathering and analyzing the client requirement it was expressed by a use case and the rest of
the development process was built on it.
Project Report
2.1.1. Use Case Diagram
Project Report
2.2 Design
Project was designed using an object oriented approach. While developing the system we had to
come across several diagrams in order to achieve the quality of the software product. After creating
the ER diagram it was mapped to a relational schema and normalized. Finally the database was
created. Class diagram was designed with class stereotypes which included with relationships. Class
diagram helped in programming the solution.
Project Report
2.2.1 ER diagram
Project Report
2.3 Implementation
Database was created using MS sql server studio express 2008 which consist of the capability of
producing results table efficient than the older versions. When we consider about c# coding of the
project DbAccess class was created in gathering objects from the database. Redundancy of code
Part belongs to making connection with the database, was reduced by creating data returning
methods inside DBAccess class. It provided the gateway of windows form to access system
database.
public class DbAccess
{
//when programmer wants to update insert delete values------------------------------------------public static int sqlQuery(String query)
{
SqlConnection conn = new SqlConnection();
conn = ConnectionManager.GetConnection();
SqlCommand cmd = new SqlCommand(query);
cmd.CommandType = CommandType.Text;
cmd.Connection = conn;
conn.Open();
return cmd.ExecuteNonQuery();
}
//Retrieve dataset--------------------------------------------------------------------------------public static DataSet DatasetRetrive(string query)

{
SqlConnection con = ConnectionManager.GetConnection();
DataSet Ds = new DataSet();
Project Report
con.Open();
SqlCommand newCmnd = new SqlCommand();
SqlDataAdapter DtAdapter = new SqlDataAdapter(newCmnd);
DtAdapter.Fill(Ds, "Answer");
con.Close();
return Ds;
}
//Get a datareader-------------------------------------------------------------public static SqlDataReader sqlreader(string query)

{
try
{
SqlCommand cm = new SqlCommand();
SqlConnection conn = ConnectionManager.GetConnection();
cm = new SqlCommand(query, conn);
SqlDataReader dr;
dr = cm.ExecuteReader();
return dr;
}
catch (Exception ex)
{
return null;
}
Project Report
A separate class was created to handle validations of the system. User inputs values can be passed
into validation methods inside validation class instead of reusing code again and again.
public class Validations

{
bool invalid = false;
//to validate whether user input is a valid email address
public bool IsValidEmail(string strIn)
{
invalid = false;
if (String.IsNullOrEmpty(strIn))
return false;
// Use IdnMapping class to convert Unicode domain names.
strIn = Regex.Replace(strIn, @"(@)(.+)$", this.DomainMapper);
if (invalid)
return false;
// Return true if strIn is in valid e-mail format.
return Regex.IsMatch(strIn,
@"^(?("")(""[^""]+?""@)|(([0-9a-z]((\.(?!\.))|[!#\$%&'\*\+/=\?\^`\{\}\|~\w])*)(?<=[0-9a-z])@))" +
@"(?(\[)(\[(\d{1,3}\.){3}\d{1,3}\])|(([0-9a-z][-\w]*[0-9a-z]*\.)+[a-z0-9]{2,17}))$",
RegexOptions.IgnoreCase);
}
//to validate whether user input is a valid phone number
public bool IsValidPhone(string strIn)
{
invalid = false;
return false;
Project Report
10
if (invalid)
return false;
@"^\d{10}$",
}
//to validate whether user input is a valid NIC number
public bool IsValidNIC(string strIn)
{
invalid = false;
return false;
if (invalid)
return false;
@"^[1-9]\d{8}[vV]$",
}
private string DomainMapper(Match match)
{
// IdnMapping class with default property values.
IdnMapping idn = new IdnMapping();
string domainName = match.Groups[2].Value;
try
{
domainName = idn.GetAscii(domainName);
}
catch (ArgumentException)
Project Report
11
{
invalid = true;
}
return match.Groups[1].Value + domainName;
}
}
After examining the ER diagram system database developed
List of Tables
Guest
create table guest(
membercode
name
company
gender
e-mail
varchar(10),
varchar(50),
char(50),
char(10),
varchar(20),
constraint pkguest primary key(membercode)

);
2.3.1. Guest
GuestPhone
create table guestphone(
memcode
phone
varchar(10),
int,
constraint pkguestphone primary key(memcode),

constraint fkguestphone foreign key(memcode) references guest(membercode)
);
Project Report
12
2.3.2. GuestPhone
Room
create table room(
roomno
name
buildingno
floorno
status
roomtype
varchar(10),
char(50),
int,
int,
char(10),
varchar(15),
constraint pkroom primary key(roomno),

constraint fkroom foreign key(roomtype) references roomtype(name)
);
2.3.3. Room
RoomType
create table roomtype(
name
descriptions
status
standard_price
Project Report
varchar(15),
varchar(50),
char(10),
money,
13
single_price
adults
children
extraadult
money,
int,
int,
int,
constraint pkroomtype primary key(name)

);
2.3.4. RoomType
Reserve
create table reserve(
membercode
roomno
code
checkin
checkout
no_of_nights
children
adults
status
varchar(10),
varchar(10),
int,
datetime,
datetime,
int,
int,
int,
char(10),
constraint pkreserve primary key(membercode,roomno),

constraint fkreserveguest foreign key(membercode) references guest(membercode),
constraint fkroomnoroom foreign key(roomno) references room(roomno)
);
Project Report
14
2.3.5. Reserve
Services
create table services(
code
name
rate
type
catid
varchar(10),
char(20),
int,
char(20),
varchar(10),
constraint pkservices primary key(code),

constraint fkservices foreign key(catid) references service_category(catid)
);
2.3.6. Services
ServiceCategory
create table service_category(
catid varchar(10),
name char(20),
status char(10),
Project Report
15
constraint pkcategory primary key(catid)

);
2.3.7. ServiceCategory
Bill
create table bill(
billing_no
date
quantity
price
taxes
units
service
empid
membercode
int,
datetime,
int,
money,
money,
int,
varchar(10),
varchar(10),
varchar(10),
constraint pkbill primary key(billing_no),

constraint fkbillemp foreign key(empid) references user(empid),
constraint fkbillguest foreign key(membercode) references guest(membercode)
);
2.3.8. Bill
Project Report
16
User
create table user(
empid
username
password
type
varchar(10),
char(20),
varchar(10),
char(15),
constraint pkuser primary key(empid),

constraint fkstaff foreign key(empid) references employee(empid)
);
2.3.9. User
Staff
create table staff(
empid
occupation
varchar(10),
char(20),
constraint pkstaff primary key(empid),

constraint fkstaff foreign key(empid) references employee(empid)
);
Project Report
17
2.3.10. Staff
Employee
create table employee(
empid
name
department
type
email
sex
varchar(10),
char(20),
char(20),
char(15),
varchar(20),
char(6)
constraint pkemployee primary key(empid)

);
2.3.11. Employee
EmployeePhone
create table employeephone(
empid
phone
varchar(10),
varchar(10),
constraint pkempphone primary key(empid),
Project Report
18
constraint fkempphone foreign key(empid) references employee(empid)

);
2.3.12. EmployeePhone
Event
create table event(
code
type
date
membercode
varchar(10),
char(10),
datetime,
varchar(10),
constraint pkevent primary key(code),

constraint fkevent foreign key(membercode) references guest(membercode)
);
2.3.13. Event
Project Report
19
Properties
create table properties(
itemcode
item_name
quantity
unit_price
varchar(10),
char(20),
int,
money,
constraint pkproperty primary key(itemcode),

);
2.3.14. Properties
ReusableProperties
create table reusable_property(
itemcode
remaining_period
varchar(10),
int,
constraint pkreproperty primary key(itemcode),

constraint fkproperty foreign key(itemcode) references properties(itemcode)
);
2.3.15. ReusableProperties
Project Report
20
Task
create table task(
taskid
status
assign_date
finished_date
varchar(10),
char(10),
datetime,
datetime,
constraint pktasks primary key(taskid)

);
2.3.16. Task
StaffAssignToEvent
create table staff_assignto_event(
empid
code
varchar(10),
varchar(10),
constraint pkstaff_assignto_event primary key(empid,code),

constraint fkstaff_eventcode foreign key(code) references event(code),
constraint fkstaff_assign foreign key(empid) references staff(empid)
);
Project Report
21
2.3.17. StaffAssignToEvent
GuestRequestServices
create table guest_reserve_room_services(
code
varchar(10),
roomno
varchar(10),
membercode varchar(10),
constraint pkguest_reserve primary key(code,roomno,membercode),
constraint fkguest_reerve foreign key(membercode) references guest(membercode),
constraint fkguest_reserve_room foreign key(roomno) references room(roomno),
constraint fkguest_reserve_roomsrevices foreign key(code) references services(code)
);
2.3.18. GuestRequestServices
Project Report
22
RoomProperties
create table guest_reserve_room_properties(
itemcode
varchar(10),
roomno
varchar(10),
constraint pkguest_reserve_prop primary key(itemcode,roomno,membercode),
constraint fkguest_reerve_prop foreign key(membercode) references guest(membercode),
constraint fkguest_reserve_room_prop foreign key(roomno) references room(roomno),
constraint fkguest_reserve_rooms_prop foreign key(itemcode) references properties(itemcode)
);
2.3.19. RoomProperties
RoomTask
create table guest_reserve_room_tasks(
taskid
varchar(10),
roomno
varchar(10),
constraint pkguest_reserve_task primary key(taskid,roomno,membercode),
constraint fkguest_reerve_task foreign key(membercode) references guest(membercode),
constraint fkguest_reserve_room_task foreign key(roomno) references room(roomno),
constraint fkguest_reserve_rooms_tasks foreign key(taskid) references task(taskid)
);
Project Report
23
2.3.19. RoomTask
Project Report
24
2.4 Testing
Testing was done in several steps of the software development process. The very 1st testing scenario
done was unit testing at the very beginning done by the developer. The designing of H.M.S. was
divided into several departments depending on the work covered on them. And in a single
department 1 or two developers worked to achieve the individual goals in them which supports to
the goals of the overall system. These departments were divided as much as independent from each
other and that made a huge impact on the testing process to make it easy. Several testing scenarios
were conducted within each department by the working developers in them.
In the testing process of the system we followed many types of testing methods that are followed
when a system is implementing. First we followed Black Box testing to get an idea about the
functions that should be included in the system to meet the requirements we gathered from the
Hotel.
In there we didnt have any core knowledge about them initially. After the implementation of every
function we had to do the White Box testing to confirm whether the particular function is working
or not. This testing helped us to identify the bugs and errors of the inbuilt functions of those
incidents. We have done several Performance Testing to check whether the system is capable of
working at the clients company environment. We checked each and every function of the
departments that we have classified with the Unit Testing to identify whether those functions are
applicable for the features of that department.
With the completion of the final system we did the System Testing, the testing that estimated the
ultimate state of the product as a whole. Here also we did the modifications as necessary to reduce
the bugs and errors.
As the final Testing of the System we implemented, we have to do the Acceptance Testing after
handing over the system to the client. In this system also we will have to be able to do the
modifications as required by the client accordingly. The maintenance also will require all these test
results in future to make the project a complete one
Project Report
25
3. Evaluation
3.1 Assessment of the Project results
Assessing of the project was done by a panel formed by the Academic section of SLIIT Matara
Center. Our Supervisor Ms. K.B.A.B.Chathurika, provided us with the relevant guidelines
throughout the development process. Several presentations were scheduled at several milestones
such as Proposal Presentation, Prototype Presentation and Final Presentation to assess the
progress or the development of the project. Most of the steps that we took were recorded in the
documents that we have created and those reports were evaluated by our Supervisor Ms.
K.B.A.B.Chathurika. She advised us to do the modifications as necessary. The presentations
mentioned above gave us the chance to present the development of the project time to time and
those works were observed by a panel of lecturers and those observations resulted us to follow the
standards of the project as much as we could.
Strength
The system provide login authorization feature to prevent unauthorized user login into the
Hotel Management System
All the date that inserted to database are fully validated to ensure the accuracy of information
H.M.S. is user-friendly and easy to use.
Database backup and security.
Weaknesses
Requirement of a web application
Project Report
26
3.2 Lessons Learned

There were lots of lessons that we learned from throughout the time we spent for developing this
project. Most importantly we learned to work according to a time schedule and how to manage the
time to take the maximum benefit of the time we had. We faced lot of inconveniences while
engaging with the project development and those incidents gave us the experiences of facing the
problems and finding the appropriate solutions as necessary. This group project also let us to get the
experience of working as a team and how to do it with a team spirit. We were molded with the
advices given by the lecturers with every comment they gave.
There were lot of experiments that we did to get on to a better out come and those things impacted
us to collect new things in to our knowledge as well as to our lives.
3.3 Future Work

The work in the future that we have to engage should be done with lessons we learned from the
project work that we have done so far. The steps that we have to be taken should be included with a
higher standard than the tasks we did in the past. We should be able to reduce the errors that we
have identified all through the time we spent for the project and that should be included with the
experiences we gathered but with a high standard.
Developing a web application will be scheduled for future. A web application could provide the
ease of making reservations for the guest at any time. We would hope to begin it as soon as possible.
The next step of the project is, handing over the system to the client. After that we have to consider
about the maintenance part of the project accordingly. Here we should still be able to do the
modifications as necessary and as well as according to the requirement of the client. All these steps
must also should be included with all the experiences and requirements gathered from the time we
spent for the development of the system.
Project Report
27
4. Conclusion
The project we developed is The Management System for the Gayana hotel tangalle. The System
gives solutions for most of the problems that we have identified in the Hotel currently. All most all
the tasks were handled manually by the management and the employees work at the Hotel. The
System that we are going to introduce will address those problems accordingly
The ability to search about specific information or detail before and after doing a hotel reservation
or to hotels room in easy way with customizing guest detail and checking the validity of details are
some purpose to build system which makes requirements possible with easy and fast way. Hotel
Management system is built to find suitable solution for reservation and customization of rooms,
guests, payments, administration and services. This system deals with the database as an end back
which is based on SQL server and its interface based on visual studio c#. The interface aims to
make reservation and using other tools easy to every one without needing to learn how to use.
The System that is going to be handed over to the client will address most of the
problems in the Hotel currently. The tasks that now are carried out manually will be able to do with
the system in more easy way. The data that are now kept in large physical files will be stored in the
centralized database of the system. That will reduce the damages that can be happened to the data
unexpectedly. The calculations that are done manually will able to be done through the system to get
more accurate results. Presently the information regarding the employees are handled manually. The
system that is introducing give the ability to handle them through the system in a more convenient
and accurately. The details of the daily income, sales and purchasing goods can be inserted to the
system easily and retrieve them whenever the user requires. Records and details of the inventory are
also handled through the proposed system with giving the solutions for the problems that arise with
the current manual procedure of the Hotel.
Those features of the introducing system will call upon the problems that we have encountered from
the current system that is prevailing in the Hotel now to make the tasks done at the Hotel
comfortably and much more efficiently
Project Report
28
References
Books:
[1] IanSommerville,Software Engineering 8th edition.Pearson education,2008.
[2] ElmasriNavathe,Fundamentals of Database System 3rd edition.Pearson education,2000.
[3] RaguRamakrishnan/JohnesGehrke,Database Management Systems 3rdedition.McGrowHILL,2003.
[4] Gerald W. Latin, Modern hotel management, W.H.Freeman, 2011.
[5] Michael J. O'Fallon, Denney G. Rutherford, Hotel Management and Operations illustrated
edition, John Wiley & Sons, 2001
World Wide Web:
[5]Hotel Management Case Study, March.6, 2010. [Online].Available:

http://www.scribd.com/doc/27927992/Hotel-Management-Case-Study, [Accessed: June.28,
2014]
[6]High-Level-Software Features, [Online].Available:
http://www.high-level-software.com/features/, [Accessed: June.25, 2014]
[7]Fernandez & Yuan, X,(1999). An analysis Pattern for Reservation and Use of Reusable Entities.
PloP 1999 conference, Retrieved from
http://hillside.net/plop/plop99/proceedings/Fernandez2/reservanalysisPattern3.PDf
[8]Lauesen, S, (2003), Task Descriptions as Functional Requirements, IEEE Computer Society,
Retrieved from http://www.itu.dk/~slauesen/Papers/IEEEtasks.pdf
[9]Louw,D,(2006, may 10).Description with UML for a Hotel Reservation System. Retrieved from
http://www.liacs.nl/assets/Bachelorscripties/2006-08JanneLouw.pdf
[10] Hotel Receptionist Resume Sample [Online].Available:
http://coverlettersandresume.com/receptionist/resume-sample-of-hotel-receptionist/,
[Accessed: July.23.2014]
[11] Hotel Receptionist Duties[Online].Available:
http://www.buzzle.com/articles/hotel-receptionist-duties.html, [Accessed: July.23.2014]
Project Report
29
Appendix A: Design Diagrams

Activity Diagrams
Activity Diagram for set room rates
Project Report
30
Add new Hotel Room
Project Report
31
Edit Hotel Room
Project Report
32
Make Reservation
Project Report
33
Take Backup
Project Report
34
Search
Project Report
35
Delete a user
Project Report
36
Add Payment
Project Report
37
Add Guest
Project Report
38
Add Staff
Project Report
39
Add property
Project Report
40
Delete user
Project Report
41
Create system restore point
Project Report
42
Deployment diagram
Project Report
43
Component diagram
Project Report
44
Class Diagram for Hotel Management System
Project Report
45
Sequence Diagram for Hotel Management System
Project Report
46
Appendix B: Test Results

Test results of several user inputs dealing with the system
1) Test results of entering invalid information to textboxes are shown here. NIC text field must
include 9 digit and v or V letter following the digits, otherwise an error bubble will
display and the error will display as a tool tip text.
2) Phone number text field must include 10 digits otherwise an error will display as below test
result
3) E-mail field must contain @ and . and they must in the order of a regular e-mail address.
Project Report
47
4) The test result we get, when trying to save the data inserted with empty fields.
Project Report
48
5) Modern metro style user interfaces
Project Report
49

Final Report Document

Uploaded by

Document Information

Original Title

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Final Report Document

Uploaded by

Copyright:

Abstract

Hotel Management System

Prasad Lakmal D.H.

Requirements and Analysis ......................................................................................................... 4

Assessment of the Project results .............................................................................................. 26

2.1.1. Use Case Diagram..

List of Acronyms and Abbreviations

H.M.S. Hotel Management System

ITP-14-MTR-03 Hotel Management System

It is much time consuming.

Lots of Manual labor is required for manual record keeping.

Difficulty of searching and retrieving records.

Slow process of reservation.

Retrieval of guest records is extremely difficult.

ITP-14-MTR-03 Hotel Management System

ITP-14-MTR-03 Hotel Management System

1.2 Product Scope

1.3 Project Report Structure

ITP-14-MTR-03 Hotel Management System

ITP-14-MTR-03 Hotel Management System

2.1.1. Use Case Diagram

ITP-14-MTR-03 Hotel Management System

ITP-14-MTR-03 Hotel Management System

ITP-14-MTR-03 Hotel Management System

//Retrieve dataset--------------------------------------------------------------------------------public static DataSet DatasetRetrive(string query)

ITP-14-MTR-03 Hotel Management System

//Get a datareader-------------------------------------------------------------public static SqlDataReader sqlreader(string query)

ITP-14-MTR-03 Hotel Management System

public class Validations

ITP-14-MTR-03 Hotel Management System

ITP-14-MTR-03 Hotel Management System

constraint pkguest primary key(membercode)

constraint pkguestphone primary key(memcode),

ITP-14-MTR-03 Hotel Management System

constraint pkroom primary key(roomno),

ITP-14-MTR-03 Hotel Management System

constraint pkroomtype primary key(name)

constraint pkreserve primary key(membercode,roomno),

ITP-14-MTR-03 Hotel Management System

constraint pkservices primary key(code),

ITP-14-MTR-03 Hotel Management System

constraint pkcategory primary key(catid)

constraint pkbill primary key(billing_no),

ITP-14-MTR-03 Hotel Management System

constraint pkuser primary key(empid),

constraint pkstaff primary key(empid),

ITP-14-MTR-03 Hotel Management System

constraint pkemployee primary key(empid)

constraint pkempphone primary key(empid),

ITP-14-MTR-03 Hotel Management System

constraint fkempphone foreign key(empid) references employee(empid)

constraint pkevent primary key(code),

ITP-14-MTR-03 Hotel Management System

constraint pkproperty primary key(itemcode),

constraint pkreproperty primary key(itemcode),

ITP-14-MTR-03 Hotel Management System

constraint pktasks primary key(taskid)

constraint pkstaff_assignto_event primary key(empid,code),

ITP-14-MTR-03 Hotel Management System

ITP-14-MTR-03 Hotel Management System

ITP-14-MTR-03 Hotel Management System

ITP-14-MTR-03 Hotel Management System

ITP-14-MTR-03 Hotel Management System

H.M.S. is user-friendly and easy to use.

Database backup and security.

Requirement of a web application