HOTEL RESERVATION SYSTEM

Summer Project Report

Submitted in partial fulfillment of the requirements for the degree of

Bachelor of Technology (B.Tech)

By

Abhinav Vasisht
CSE/07/301
Yatharth Batra
CSE/07/359
July 2010

SHRI BALWANT INSTITUTE OF TECHNOLOGY

Approved by AICTE, Min of HRD, Govt of India & DTE, Govt of
Haryana
Affiliated to MD University, Rohtak

[1]
Meerut Road (Pallri), Near DPS, Sonepat-131001, Haryana

[2]
 CERTIFICATE

This is to certify that the Project titled HOTEL RESERVATION SYSTEM and submitted
by ABHINAV VASISHT having Roll No CSE/07/301 for the partial fulfillment of the
requirements for the degree of Bachelor of Technology/Engineering (B.Tech/ B.E.),
embodies the bonafide work done by him/her under my supervision.

[3]
Acknowledgement

This report gives the details of the project work done at the end of VI
semester during the summer vacation for partial fulfillment of the
requirements for the degree of Bachelor of Technology/Engineering
(B.Tech/ B.E.), under the Supervision of ASHWINI KUMAR.

I am very grateful to my supervisor ASHWINI KUMAR for his/her help

and able guidance for the project. I am very thankful to my Institute,
for providing me resources and facilities to help in the project.

____________________
Signature of the Student

Name: ABHINAV VASISHT

Date: 11/08/2010

[4]
 Table of Contents

Introduction.........................................................................................................................8
1 Feasibility Report..............................................................................................................9
1.1 1.2 Scope.................................................................................................................11
1.2 1.3 System Overview..............................................................................................11
1.3 1.4 Project References.............................................................................................12
1.4 1.5 Acronyms and Abbreviations............................................................................12
1.5 1.6.2 Coordination...................................................................................................12
1.6 2.1.2 Input/ Output..................................................................................................13
1.7 2.1.3 Processing......................................................................................................13
1.8 2.1.4 Security..........................................................................................................14
1.9 2.1.5 System Interaction..........................................................................................14
1.10 2.1.6 Physical Environment..................................................................................14
1.11 2.2 Current Functional Procedures........................................................................14
1.12 2.3 Functional Objectives......................................................................................15
1.13 2.4 Performance Objectives..................................................................................15
1.14 2.5 Assumptions and Constraints..........................................................................16
1.15 2.6 Methodology...................................................................................................16
1.16 2.8 Recommendation.............................................................................................16
2 3.0 PROPOSED SYSTEM.............................................................................................17
2.1 3.1 Description of Proposed System.......................................................................17
2.2 3.2 Improvements....................................................................................................17
2.3 3.3 Time and Resource Costs..................................................................................17
2.4 3.4 Impacts..............................................................................................................17
2.5 3.4.1 Equipment Impacts ........................................................................................18
2.6 3.4.2 Software Impacts............................................................................................18
2.7 3.4.3 Organizational Impacts..................................................................................18
2.8 3.4.4 Operational Impacts.......................................................................................18
2.9 3.4.5 Developmental Impacts..................................................................................19
2.10 3.4.7 Security and Privacy Impacts.......................................................................19

[5]
 2.11 4.0 Alternative System..........................................................................................19
3 Requirement Specification..............................................................................................21
2.12 Document Conventions.........................................................................................21
2.13 Intended Audience and Reading Suggestions.......................................................21
2.14 Project Scope.........................................................................................................21
2.15 References.............................................................................................................21
3 Overall Description.........................................................................................................22
3.1 Product Perspective.................................................................................................22
3.2 Product Features......................................................................................................22
3.3 User Classes and Characteristics.............................................................................22
3.4 Operating Environment...........................................................................................22
3.5 Design and Implementation Constraints.................................................................23
3.6 User Documentation................................................................................................23
3.7 Assumptions and Dependencies..............................................................................23
4 System Features..............................................................................................................23
4.1 Web based application............................................................................................23
4.2 no paper work ........................................................................................................24
4.3 User authentication .................................................................................................24
4.4 Provide security .....................................................................................................24
4.5 Online work ...........................................................................................................24
4.6 fast and easily access .............................................................................................24
5 External Interface Requirements.....................................................................................24
5.1 User Interfaces........................................................................................................24
5.2 Interfaces Hardware................................................................................................27
5.3 Software Interfaces..................................................................................................27
5.4 Communications Interfaces.....................................................................................28
6 Other Nonfunctional Requirements................................................................................29
6.1 Performance Requirements.....................................................................................29
6.2 Safety Requirements...............................................................................................29
6.3 Security Requirements............................................................................................29
6.4 Software Quality Attributes....................................................................................29
7 Other Requirements........................................................................................................30

[6]
4 Design Specification.......................................................................................................31
DATABASE STRUCTURE.............................................................................................39
6 Conclusion.................................................................................................................54
7 Bibliography................................................................................................................55
8 Checklist........................................................................................................................56

[7]
 Introduction

Being social, communicating with others is the most

important part of a human being, but that is not the
case now, because people seem to have no time
today. Considering this thing in mind a system has
been developed, which saves a lot of time dealing
with the transactions in a company’s office, located at
various places. It is quite easy to deal with the
transactions if they are completely computerized, but
if these transactions are done manually many
precautions are to be taken which is an overhead to
the administrative department. This software is made
for the sales and services department of an Hotel
Administration which is responsible for maintaining
the inventory, maintaining the necessary Office
details and also resolving the customer’s
complaints to provide them full satisfaction.

[8]
1 Feasibility Report

PURPOSE
It is required to build a website through which:
• A user, according to its requirements &
budget can search a 3-star or 4-star hotel
from countries like India, United States and
Australia.
• Addition of new hotels is allowed in the
website.

[9]
MAJOR CHALLENGES

• To Increase the number of bookings taken from hotel’s existing website.

– By making the interface more user friendly.

– Hotels from other countries like Australia, United States are also included.

– Seeking Feedback.

• To Increase hitting frequency of website

– By implementing Search Engine Optimization i.e. including user friendly

keywords in pages’ head and pages’ content.

• New website to be re-written with both search engines and customers in mind

– Simple Site Navigation.

– Minimum Number of Steps to Book a hotel.

Hotel Reservation System provides the facility of managing the hotel booking in any
area. It is not a single task but a combination of many activities like:
• Addition of Hotels.

• Maintenance of Hotel customer details.

• Keeping records of Hotel rooms.

• Maintaining the Hotel reservation counter.

All these tasks require a lot of human work and security. Because
some of the information can be quite confidential for company and loss
of that information can cause a lot of loss. This module may be the
very first activity but other modules depend on it for their functionality.
So, such a system is really needed which can ease, simplify and secure
these tasks.

[10]
1.1 1.2 Scope

It provides a single, complete, integrated & authoritative source of information for

HOTEL ADMINISTRATORS, agents & customers associated with the hotels. Each
project must have a scope for future so that the real advantage of developing the project
can be taken. The project HRS has a big scope to do.
• Each company has a system to deal with the Hotel Reservation system. And this
process requires such efficient system which can perform the task frequently with
ease. So HRS can prove very helpful for these type of companies, however, some
modifications may be required before implementing it.
• This project can be implemented as a module in any HRS concerning any
company.
• There is room for future development according to user’s changing requirements
i.e. as and when user requires some modifications in the hotel functionality it can
be done easily. There is also scope for any future enhancements if the
company/user/company wants to do such as increasing the size of hotels,
including more hotels, equipment addition etc.

1.2 1.3 System Overview

SQL SERVER (database application) is used for the communication

between the server and the client through which we can retrieve the
information. The transactions are seen when we send the request to
the server to fetch the record from its database.

• The CRESTECH INFOSYSTEMS is the responsible

organization which trained us throughout the training and
trained us to develop the projects without any assistance.
• The application name is HRS Module which makes use of
ASP.NET with SQL SERVER 2005 (Application
Programming).
• Application category
− Major application: The major security issue
associated with the application is the database
security. As well as there is the password security
provided with the application wherein only the
authenticated user can perform the functions
provided by the server. Also there is validation

[11]
 functionality which enhances the security facility for
our project.

• Operational status
− Project is under development with major
modification going on it as per the accordance of
time.

• System environment or special conditions

Only the authorized user (who has direct access to
database) has the right to login. Unauthorized user or the
customers does not have the appropriate rights to modify
or add details. There is proper validation services
included for the security of the project so that no other
unauthorized person can have access to this facility.

1.3 1.4 Project References

• WWW.VERAHOTEL.COM
• Training and projects (PREVIOUS MODULE)

1.4 1.5 Acronyms and Abbreviations

HRS: Hotel Reservation system

SRS: Software requirement specification
AMC: Annual maintenance contract
FC: Feasibility study

1.5 1.6.2 Coordination

Various organizations that are involved for the project are:-

CRESTECH INFOSYSTEM: -Provided us the guidance for implementation of the

project.

Reservation: - Provided us the platform for the project.

[12]
Under the guidance of CRESTECH trainers we tried to build up the project with
coordination. The project is divided into several modules and each module is worked
upon by each member of the group. The specific schedule was provided by the
CRESTECH team, based on which our project explored.

1.6 2.1.2 Input/ Output

Hotel Reservation system is loaded on a high configured server machine and this
machine has a large storage database for storing or retrieving the information regarding
hotels.
For the database purpose SQL SERVER 2005 is used to make the database server where
we can easily send the request for storing or retrieving the data.
To run this application Visual Studio 2008 is used. Because hotel Reservation system is
developed in the asp.net (server side scripting language) and all the codes executes where
the asp.net server is installed then it send these executed code to web browser.
To run this application efficiently with more user friendly at the client side MOZILA
WEB BROWESER is used.
Any operating system where Mozilla web browser installed.
TCP/IP protocol is used to communicate with the server. Here request send by the client
using TCP/IP, HTTP protocols to the server and server receive the request and send the
response to the client through the TCP/IP, HTTP protocol.
Here a centralized data base is used to store or retrieve the information.

1.7 2.1.3 Processing

System processing includes large system memory to store the database to student
information for the Reservation and maintenance of the hotels of the company. For the
system processing the SQL SERVER is being used as it can make access to the database
with ease to handle the requiring situations.
To run this application we have need different types of hardware device. These are
following as
Processor – 3.0 GHz,
Ram – 1 GB,
HDD – 80 GB,
Switches, Router,
Transmission Media – co-axial cable, optical fiber, Wi-Fi modem etc
Keyboard,
Mouse,
Monitor.

[13]
When user run this application or accesses this application on particular computer which
is connected in the network. It give the domain name of the hotel Reservation system
application in the internet explored window and click on the go button then that request
send by the user computer to sever computer via transmission media (using router or
switches it fetch the path of the server computer and) than server give the response
corresponding to that request in this way all the interfaces interact with the hardware
device and network devices and the sever computer. It uses the http protocol to send and
receive the request on the both side.

1.8 2.1.4 Security

HRS module needs security for the system, so to be able to prevent the unauthorized
access into the system by providing a login option to the authorized persons in this
process and prevent the system for being a complete chaos.
As we had put quite a lot validations in the under process project with authentications
also being there, So the unauthorized access to the system from outsider as well as insider
is not possible at all. For that purpose we had use JavaScript, SQL and ASP.NET
properties and functionalities , so that one have a safe and authorized access to the system
and feel free to use the system with security.

1.9 2.1.5 System Interaction

This function makes the system interact with the other modules, in the company which
makes the system increase its functionality.
Identify the interaction with other systems.
The system interacts with other modules such as PURCHASE AND STORE
INVENTORY, FIXED ASSETS RESERVATION SYSTEM etc. As per the interaction
is talked about hotel equipments, maintenance, AMCs etc. are all related to such kind of
modules in the provided HRS. As their dealings of assets of hotels, are in the hands of the
other departmental modules.

1.10 2.1.6 Physical Environment

Local communications under the consideration of the company/company franchise area
only.

1.11 2.2 Current Functional Procedures

[14]
The current functional procedure involves large paperwork and large staff to organize the
administration and Reservation process. Current functional procedure includes lots of
paper work which increases large amount of manual work collection and retrieval of the
information from database and sometimes it became completely unmanageable which
ultimately lead to the increase in assets of maintaining an unorganized way.
All in all current system is a complex; unorganized, unsecured, completely manually
operated, etc needs a new system to be implemented.

The current functional procedures of any existing system, whether automated or manual.
Specifically, document the major processing and data flow of the current system(s),
volume of work currently processed, costs incurred in operating the current system, skill
categories and number of staff required to operate and maintain the current system,
equipment used by the existing system, and any other factors that are unique to the
current system.

1.12 2.3 Functional Objectives

Functional objectives of the new system will be able to overcome most of the current
system demerits and flaws, which includes more security into the system, organized
collection of database makes retrieve information about a particular database in just a go,
decreases the manual work, less staff to handle the data etc are features will make it an
advance system from the current working system.

• Analyze the anticipated functions of the system,

considering such areas as new services, increased
capacity, legislative and policy requirements, privacy and
security requirements, audit controls, and target
completion date.

1.13 2.4 Performance Objectives

[15]
Major objective of this system will increase the performance by reducing the staff, reducing
paperwork, making data retrieval from the data quicker and easier, maintaining data in an
organized way, etc which ultimately leads to the efficient system development and the whole
system will work as its been designed to do. Identify major performance objectives, considering
such areas as reduced staff and equipment costs, increased processing speed, increased
productivity, improved Reservation information services, improved controls over automated
decision-making system(s), and compliance with regulations.

1.14 2.5 Assumptions and Constraints

Assumptions and constraints, these are included to document the specific requirements
on which the estimates, schedules, and there are factors considered in planning phase
involve a degree of risk (e.g.: if an activity needs special equipment, the project manager
may assume that it will be available).
Assumptions: The development team will be familiar with the quality standards needed
in the development of the module and will provide communication and technical support
in the installation. This module will be done with minimum of 1.0 GB RAM, processor,
monitor, back end for database, web browser or any other technical assumptions for
frontend. It may require large database memory to store the complete student information
while the process.
Constraints: Any later change in the project other than already listed may delay in the
scheduled data.
Determine the assumptions and constraints, such as operational life of the proposed
system; period of time for comparison of system alternatives; input, output, and
processing requirements; financial constraints; changing hardware, software, and
operating environment; and availability of information and resources.

1.15 2.6 Methodology

The methodology involved in this module provides the information of the hotels, hotels
stock, hotels requirements, hotel complaints, hotel description, hotel network diagram,
and equipment description. And all these information maintained by the hotel
administrator. If any modification needed in the hotels an administrator easily modify the
hotels information’s.

1.16 2.8 Recommendation

The proposed system is a solution to computerize all the manual Reservation work of
every hotel in the company. Hotel Reservation system provides the information about
each hotel in the company.

[16]
2 3.0 PROPOSED SYSTEM
2.1 3.1 Description of Proposed System

The proposed system has used the concept of database connectivity with asp.net. The
system will include:
• All the details of various hotels listed in company franchise.

• It will also keep the maintenance required and booking reservation stock of the
hotels.

• Provided password facility to limited users to access the application.

2.2 3.2 Improvements

The improvements in the proposed system will make a need of replacement of the current
system. The improvements are stated below:
• Automatic generation of new hotel system without doing much effort. Hardware
and software requirements will remain the same.

2.3 3.3 Time and Resource Costs

We are developing an HRS module which will require six months for completion. All the
necessary resources are provided by our trainers and company administration. So there
are limited resource requirements.

2.4 3.4 Impacts

The major impact it will cause to the Hotel/company administration and Reservation is
that it will reduce the load of work from the working staff members, reduces the load of
paperwork and also it saves time for lengthy back paining long hour workloads.

[17]
2.5 3.4.1 Equipment Impacts
The only need in terms of equipments will be the need of the more computer systems
then current working system for the efficient working of the system.

2.6 3.4.2 Software Impacts

The HRS module requires following modifications from the current application are:
• Need backend database to store the student information.

• Addition to backend, need any frontend software for the backend database
connectivity.

• Otherwise no software requirement is there.

• High featured web browser required.

2.7 3.4.3 Organizational Impacts

In order to maintain coordination between the different modules of the project the staff
needs to have some technical knowledge about the organization or the system and a
proper co-ordination among al the groups is also required.

2.8 3.4.4 Operational Impacts

Effects of different operations on the system, as:
• User operating procedures: User needs to have some
knowledge about the procedure to communicate with
system.
• Operating center procedures: Different operating center
(staff) has different facilities to operate with the system.
• Operating center/user relationships: The operating
center\user relationships will improve if we are provided
some information about the project from the company
franchise.
• Source data processing: this will depends on the needs in
project completion.
• Data entry procedures: all the data of various hotel assets
needs to be entered into the database to keep track on the
working and maintenance on the hotel assets.
[18]
 • Output reporting procedures, media, and schedules:
• System failure contingencies and recovery procedures:
Backup of the database is needed in case emergencies or
system failure.

2.9 3.4.5 Developmental Impacts

The developmental impacts in the application affects the functioning and these are:
• Resources required for developing databases: Backend for
storage. I.e. SQL SERVER 2005, etc.
• SRS, ER diagrams, DFD.S are the part of developmental
impacts.
• Computer processing resources required to develop and
test the new system: browser and server.
• Privacy and security implications: provided login interface
to authorized person belongs to different authorized
person of different procedures.

2.10 3.4.7 Security and Privacy Impacts

Security and privacy factors for the database may limit the services provided to the user
or the authenticated user.

The security and privacy factors that may influence the development, design, and
continued operation of the proposed system are all about the validations and
authentications using java scripts etc.

2.11 4.0 Alternative System

Alternative system for hotel Reservation system is window based application. For this
application we have no need of asp.net. This application can’t be used in the HRS
because it’s a separate application and for this we have need to make the administrator
server and various clients to work efficiently.

[19]
[20]
3 Requirement Specification

2.12 Document Conventions

Capital letters define the main section or function of the project like
HOTELS, BOOKING SECTION like that and bold letters define the
specific functionality of particular hotels. And the highlighted section
defines the project main parts.

2.13 Intended Audience and Reading Suggestions

This document is so helpful for the developers, project mangers as well
as marketing staff. With the help of this document developers analyze
the requirement of this project and what functioning are needed in this
project to make the project complete with maximum satisfaction of
user. Project manager easily manage the flow of project how it is work
with the project so that it can achieve the maximum completion of the
project. Project manager easily defining the time dead line of this
project so that project can be delivered on time. And the marketing
staff takes the idea of the project cost.

2.14 Project Scope

<Provide a short description of the software being specified and its
purpose, including relevant benefits, objectives, and goals. Relate the
software to corporate goals or business strategies. If a separate vision
and scope document is available, refer to it rather than duplicating its
contents here. An SRS that specifies the next release of an evolving
product should contain its own scope statement as a subset of the
long-term strategic product vision.>

2.15 References
List any other documents or Web addresses to which this SRS refers.
These may include user interface style guides, contracts, standards,
system requirements specifications, use case documents, or a vision

[21]
and scope document. Provide enough information so that the reader
could access a copy of each reference, including title, author, version
number, date, and source or location.

3 Overall Description

3.1 Product Perspective

<Describe the context and origin of the product being specified in this
SRS. For example, state whether this product is a follow-on member of
a product family, a replacement for certain existing systems, or a new,
self-contained product. If the SRS defines a component of a larger
system, relate the requirements of the larger system to the
functionality of this software and identify interfaces between the two. A
simple diagram that shows the major components of the overall
system, subsystem interconnections, and external interfaces can be
helpful.>

3.2 Product Features

<Summarize the major features the product contains or the significant
functions that it performs or lets the user perform. Details will be
provided in Section 3, so only a high level summary is needed here.
Organize the functions to make them understandable to any reader of
the SRS. A picture of the major groups of related requirements and
how they relate, such as a top level data flow diagram or a class
diagram, is often effective.>

3.3 User Classes and Characteristics

<Identify the various user classes that you anticipate will use this
product. User classes may be differentiated based on frequency of use,
subset of product functions used, technical expertise, security or
privilege levels, educational level, or experience. Describe the
pertinent characteristics of each user class. Certain requirements may
pertain only to certain user classes. Distinguish the favored user
classes from those who are less important to satisfy.>

3.4 Operating Environment

<Describe the environment in which the software will operate,
including the hardware platform, operating system and versions, and

[22]
any other software components or applications with which it must
peacefully coexist.>

3.5 Design and Implementation Constraints

<Describe any items or issues that will limit the options available to
the developers. These might include: corporate or regulatory policies;
hardware limitations (timing requirements, memory requirements);
interfaces to other applications; specific technologies, tools, and
databases to be used; parallel operations; language requirements;
communications protocols; security considerations; design conventions
or programming standards (for example, if the customer’s organization
will be responsible for maintaining the delivered software).>

3.6 User Documentation

<List the user documentation components (such as user manuals, on-
line help, and tutorials) that will be delivered along with the software.
Identify any known user documentation delivery formats or
standards.>

3.7 Assumptions and Dependencies

<List any assumed factors (as opposed to known facts) that could
affect the requirements stated in the SRS. These could include third-
party or commercial components that you plan to use issues around
the development or operating environment, or constraints. The project
could be affected if these assumptions are incorrect, are not shared, or
change. Also identify any dependencies the project has on external
factors, such as software components that you intend to reuse from
another project, unless they are already documented elsewhere (for
example, in the vision and scope document or the project plan).>

4 System Features
Hotel Reservation system has following features and functionality.
These features and functionality makes it efficient for the end user.

4.1 Web based application

Hotel Reservation system is a web based application it can be access
though out the organization with the proper login or it can accessed
outside the organization if secure password and id provided to the

[23]
 users. Users provide a domain name trough which they can access the
particular system with the help of computer which connects in the
network.

4.2 no paper work

In hotel Reservation system there have no need to the end user do the paper work. All
the work done in the computerized system. And it can easily store the entire hotel
regarding information safely. There have no need to manage the stock register,
complained register etc.

4.3 User authentication

In hotel Reservation system different types of user have different rights. Like in this
system all the hotel maintained by the hotel administrator and only administrator have all
the authentication like to maintain the hotel information, modify the hotel information
etc. Any other users instead of administrator have no authentication to maintain or
modify the hotel information.

4.4 Provide security

Hotel Reservation system provides the security to its user. In this each user have its own
id and password though which they access the hotel Reservation system if there have no
password and id it can’t login in the hotel Reservation system.

4.5 Online work

In this all the work done online there have no need to end user to maintain the register for
hotel information. User just login in the hotel Reservation system and do the works
according there need and save that work and logout.

4.6 fast and easily access

If user is valid then it can access the information easily, vastly access the information
throughout the organization.

5 External Interface Requirements

5.1 User Interfaces

In the hotel Reservation system there have a home page thought which
different hotel administrator can login in the different hotel section like
ADD TO HOTEL SECTION, BOOKING STATUS SECTION, and HOTEL GUIDE
SECTION. After clicking on hotel section a login page is appeared though
which they can login if administrator is valid otherwise it can’t access the
hotel section. Here snapshot describe these interfaces...

[24]
HOME PAGE

[25]
AFTER CLICKING ON FEEDBACK SECTION

[26]
Same interface corresponding to ADD TO HOTEL SECTION, BOOKING
STATUS SECTION, and HOTEL GUIDE SECTION.

5.2 Interfaces Hardware

To run this application we have need different types of hardware
device. These are following as

Processor – 3.0 GHz,

Ram – 1 GB,

HDD – 80 GB,

Switches, Router,

Transmission Media – co-axial cable, optical fiber, Wi-Fi modem etc

Keyboard,

Mouse,

Monitor.

When user run this application or accesses this application on

particular computer which is connected in the network. It give the
domain name of the hotel Reservation system application in the
internet explored window and click on the go button then that request
send by the user computer to sever computer via transmission media
(using router or switches it fetch the path of the server computer and)
than server give the response corresponding to that request in this
way all the interfaces interact with the hardware device and network
devices and the sever computer. It uses the http protocol to send and
receive the request on the both side.

5.3 Software Interfaces

Hotel Reservation system is loaded on a high configured server
machine and this machine has a large storage database for storing or
retrieving the information regarding hotels.

[27]
For the database purpose SQL SERVER 2005 is used to make the
database server where we can easily send the request for storing or
retrieving the data.

To run this application ASP.NET SERVER 3.0 is used. Because hotel

Reservation system is developed in the asp.net (server side scripting
language) and all the codes executes where the asp.net server is
installed then it send these executed code to web browser.

To run this application efficiently with more user friendly at the client
side MOZILA WEB BROWESER is used.

Any operating system where Mozilla web browser installed.

TCP/IP protocol is used to communicate with the server. Here request

send by the client using TCP/IP, HTTP protocols to the server and
server receive the request and send the response to the client through
the TCP/IP, HTTP protocol.

Here a centralized data base is used to store or retrieve the

information.

<Describe the connections between this product and other specific

software components (name and version), including databases,
operating systems, tools, libraries, and integrated commercial
components. Identify the data items or messages coming into the
system and going out and describe the purpose of each. Describe the
services needed and the nature of communications. Refer to
documents that describe detailed application programming interface
protocols. Identify data that will be shared across software
components. If the data sharing mechanism must be implemented in a
specific way (for example, use of a global data area in a multitasking
operating system), specify this as an implementation constraint.>

5.4 Communications Interfaces

<Describe the requirements associated with any communications
functions required by this product, including e-mail, web browser,
network server communications protocols, electronic forms, and so on.

[28]
Define any pertinent message formatting. Identify any communication
standards that will be used, such as FTP or HTTP. Specify any
communication security or encryption issues, data transfer rates, and
synchronization mechanisms.>

6 Other Nonfunctional Requirements

6.1 Performance Requirements

<If there are performance requirements for the product under various
circumstances, state them here and explain their rationale, to help the
developers understand the intent and make suitable design choices.
Specify the timing relationships for real time systems. Make such
requirements as specific as possible. You may need to state
performance requirements for individual functional requirements or
features.>

6.2 Safety Requirements

<Specify those requirements that are concerned with possible loss,
damage, or harm that could result from the use of the product. Define
any safeguards or actions that must be taken, as well as actions that
must be prevented. Refer to any external policies or regulations that
state safety issues that affect the product’s design or use. Define any
safety certifications that must be satisfied.>

6.3 Security Requirements

<Specify any requirements regarding security or privacy issues
surrounding use of the product or protection of the data used or
created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing
security issues that affect the product. Define any security or privacy
certifications that must be satisfied.>

6.4 Software Quality Attributes

<Specify any additional quality characteristics for the product that will
be important to either the customers or the developers. Some to
consider are: adaptability, availabiility, correctness, flexibility,
interoperability, maintainability, portability, reliability, reusability,
robustness, testability, and usability. Write these to be specific,
quantitative, and verifiable when possible. At the least, clarify the

[29]
relative preferences for various attributes, such as ease of use over
ease of learning.>

7 Other Requirements
<Define any other requirements not covered elsewhere in the SRS.
This might include database requirements, internationalization
requirements, legal requirements, reuse objectives for the project, and
so on. Add any new sections that are pertinent to the project.>

[30]
4 Design Specification

USE CASE DIAGRAM

[31]
 CONTEXT DIAGRAM
UNREGISTER
USER ADMINISTRATOR

HOTEL
BOOKING
WEBSITE.

REGISTERED
USER

[32]
ACTIVITY DIAGRAM

[33]
ACTIVITY DIAGRAM

[34]
ACTIVITY DIAGRAM

[35]
ACTIVITY DIAGRAM

[36]
STATIC PAGES

[37]
FILE SYSTEM

[38]
 DATABASE STRUCTURE

1. “CustomerDetails” table

a. Username(primary key)

b. User_Type

c. Password

d. Gender

e. Emailid

f. Date_of_Birth

g. Country

h. City

i. Address

j. Zipcode

k. Occupation

2. “_HotelDetails” table

a. Hotel_ID (primary key)

b. Username

c. Hotel_Name

d. Room_Rate

e. Hotel_Address

f. City

g. Website (optional)

[39]
 h. Description

i. Amenities

j. Reachability

k. No_of_Rooms

l. Contact_No

m. Country

n. Image (optional)

3. “_HotelReviews” table

a. Comment_No (primary key)

b. Hotel_ID

c. Hotel_Name

d. FullName

e. Emailid

f. Comments

4. “_SearchResults” table

a. Hotel_ID (primary key)

b. Hotel_Name

c. Room_Rate

d. Hotel_Address

e. City

f. Website (optional)

g. Description
[40]
 h. Amenities

i. Reachability

j. No_of_Rooms

k. Contact_No

l. Country

m. Image

n. Rooms

5. “Feedback” table

a. FullName

b. Emailid

c. Comments

6. “Booking” table

a. Comments

b. BookingID (primary key)

c. FullName

d. Gender

e. Date_of_Birth

f. Address

g. Country

h. City

[41]
i. Zipcode

j. ContactNo

k. Emailid

l. DateBookingFrom

m. DateBookingTo

n. No_of_Rooms

o. No_of_Adults

p. No_of_Children

q. CCNo

r. Validupto

s. Last4Digits

t. Booking_Date

u. Amount

v. HotelSelected

[42]
LIMITATIONS
• There is no category in rooms provided by
hotels.
• A user can be either a Customer or an
Agent, but not both.
• A hotel cannot be booked in Hotel Guide
Section.

[43]
5 SNAPSHOTS

HOME PAGE

[44]
ADD HOTELS

[45]
[46]
BOOK HOTELS: 1

[47]
BOOK HOTELS: 2

[48]
BOOK HOTELS: 3

[49]
ADMIN PANEL

[50]
REVIEWS

[51]
FEEDBACK

[52]
BOOKING STATUS

[53]
 6 Conclusion

The following conclusions have been achieved:

 Smooth flow of data without any hurdles.
 Adequate validation checks for data entry.
 Adequate security of data.
 Facility to update data from time to time.
 Prompt and specific retrieval of data.
 Flexibility in the system according to the changing
environment.
 Controlling redundancy in storing the same data
multiple times.
 Accuracy, timeliness and comprehensiveness of the
system output.
 Stability and operability by people of average
intelligence.

[54]
 7 Bibliography

Bibliography or References must be included in the report according to the format given
in the following examples. References should be cited properly inside the text of the
report.

1. Asp.Net Bible.
2. Asp.Net Complete Reference
3. www.codeguru.com
4. www.devex.com
5. www.verahotel.com

1. BOOK

Title: Implementations Using ASP.NET and C#.NET

Author: Ralf Sudelbucher
Publications: TMG Publications 2005.

[55]
 8 Checklist
This checklist is to be attached as the last page of the report.

This checklist is to be duly completed by the student and verified by the

Programme Coordinator and HOD

1. Is the report properly spiral bound? Yes / No

2. Is the Cover page in proper format? Yes / No

3. Is the Title page in proper format? Yes / No

4. (a) Is the Certificate from the Supervisor in proper format? Yes / No

(b) Has it been signed by the Supervisor? Yes / No

5. (a) Is the Acknowledgement from the Student in proper Yes / No

format?

(b) Has it been signed by the Student?

7. Does the Table of Contents include page numbers? Yes / No

(i). Are the Pages numbered properly? Yes / No

(ii). Are the Figures numbered properly? Yes / No

(iii). Are the Tables numbered properly? Yes / No

(iv). Are the Captions for the Figures and Tables proper? Yes / No

(v). Are the Appendices numbered properly? Yes / No

8. Is the conclusion of the Report based on discussion of the Yes / No

work?

9. Are References or Bibliography given in the Report? Yes / No

Have the References been cited inside the text of the Report? Yes / No

Is the citation of References in proper format? Yes / No

[56]
10. A Compact Disk (CD) containing the softcopy of the Final Yes / No
Report (preferably in PDF format) and a Final Project
Presentation in MS power point only (made to the Supervisor /
Examiner has been placed in a protective jacket securely
fastened to the inner back cover of the Final Report. Write the
name and Roll No on the CD.

Declaration by Student

I certify that I have properly verified all the items in the checklist
and ensure that the report is in proper format as specified in the
course handout.

Name:
Place:
Date:
Signature of the Student:

Verification by HOD

I have duly verified all the items in the checklist and ensured that the
report is in proper format.

Name:
Place:
Date:
Signature of the HOD:

Verification by Programme Coordinator

I have duly verified all the items in the checklist and ensured that the
report is in proper format.

[57]
Name:
Place:
Date:
Signature of the Programme Coordinator:

[58]