You are on page 1of 17

Hotel Management System

ABSTRACT
This is software which is mainly made for management of a Hotel. The software has been designed with JAVA as frontend and Microsoft Access as back-end. The project Hotel Management manages and maintains the records of customers and rooms in the hotel. The rooms have different categories such as standard, deluxe, VIP etc. Also some rooms have Ac, TV, Refrigerator and many other facilities. Hotel also has other facilities like restaurant, swimming pool etc. So these charges and records will be maintained accordingly. This software has been made in a user friendly interface, so that normal person can add, delete and modify the entries of customer and handle the transactions of customers easily.

Table of Contents
1.0 Introduction 1.1 Project Summary 1.2 Purpose 1.3 Scope 1.4 Objective 2.0 Project Management 2.1 Project Planning 2.1.1 Project Development Approach and Justification 2.1.2 Project Plan 2.1.3 Milestones and Deliverables 2.1.4 Roles and Responsibilities 2.1.5 Group Dependencies 2.2 Project Scheduling 2.3 Risk Management 2.3.1 Risk Identification (it is concerned with discovering possible risk to the project) 2.3.2 Risk Analysis(each identified risk is considered in turn and a judgment made about the probability and the seriousness of the risk) 2.3.3 Risk Planning (Identify strategies to manage the risk) 2.4 Estimation 2.4.1 Effort Estimation 2.4.2 Cost Analysis (Total cost of the project including parts and labors. Labor cost should be broken down into the areas of design, analysis, prototype construction, software development and programming, hardware-software integration, testing, design modifications and documentation. A cost analysis is NOT a tabulation of your expenditure) 3.0 System Requirements Study 3.1 User Characteristics (Type of users who is dealing with the system) 3.2 Hardware and Software Requirements (minimum requirements to run your system) 3.3 Constraints 3.3.1 Regulatory Policies 3.3.2 Hardware Limitations 3.3.3 Interfaces to Other Applications 3.3.4 Parallel Operations 3.3.5 Higher Order Language Requirements 3.3.6 Reliability Requirements 3.3.7 Criticality of the Application 3.3.8 Safety and Security Consideration 3.4 Assumptions and Dependencies 4.0 System Analysis

Study of Current System Problem and Weaknesses of Current System Requirements of New System 4.3.1 User Requirements 4.3.2 System Requirements 4.4 Feasibility Study 4.4.1 Does the system contribute to the overall objectives of the organization? 4.4.2 Can the system be implemented using the current technology and within the given cost and schedule constraints? 4.4.3 Can the system be integrated with other system which is already in place? 4.5 Requirements Validation 4.6 Activity/Process In New System(Use event table) 4.7 Features Of New System 4.8 Class Diagram 4.9 System Activity(Use case and/or scenario diagram) 4.10 Object Interaction 4.11 Sequence and Collaboration Diagram

4.1 4.2 4.3

5.0

System Design

5.1 System Application Design 5.1.1 Method Pseudo code 5.2 Database Design/Data Structure Design 5.2.1 Table and Relationship 5.2.2 Logical Description Of Data 5.3 Input/Output and Interface Design 5.3.1 State Transition/UML Diagram 5.3.2 Samples Of Forms, Reports and Interface 5.4 Database Design 5.4.1 Mapping Of ER Diagrams into Tables 5.4.2 Normalization 5.4.3 Table Relationship Diagram With Indication of all Keys 5.5 Input/output Design 5.6 Interface Design 5.6.1 Access Control and Security 5.6.2 State-Transition Diagram 5.7 System Structural Design 5.8 Matrices Preparation 6.0 Implementation Planning 6.1 Implementation Environment 6.2 Program/Modules Specification 6.3 Security Features 6.4 Coding Standards

7.0 Testing 7.1 Testing Plan 7.2 Testing Strategy 7.3 Testing Methods 7.4 Test Cases 7.4.1 Purpose 7.4.2 Required Input 7.4.3 Expected Result 8.0 Limitation and Future Enhancement 9.0 Conclusion and Discussion 9.1 Self Analysis of Project Viabilities 9.2 Problem Encountered and Possible Solutions 9.3 Summary of Project work

1. Introduction
1.1 Project Summary
This is software for managing the general activities of a hotel like booking of rooms, billing etc. The purpose of this document is to collect, analyze and define high-level needs and features of the Hotel Management System. It focuses on the capabilities needed by the stakeholders, and the target users, and why these needs exist. The details of how the Hotel Management System fulfills these needs are detailed in the use-case and supplementary specifications.

1.2 Purpose
This software is aimed at facilitating the prompt, accurate and easy management of a hotel. It will be very helpful to the manager on the one hand and to the customers as they would be able to get good and fast service.

1.3 Scope
In this software, the hotel manager can add new customers and manage that customer information. Restaurant manager can add restaurant bill in that customer bill. This software works at all hotels that cater to a large number of customers and want to computerize the complete management process.

1.4 Objective
The objective of Hotel Management system is to develop a project which maintains booking of rooms and handles accounts of a hotel. It is a window based application to be implemented in java.

2. Project management
2.1 Project Planning
The plan consists of collecting requirements, creating gantt chart, data flow diagram, use-case diagram, class diagram, semantic model diagram, sequence diagram, collaboration diagram, activity diagram, and implementation.

2.1.1 Project Development Approach and Justification The approach is in four steps: Design, Implement, Test, and Review.

2.1.2 Project Plan

2.1.3 Milestones and Deliverables When one task is performed and completed, its said to have covered a milestone. The working model of the software is called deliverables. 2.1.4 Roles and Responsibilities The programmer has to implement the software logic for two roles of a person: Administrator and User 2.1.5 Group Dependencies This part has to deal with inter dependency of the software logic i.e. in terms of classes, files, functions, etc

2.2 Project Scheduling


If various projects are going on than some specific amount of time is dedicated to both of the projects making efficient project scheduling.

2.3 Risk Management


2.3.1 Risk Identification Since such working models are already available online for free, the use of this software after paying some money will not be easy for faculties and students.

2.3.2 Risk Analysis The risk is analysed as the above and the solution is as following point.

2.3.3 Risk Planning Providing a high reliability and privilege given to faculties to create new software with more security features will compensate for the money.

2.4 Estimation
2.4.1 Effort Estimation This part includes the work hours of employees for the project.

2.4.2 Cost Analysis Total cost of the project including parts and labors. Labor cost should be broken down into the areas of design, analysis, prototype construction, software development and programming, hardware-software integration, testing, design modifications and documentation. A cost analysis is NOT a tabulation of your expenditure.

3. System Requirements Study


3.1Hardware and Software Requirements
Operating System: Vista, XP, Windows 7 RAM: 512MB or more

3.2 Constraints
3.2.1 Regulatory Policies All policies relevant to Regulation and this software need to mentioned here.

3.2.2 Hardware Limitations When server cannot cater to more number of users, it takes time to process.

3.2.3 Interfaces to Other Applications There is no interface with other application. 3.2.4 Parallel Operations Parallel operation for hotel management is to create user and allocating room. 3.2.5 Higher Order Language Requirements As the program is written in JAVA, server must be available to process the script of JAVA.

3.2.6 Reliability Requirements The software is of no use if it doesnt provide reliability.

3.2.7 Criticality of the Application Attention must be paid to the critics i.e. how to remove the problem and how to add a new feature. 3.2.8 Safety and Security Consideration The software should not cause spread of a virus.

3.4 Assumptions and Dependencies


Assumptions made: 1. The software should work on different operating systems. 2. There should be database backups.

4. System Analysis
4.1 Study of Current System
Current system for hotel management is fully based on paper work. Hotel Management has to manage all records of customers and rooms in papers.

4.2 Problem and Weaknesses of Current System


Paperwork is tedious job. There is delay and the problem of human error in allotting rooms and providing services.

4.3 Requirements of New System


4.3.1 User Requirements There should be software which allocate rooms automatically and maintain records of customers and generate bill automatically for customers. 4.3.2 System Requirements

There should be database backup of hotel management system. There should be Java supported framework for the system. Operating system should be Windows XP or higher version of Windows.

4.4 Feasibility Study


4.4.1 Does the system contribute to the overall objectives of the organization?

4.4.4 Can the system be implemented using the current technology and within the given cost and schedule constraints?

4.4.5 Can the system be integrated with other system which is already in place?

4.5 Requirements Validation


It is concerned with showing that the requirements actually define the system which the customer wants.

4.6 Activity/Process In New System


As defined in 4.3

4.7 Features Of New System


-Easy management of checking in and other processes. -Saves time -Can give accurate information about hotel when required -Billing becomes easy -Customer information -Reduces paper work

4.8 Class Diagram

4.9 System Activity

4.10 Object Interaction


This deals with how two or more objects exchange data along with them.

4.11 Sequence and collaboration diagram

5. System Design
5.1 System Application Design
From first form of login for administrator to corresponding other forms. 5.1.1 Method Pseudo code Algorithm or flow-chart is generated according to the data and the task to be performed.

5.2 Database Design


Relational Database is maintained as we know the data required is the same for all.

5.2.1 Table and Relationship There are 3 tables maintained in MS Access: 1. Room: Maintains list of all rooms of the hotel 2. Customer: Information about customer 3. Admin: Administrator login

5.3 Input/output and Interface Design


Input/output always differs because of different customers but Interface is same for all.

5.3.1 Samples of Forms, Reports and Interface Login Form:

Main Window:

Check In and Check out Form:

Guest Information window:

Room Information Window:

5.4 Interface Design


5.4.1 Access Control and Security The security and access control is provided by a login form that checks the user id and password of the user.

6. Implementation Planning
6.1 Implementation Environment
Implementations environment is in Java and software is made in Netbeans IDE. NetBeans provides a user friendly environment for project development. .

6.2 Program/Modules Specification


The Hotel Management software is aimed towards the hotels that want to computerize their management system. It is user-friendly and easy to learn.  Functions: -Login for authorized users -Entry of customer details -Allot room to customers based on current status as shown by software. -Manage the billing including usage of other services of the hotel -Track of all customers as their details are stored.

6.3 Security Features

-There is one module for administrator login. First of all administrator has to login to software with his/her user-id and password.

6.4 Coding Standards


The system is developed in Java which is an Object-Oriented language. Proper validation has been done for various inputs and outputs of the system. Care has been taken about proper indentation of the code.

7. Testing
7.1 Testing Plan
First inspection is performed followed by white box testing which is applied by the programmer.

7.2 Testing Strategy


If it is white box testing then all statements are checked whether they are logically correct.

7.3 Testing Methods


Two methods are used: Boundary value checking, Equivalence class partitioning

7.4 Test Cases


Test Case 1: Testing login module Expected response: Error message should be displayed if entered USERID and/or password is not found in database of administrator. System response: Error: No match for USERID and/or password. Test Case 2: Testing Check in module CHECK IN Expected Response: Error message should be displayed if room is not available for requested period. System Response: The following errors were found: Room is not available for requested period.

7.4.1 Purpose Checking whether the performance is up to the mark is very important.

7.4.2 Required Input

First condition to check is to provide valid input which should give valid output.

7.4.3 Expected Result Through expected results only we can check whether the output is correct.

8. Limitation and Future Enhancement


Limitation: The limitation of our present software is that this is desktop based software and we cannot reserve rooms in advance for customer.Thisproject cant be used for hotel having different branches. Future Enhancement: We are going to make online web based application for this system so customer can automatically find rooms and reserve their rooms in advance.

9. Conclusion and Discussion


9.1 Self Analysis of Project Viabilities Review the software often, to check how its working.

9.2 Problem Encountered and Possible Solutions


If any problem occurs, then solve it.

9.3 Summary of Project work


Planning and design of code is very important while building large software.