A

PROJECT REPORT

ON

HOTEL MANAGEMENT SYSTEM

Submitted By

Mr. Ganesh G. Gotpagar Mr. Sagar B. Gharge

Under The Guidance

Mr. H. P. Khandagale

Submitted To

(COMPUTER SCIENCE AND TECHNOLOGY)

DEPARTMENT OF TECHNOLOGY

SHIVAJI UNIVERSITY, KOLHAPUR

2013-2014

DEPARTMENT OF TECHNOLOGY

CERTIFICATE

This certifies that Ganesh Gotpagar, Sagar Gharge has successfully

completed a project on Hotel Management System to our requisite

satisfaction during the academic year 2013-2014.

This project is completed under the guidance of Mr. H. P. Khandagale as

Per rules of Shivaji University.

Project Guide Head Of Dept.

(Prof. H. P. Khandagale) (Prof. R. J. Deshmukh)

We are thankful to our H.O.D Prof. Deshmukh R. J. for all their

support & inspiration and we hope the same to continue in future.

Great regards to Mr. Khandagale H. P. for being our project guide

and other members of Computer department for giving us valuable guidance that

helped us to complete our project on schedule. We are also thankful to staff

members of our college for their co-operation.

Date:

Place: KOLHAPUR

Student Name Roll no.

Sagar B. Gharge 21

Ganesh G. Gotpagar 22

Tables of Content

1. Abstract

2. Project Objectives

3. Requirements

3.1 Design Constraints and Dependencies

3.2 Product Functions

3.3 Hardware and Software Requirements

3.4 Performance Requirements

3.5 Quality Requirements

4. Project Design

4.1 Feasibility

4.2 Data Flow diagrams

4.3 UML Documentations

5. System Implementation

5.1 Important Functions

5.2 Important Algorithms

5.3 Screen Shots of GUI

6. System Testing

6.1 Test Cases

6.2 Test Procedures

7. Future Scope

8. Conclusion

9. References

9.1 Bibliography

9.2 Web References

Chapter 1

ABSTRACT

This Program is for those Hotel Manager who want automate all the work

in hotels at present. It is very easy to use because it is totally GUI (Graphical User

Interface) based application.

Relevance of Project:-

This project HOTEL MANAGEMENT SYSTEM aims at automating all the

work being done manually in hotels at present. Management system is to generalize

an simplify the monthly or day to day activities of Hotel like Room activities, Check

in of New Customer, Check out of customer, Assigning a room according to

customer requirement, and finally compute the bill etc. which has to be performed

on regular basis. To provide efficient, fast, reliable and user-friendly system is the

basic motto behind this exercise.

Project Idea:

Hotel Management System Program is very useful not only as being a

programmer yourself but also it can use for Hotel purpose. You can add new

customer, checkout of customer, search particular customer information, view

option is also available to view all room booking customer &checkout customer.

The project HOTEL MANAGEMENT SYSTEM gives us the complete

information about the present work in hotel. We can enter the particular record of

the customer and retrieve all the information of the particular customer. We can

also check how many room are available in hotel & provide a room according to

customer requirement.

The coding of this project is done by using the language JAVA

PROGRAMMING. Because it is easy to implement and user friendly. This

language is simple because everything is done with the help of mouse click event

and keyboard click.

Chapter 2

PROJECT OBJECTIVES

2.1 Function Details:-

2.1.1 Creating new Entity (Hotel, Room & Customers etc.)

This is used to add a new employee detail delete entity details and view the

details. In that screen, the automatic item is created. In this work function, whenever

a new entity is required to be added the corresponding forms are opened and the

database is manipulated to check whether the data is already existing or not. If it

already exists, then it prompts that Entry already existing and if not than the data

is entered with the various validation checks.

2.2 Function New Room()

This is the function used to open a new room for a customer so that he/she can

assign a separate room. In that screen, the automatic room number is created. After

opening a new room for the customer, finally a room is assigned to a customer and

the room records are appended in the data file.

2.3 Function Checkin Customer()

This function is used to admit a customer in our Hotel after entering his all

personal details like Name, Address, Purpose, Sex and then he/she is assigned a

room from New Room() function.

2.4 Function Checkout Customer()

This function is used to checkout the customer details from database. When

the user inputs his room number, the same room number will be checked in the

database, if the room number is matched in the database, then the customer will be

check-out from the database and transferred the record of the checkout to another

table of database so that the Hotel Management has the record customers who have

check-out to fulfill his legal liabilities.

2.5 Function Generate Bill()

When any customer check-out, his/her bill is generated automatically by

Calculated check-out date minus check-in date and getting multiplied it by daily

room charge plus other charges and the bill has to be saved in the table in the

database.

2.6 Function Display Record ()

This function is used to display all the transaction including the customer

name, address, room number in the screen. This is a global report to display all the

transaction records in the screen.

Chapter 3

REQUIREMENTS

The requirements of software system describe hardware & software, data

requirement and that it will be easy to understand overall requirement of software to

be built.

3.1 Design Constraints and Dependencies

The design constraint refers to some limitations on the conditions under which

software is developed or on the requirements of the software.

1. The software can run only on Windows 7 and XP.

2. Design of project should be easy to modify.

3.2 Product Functions

3.1 Login validation: - Login validated by system.

3.2 Protection: - To get access only to the authorized members.

3.3 Hardware and Software Requirements

3.3.1 Minimum Hardware Requirements:

Processor: Intel Pentium II

Memory: 32 MB

Hard disk: 1064 MB

Printer: Laser Printer

Monitor: VGA Color Monitor

3.3.2 Minimum Software Requirements:

Operating System: Windows XP

Application Software: Microsoft Access 2007

3.4 Performance Requirements

While there is much discussion of performance measurement and its benefits

and is advantages, the work relating to performance indicators themselves has often

been presented in the form of manuals or handbooks which aim either to help

the hotel manager develop a set of indicators suitable for his or her hotel .

Hotel manager with a predefined set of indicators which the manual asserts to

be tested and useful.

Six reasons for measuring performance which, given the ever-increasing

pressure on manager world-wide to justify resources, are becoming more relevant

for all hotel.

The political imperative

Accountability to the parent institution

Accountability to customers

Performance indicators in relation to service level agreements

Performance indicators in relation to quality

Decision support

These reasons are of such clear importance that hotel managers would be to

avoid measuring their hotel services performance.

3.5 Quality Requirements

1. Interface should be user friendly.

2. Application should be tested under Test to pass and Test to fail testing.

3. GUI should be tested under Black box testing.

Chapter 4

PROJECT DESIGN

4.1 Feasibility study:

The project will be carried out during a period of 25 weeks during this

period the following task will be accomplished.

4.1.1 Project Finalization :

In this module we have discovered some project topics & finalize the

project.

4.1.2 Technology Understanding:

In this module we have studied the feasibility of project & study of current

system, its limitations, working of Java & its use.

4.1.3 Documentation Design:

In this module we have prepared the documentation according to software

development lifecycle i.e. synopsis software requirement specification.

4.1.4 Prototype Design:

This stage will involve designing the prototype of the system. The

deliverable of this task is design, probably in paper, which will help in the

implementation phase.

4.1.5 Prototype Coding:

This stage will take the design from the previous stage & implement the

prototype that can be capable of composing and receiving different messages.

4.1.6 Prototype Testing:

This stage will test the functions of the prototype and additional services

as they are integrated in to the system. The deliverable of this stage will be a

document containing any errors found in the implementation of the prototype and/or

the system functions, together with their solution.

4.2 Data Flow Diagram

Data flow diagram is used to only flow of data in system. This Data Flow

Diagrams applied when input data are to be transformed to a series of a

computational or manipulates components into output data. If the data flow

degenerates into a single line of transformers, it is termed batch sequential.

4.3 UML Diagram

4.3.1 Use Case Diagram:-

A use case is a scenario that describes the use of a system by an actor to

accomplish a specific goal. What does this mean? An actor is a user playing a role

with respect to the system. Actors are generally people although other computer

systems may be actors.

4.3.2 Class Diagram

This class diagram of the pattern description Itemizes the classes/objects that

are included in the requirements pattern & describe the responsibilities of each

class/object.

Fig: - Class Diagram

4.3.3 Sequence Diagram

The sequence diagram shows all the sequence of operations that are

performed with respect to time. It shows the various controllers of our portal

& thus their operations performed A sequence diagram is kind of interaction

diagram in UML, that shows how processes operate one with another and in

what order. It is constructing of message sequence chart. As shown below.

Fig: - Sequence Diagram

4.3.4 Activity Diagram:-

The Activity diagrams to negotiation of control when

multiple authorized people attempt to monitor & control a single sensor at the

same time. The construction details indicating how this operation are invoked

& interface details

4.3.5 E-R Diagram

4.4 Different Application

4.4.1 Easy Interface :

It is made of very simple interfaces. Any end user with a minimum

knowledge of operating the Computer can easily familiar with this software

4.4.2 Automates the task

It automates the task, which have to be carried out manually in other

payroll softwares. Such as CheckIn of new customer, Checkout of customer,

Compute the Bill etc.

4.2.3 Security

It is password-protected software. Unauthorized user cannot log on to

this software.

4.2.4 Reliability

It is reliable software. One can rely on the result produced by this

software. We try to remove all the errors from it and make it error free but it

can be error prone.

Chapter 5

SYSTEM IMPLEMENTATION

5.1 Important Functions

5.1.1 GetDate ():-

It returns a current date.

Date d = new Date ();

d.getDate();

5.1.2 Show MessageDialoge ()

To show Message Box on Output Screen use to Following Function

JOptionPane.showMessageDialog((Component)e.getSource(),Message);

5.1.3 Set Font ()

It Returns Font.

To specifies Size, Color to the character use the Set Font () function

Set Font (new Font ("Arial", 1, 15));

5.1.5 Result Set ():-

It is used to retrieve the data from the database into its object. For

selecting the next record we use next () method of ResultSet.

ResultSet r = Statement.executeQuery ();

5.1.5 TabbedPane() :-

A tabbed pane is a component that appears group of folders in a file

cabinet. Each folder has a title.

void addTab(String str, Component comp)

5.2 Important Algorithms

5.2.1 Establish the connection with the database.

It is used to establish the connection between the java applications

And the database.

5.2.2 Steps to establish the connection.

1. Open the control panel.

2. Click on administrative tools.

3. Click on ODBC data source.

4. Click on add button.

5. Give data source name.

6. Select the database name to add into data source name.

7. Load the database driver.

Class.forName (sun.jdbc.odbc.JdbcOdbcDriver);

8. To create the object of connection class.

5.2 Screen Shots of GUI

5.2.1 Login Form

5.2.2 Room Booking Form

5.2.3 Checkout Form

5.2.4 New Room Form

5.2.5 All Available Room

5.2.6 Edit Room Price

5.2.7 Room Booking Form

Chapter 6

SYSTEM TESTING

System testing of software is testing conducted on a complete, integrated

system to evaluate the systems compliance with its specified requirements. System

testing falls within the scope of black box testing and as such, should require no

knowledge of inner design of the code or logic.

6.1 Test Cases

Test cases in software engineering are a set of conditions or variables

under which a tester will determine whether an application or software system is

working correctly or not.

6.1.1 Test cases for Login Form:-

Sr.No. Test case

name

Input Expected

Result

Actual Result

1. Login

Validation

Enter User Name

and password and

click Login.

Homepage

should be

displayed.

Homepage is

displayed.

2. Login

Invalidation

Enter User Name

and password and

click Login.

Message of

invalid

password or

User Name

should be

displayed.

Message of

invalid

password or

User Name is

displayed.

6.1.2. Test case for Functional unit:-

Sr.

No.

Test case name Expected Result Actual Result

1. Checkout To search all the

information of customer

according to room number

To display all the

information of

customer according to

room number

3. Search To search the particular

customer information

To display the

particular customer

information.

4. Database Table

(Room

Booking)

To display the information

of all room booking

customer

To display the

information of all room

booking customer

5. Database Table

(All Available

Room)

To display the information

of all available room in

Hotel

To display the

information of all

available room in Hotel

6. Bill Generation To check generated bill

should be correct

Generated bill should

be correct

6.2 Test Procedure

Testing procedures must encompass all aspects of the software testing

process. Its vitally important that the procedures define the people who will be

involved in the testing process, the skill set of each team member, and their

availability for the duration of the testing cycle.

6.2.1 Black Box Testing.

Black Box testing suggests no knowledge of internal logic or code

structure is required. This testing does not need the internal knowledge of the code

or design. It totally focuses on the testing for requirements and functionality of the

work software application.

6.2.2.1 Login Form.

We enter User name and password and only check the main form

gets displayed or not.

6.2.2 Test To Pass.

It is designing and running, the simplest and straight forward cases to

ensure that software works as expected.

6.2.2.1 Searching.

On the basis of Room number we check whether the expected record is

displayed or not.

6.2.2.2 Bill Generation.

On entering the Room charges per day and extra charges to check whether

the generated bill is correct or not

6.2.3 Test To Fail.

It is designing and running the test cases, with the purpose of

breaking the software.

6.2.3.1 Login Form

To check if the account is displayed when password is incorrect.

6.2.3.2 Room Allocation

To check whether room is available or not.

6.2.4 GUI testing.

GUI software testing is the process of testing a product that uses a graphical

user interface, to ensure it meets its return specifications. This is normally done

through the use of variety of test cases.

Sr.

No.

Test

Condition

Expected Result Actual Result

1. Homepage

screen

The Homepage should be

displayed after Login.

The Homepage is

displayed after Login.

2. Buttons The button should be appear on

Proper place

The button appear on

Proper place

3. Name given

to button

Action should be perform

according to name given to

button

Action perform

according to name

given to button

4. Frame On the screen current frame

should be displayed.

On the screen current

frame is displayed.

Chapter 7

FUTURE SCOPE

This application fits into the current scenario, which is the information

age. Modern hotels, to increase their efficiency can use this application with some

modifications as per their customized needs.

This application can be easily implemented under various situations. We can

add new features as and when we require. Reusability is possible as and when

require in this application. There is flexibility in all the modules.

Due to large amount of data a system required to store a data and respond as

and when required. All the calculations can be done accurately in quick time. Due

to the large number of customer, a system is required to store the updated

information.

Chapter 8

CONCLUSION

This project has been a great experienced to us. This project work really gives

chance to learn something practically. It has helped us to learn and understand the

language Java and Software Testing concepts in more details as well as implements

software concepts in real life to develop software that is compatible with the user

and satisfy the user needs. It helps us very much to build our spirit. We have tried

to make our software user friendly as possible.

The main purpose of our project is to handle each and every task on the

computer and to keep the stored information as secure as possible.

Because of our inexperience we couldnt develop a real world well

working software. Now we have got some experience. Now we have known that to

develop a good software we have to follow almost every rule of the Software

Engineering, otherwise development of successful software is not possible.

Planning is an essential part of software engineering

.

Chapter 9

REFERENCES

9.1 Bibliography

1. Java Complete reference.

2. Java Black Book.

9.2 Web References

1. www.lynda.com

2. www.tutorialpoint.com/java

3. www.netbeans.org

4. www.javabeginner.com

9.3 DEFINITION OF THE PROJECT

P : Planning before doing any type of work.

R : Requirement gathering.

O : Organizing the work.

J : Joint efforts put together in the work.

E : Estimation of the material.

C : Costing of the work.

T : Techniques used in performing the work.