hotel management

Table of Contents

1. Acknowledgment…………………………………………….2

2. Certificate…………………………………………………….4

3. Software Requirement Specification3.1. Introduction………………………………….63.2. Overview…………………………………….8

4. Design4.1. E-R Diagram……………………………….144.2. Decision Tree………………………………154.3. UML Diagram……………………………...16

5. Screenshots…………………………………………………….20

6. Testing and future scope………………………………………27

7. Bibliography…………………………………………………...29

8. References……………………………………………………...30

Certificate

Geetanjali Institute Of Technical Studies

List of figures

1. Server Client Architecture - 9

2. 0-Level Data flow diagram - 12

2

Online Hotel Reservation System



5. E-R Diagram - 14

6. Decision Tree - 15

7. Activity Diagram - 16

8. Class Diagram - 17

9. Sequence Diagram - 18

10. Use Case Diagram - 19

11. Home Page - 20

12. Reservation page - 20

13. Cancellation page - 20

14. Customer info page - 21

15. Customer detail page - 21

16. Confirm reservation page - 22

17. Login page - 22

18. Emp_Home page - 23

19. Suites page - 23

20. Relaxwellness page - 24

21. Meeting page - 24

22. About us page - 25

List of Tables

1. Hardware interface - 9

Software Requirement Specification

Introduction

This project is an ASP.NET based application that can be accessed throughout the hotel area. This is an integrated application that contains both user component and managerial component.

3


Hotel needs to maintain the record of guests and reserve rooms beforehand. Customers should be able to know the availability of the rooms on a particular date. They should be able to reserve the available rooms according to their need in advance. To make their stay comfortable, they are provided with food and other services. The record of the food taken by each customer and the services availed by the customer should be kept. These records help in generating bill.

Purpose:-The main objective of the entire activity is to automate the process of day to day activities of the hotel such as:

Room activities, Admission of a New Customer, Assign a room according to customer’s demand, Checkout of a computer and releasing the room Finally compute the bill etc. Packages available. Advance online bookings. Online Cancellation. List of Regular customers. Email facility. Feedbacks

Scope:- A person should be able to see the home page of the hotel to see all necessary facts about it. See the status of the suites so that he can choose the desired category. Search for a particular suite or table to ensure that it’s reserved or not and notify if any

cancellations are made afterwards. Place requests for reserving suites or tables with the desired category. See if the room the person has requested is available or not and if not then when can it be

available afterwards or notify if any cancellation has been made on that particular room later on if any.

Cancel the reservation made earlier for a particular suite or a restaurant table. Reserve a particular suite or table as per the category choice given in the list. As soon as a reservation is made for a suite or table, an e-mail should be sent to the

concerned person.

Assumptions/Risk assessment:-

Assumptions support the base of the solution. Assumptions include:- Hotel houses a limited number of suites in particular category for the sake of many

borrowers. Hotel does not entertain any unauthorized person to enter the administrator or employees’

site from any computer. Client systems supports .NET framework. Hotel server runs a version of Windows operating system.

4


User should have basic knowledge and knows how to search of find information on the internet.

User has a decent internet speed to run the online solution.

Benefits:- System Connectivity No data duplication No Paper Work Required Time Efficient Cost Efficient Automatic data validation User friendly environment Data security and reliability Fast data insertion & retrieval

Abbreviations:- ASP – Active Server Pages SQL – Structured Query Language HTTP/HTTPS - Hypertext Transfer Protocol is a transaction oriented client/server protocol

between web browser & a Web Server. TCP/IP - Transmission Control Protocol/Internet Protocol, the suite of communication

protocols used to connect hosts on the Internet. HTML - Hypertext Markup Language is a markup language used to design static web pages.

Technologies:- Asp.net 2.0. Microsoft SQL Server Management Studio Express Microsoft Visual Studio 2005 Album Flash Creator

Overview

Overall Description will describe major components of the system interconnection and

external interfaces.

Specific Requirements will describe the function of actors, their role in the system and

constraints.

5


Overall Description

Project Perspective:-

The web pages are present to provide the User Interface on customer client basis.

Communication between Client and Server is provided through HTTP/HTTPS

Protocols.

The client software is to provide the User Interface on system, user client side and for

this TCP/IP Protocol is used.

On the server side, the web server is for .Net Framework and database server for storing

information.

Fig. 1 Server-Client Architecture

Software Interface:-

Client on internet: Web browser, Operating System (any).

Client on intranet: Client Software, Web browser, Operating System (any).

Web Server: ASP.NET, Operating System (any).

Database Server: MS SQL server studio express, Operating System (any).

Development End: Visual Studio

Hardware Interface:-

6

Client

(Customer)HTTP/HTTPS

ASP.NET SQL

Application Server Database Server


Client Side

Processor RAM Disk Space

Internet Explorer 8.0

Pentium II at 500 MHz

64MB 1GB

Mozilla Firefox

Pentium III at 500 MHz

128MB 2GB

Table.1 Hardware Interface

Communication Interface: Client on Internet will be using HTTP/HTTPS protocol. Client on Intranet will be using TCP/IP protocol.

User Characteristics: Every user should be comfortable of working with computer and net browsing. He must have some sort of basic knowledge of English too.

Constraints: GUI is only in English. Login and password is used for identification of employees. This system is working for single server. There is no maintainability of back up so availability will get affected. Limited to HTTP/HTTPS.

Roles

Administrator - Administrator is a person who manages and supervises the functioning of the hotel. Administrator creates his/her account during the initial setup of the solution. Administrator has to sign in like the user to access the hotel. Administrator can search for employees & guests. He/she can view the employee & guest details. He/she can view the profile and make changes to it if necessary. He/she can change the password by entering the answer for the security question. Administrator can add/delete employee or guest. Administrator can mail reminders to employees.

7


Administrator can view transaction details of guests or employees separately.

Employees Employee has to sign up for his personal account profile. Employee can view his/her profile details & change password if necessary.. Employee can only view the guest’s list. Employee can view the comments posted by user. Employee can view the reminders sent by the administrator

Guests

Guests can post feedbacks on the website. Guests can view the facilities or schemes offered by the hotel. Guests can make reservation/cancellation request online. Guests can get request confirmation/denial by mail. Guests can make special service requests for their arrival. Guests can book meeting hall or restaurant table in advance. Guests can choose mode of bill payment as available.

Features and Services

Features Performance: During past several decades, the records are supposed to be manually

handled for all activities. The manual handling of the record is time consuming and highly prone to error. To improve the performance of the Hotel Management System, the computerized system is to be undertaken. This project is fully computerized and user friendly even that any of the members can see the report and status of the company.

Efficiency: The basic need of this website is efficiency. The website should be efficient so that whenever a new user submits his/her details the website is updated automatically. This record will be useful for other users instantly.

Control: The complete control of the project is under the hands of authorized person who has the password to access this project and illegal access is not supposed to deal with. All the control is under the administrator and the other members have the rights to just see the records not to change any transaction or entry.

Security: Security is the main criteria for the proposed system. Since illegal access may corrupt the database. So security has to be given in this project.

8


Services Reservation/Cancellation – Allows user to make reservation or cancellation in hotel. Search facility – Can search if the suites are available or not. Request for specific suite type – Can request for a specific type of suite. Transactions – Can make bill transactions through available payment mode. Notifications – Can receive notifications about the request made to the hotel admin.

Functional Requirements Room Detail Functions

Opening a New Room Modification to room assigned

Check-in and check-out Detail Functions Admission of New customer Check-out of customer Room assigning related to customer’s need

Statement of Customer Details Check-in customer Check-out customer Room Details Mode of bill payment Room services made to the guest & record it Customer Records

Data flow diagram

Reservation room

Hotel DB

Update room DB

9

Hotel Reservation

System

Customer

Admin


Fig.2 Level-0 DFD

Database

Fig.3 Level-1 DFD

Database

10

Customer

Special offers

Check room detail

Check availability0.2 Update database

0.3

Admin

Customer Confirm room booking

Book services0.2.1

Billing0.2.2

Cancel bookings0.3.1

Updates in room price & services

0.3.2


Fig.4 Level-2 DFD

Design

1. Entity-relationship diagram

11

Admin Username

Password

Roll_id

Customer

Cust-id Title

Fname

Postal_id

Address

Lname

Makes

Booking_details Total_pay Dep_date Book_date Room_no Cust_id Booking-id

Availability

Room_detail Room_price Status

Admin

Accesses


Fig.5 E-R Diagram

2. Decision tree

12

Email_id

Arr_date

Room_type Room_no

Visit

Make reservation Cancellation/Modification

Select check-in and check-out date Enter Cust_id

Check Availability Confirm your cancellation/modification Yes

No

Creditcard

Number

Type


Fig.6 Decision tree

3. UML Diagram

3.1. Activity diagram

13

Reservation enquiry Check availability

Cancel Update

Fill the form

Confirm reservation

Get Cust_id


No

Yes

~

Fig.7 Activity Diagram

3.2. Class diagram

14

Make reservation

Give credit card no.

Confirm reservation Billing

Check In Check out

Customer Cust_idFirst_nameLast_nameContact_noAddressEmail-idCreditcard_no

Add customerRetrieve information

Booking detail

Arrival_dateDeparture_dateBookin_idBooking_dateRoom_noCustomer_id

Check availabilityUpdate informationDelete information

Total paymentRetrieve record

Asks for

Room detail

Room_idRoom_typeRoom_priceStatus

AvailabilityRoom priceUpdate room priceImply available discount scheme

Admin

User_namePassword Roll_id

Add informationUpdate informationRetrieve informationDelete information


Fig.8 Class Diagram

3.3. Sequence Diagram

Check availability

15

Availability

WindowUser Interface

Hotel

Reservation


Condition

Message Room available

Make reservations

Note

Fig.9 Sequence Diagram

3.4. Use-case diagram

16

Notice Confirmation

If room available for each day of stay, make reservations & send confirmation message to the concerned.

Customer info

Book room

Services available

Room info

Room available

Services requiredPaymentCancelUpdateConfirmation message/e-mail


(Customer) (Admin)

Fig.10 Use-Case diagram

Screenshot

17


Testing and Future scope

Testing:-Software design is a critical element of software quality assurance and represents the ultimate review of specification, design and code generation. Once the source code has been generated, the software must be tested to uncover as many errors as possible before delivery to the customer. Our goal is to design a series of test cases that have a high likelihood of finding errors. .If testing is conducted successfully, it will uncover errors in the software. As the secondary benefits, testing demonstrates that software functions appear to be working according to specification, that behavioral and performance requirements appear to have been met. The software can be tested by one of the two ways:

Knowing the specified function that a product has been designed to perform, tests can be conducted that demonstrate each function is fully operational while at the same time searching for errors in each function.

Knowing the internal working of the product, tests can be conducted to ensure that internal operations are performed according to specifications and all internal components have been adequately exercised. The first approach is called black – box testing and the second, white – box testing.

White Box Testing:-White box testing is a test case design method that uses the control structural of the procedural design to derive test cases. It is also called glass box testing. Using this method we can derive test cases that-

Guarantee that all independent paths within a module have been exercised at least once. Exercise all logical decisions on their true and false sides Executes all loops at their boundaries and within their operational bounds. Exercise internal data structures to ensure their validity.

Black Box Testing:-Black – box testing focuses on the functional requirements of the software i.e. it enables the software engineer to derive sets of input conditions that will fully exercise all functional requirements for a program. It is also called behavioral testing. Black–box testing attempts to find errors in the following categories:-

Incorrect or missing functions Interface errors Initialization and termination errors

18


Testing Strategy:-Designing effective test cases is important but so is the strategy we use to execute them. There are a number of testing strategies, which have the following generic characteristics: -Testing begins at the component level and works “outward” toward the integration of the entire computer–based system.Different testing techniques are approximate at different points in time.

Testing is conducted by the developer of the software and (for large projects) an independent test group.

Testing and debugging are different activities, but debugging must be accommodated in any testing strategy.

The software engineering process may be viewed as a spiral. Initially, system engineering defines the role of software and leads to software requirement analysis where the information domain, function, behavior, performance, constraints and validation criteria for software are established. Moving inward along the spiral, we come to the design and finally to coding. There are a number of testing strategies, which are given below: -

Unit Testing:-In the unit testing interfaces, local data structures, boundary conditions, independent paths, error handling paths are tested. Test cases should be design to uncover errors due to erroneous computations, incorrect comparisons, or improper control flow. For this purpose basis path and loop testing is done. After source level code has been developed, reviewed and verified for correspondence to component level design, unit test case design begins. In unit test application ‘drivers’ are developed which are programs, accept test case data, passes such data to the component to be tested and prints relevant results. ‘Stubs’ are also developed which serve to replace modules that are subordinate the component to be tested.

Integration testing: -Integration testing is systematic technique for constructing the program structure while at the same time conducting the tests to uncover errors associated with interfacing. The objective is to take unit tested components and build a program structure that has been dictated by design. There are two types of integration – Bottom up integration and Top down integration. Regression and smoke testing are done in integration testing strategy.

Validation testing: -Next step is the validation testing where requirements established as part of software requirements analysis are validated against the software that has been constructed. At the culmination of integration testing, software is completely assembled as a package, interfacing errors has been uncovered and corrected, and a final series of software tests i.e. validation testing begins.

Future Scope:-The fact that the present investigation is mainly aimed to work for a hotel system to perform various service activities similar to organization for which the system is proposed.

19


BIBLIOGRAPHY

1. Using Asp.net 2.0

2. www.google.com

20

http://www.google.com/


REFERENCES

1. www.wikipedia.org/asp.net

2. www.oberoihotels.com

3. www.travelindia.com

4. www.wikipedia.org/traveldestinations

21

http://www.wikipedia.org/traveldestinations

http://www.travelindia.com/

http://www.oberoihotels.com/

http://www.wikipedia.org/asp.net

Documents

hotel management