Hotel Management

Developed By :

1
Hotel Management

CERTIFICATE

This is to certify that Mr./Ms. of M.C.A–

Semester V has successfully completed his/her project work

on “Online Hotel Management ” during the academic

year 2010-11.

Dr. Anil Patel

(Project Guide) (Director)

2
Hotel Management

CERTIFICATE

This is to certify that Mr./Ms. of M.C.A – Semester V has

successfully completed his/her project work on “ Online

Hotel Management” during the academic year.

(Project Guide) (Director)

3
Hotel Management

ACKNOWLEDGEMENT

PROJECT ABSTRACT

Here we have developed a project on Online Hotel Management To reduce The effort for
booking any room or facility of any hotel.

By using our project any customer or user can send inquiry for getting
information about all the facility available in hotel and also hotels available in different
Cities so our project can be very help full for all the customer.

We have added so many forms and function which makes project user
friendly And easy to understand.

We have tried to add that type of controls and functions which can be easily
understand the whole project easily by any technical person.

4
Hotel Management

Index
TABLE OF CONTENTS
Title Page No
COVER PAGE………………………..………………………………………....1
COLLEGE CERTIFICATE………………………………………................... 2
ACKNOWLEDGEMENT………………………………………....................... 4
ABSTRACT…………………………………………………………………….. 5

CHAPTER-1 Introduction…………………………………………………….
1.1 Project Summary ………………………………………………….. 9
1.2 Purpose …………………………………………………………….. 9
1.3 Scope…………………………………………………………………10
CHAPTER-2 Project Management……………………………………………
2.1 Project Planning and Scheduling…………………………………...12
2.2 Risk Management……………………………………………………17

5
Hotel Management

2.3 Estimation……………………………………………………………20
CHAPTER-3 System Requirement Study……………………………………..
3.1 User Characteristics…………………………………………………24
3.2 Hardware and software Requirements…………………………….24
CHAPTER-4 System Analysis………………………………………………….
4.1 Requirements of new system……………………………………….26
4.2 Feasibility Study…………………………………………………….31
4.3 Requirements Validation …………………………………………..32
4.4 Function of System………………………………………………….32
4.5 Data Dictionary…………………………………………………….....32
4.6 Data Flow Diagram………………………………………...............33
4.7 E-R Diagram………………………………………………..
CHAPTER-5 System Design……………………….……………………………5.1
Database Design……………..….……………………………………37
5.2 Input Output and Interface Design….……………………..……….38

CHAPTER-6 Implementation Detail……………………………

6.1 Security Features…………………………………………………….41
6.3 Coding Standards……………………………………………………41
CHAPTER-7 Testing……………………………………………..
7.1TestingPlan……………………………………………………………48
7.2TestingStrategy………………………………………………………..44
7.3TestingMethods…………………..…………………………………....46
7.4 Test Cases……………………………………………………………..48

CHAPTER-8 Screenshots and User Manual…………………………………………49

CHAPTER-9 Conclusion and Discussion……………………………………………..55

6
Hotel Management

7
Hotel Management

1. INTRODUCTION

1.1 PROJECT SUMMARY

Online Hotel Management is a very user friendly project. In this project user can easily
understand and fill up the Room Reservation form. In this project there are various types
of forms are there like Room Registration Page in which user can insert his Personal,
Needs & facilities then upload his form by which user can register in the web site & can
search for various class of rooms.

8
Hotel Management

In this project all the forms which user want to fill up its totally easy to understand. So in
any way user is not disturbed or not confuse at all, anyone can easily fill up room
reservation form it’s totally user friendly form. by the help of this forms user can easily
apply for the room reservation which are empty in hotel, and management can also call
the customer for the confirmation so all the customer can easily get all facilities.
.
1.2 PURPOSE

 GOALS & OBJECTIVES

 The Purpose of the project is very clear that user can find room facilities easily &
hotel service Providers also get good customer very easily. Customer can register
in the website & can create his own registration then he can receive email for his
room status related to his reservation. The hotel can register in web site & can so
user can see status.

 The Main Goal of this project is to provide an verry faster room reservation
services so any user can get this service verry easily.

 The goal of my project is that I want my project totally user friendly project and I
hope I get success. When I make the project I kept one thing in my that when user
fills up various types of forms , there are not any kind of confusion are there , any
one which is technical person apart from the technical field and non technical
person both type of person are easily understand about the fields and easily fill up
it.

 It saves lots of time , now a days there is a fast process world any one can work
fastly so, this project help that people who are searching for reservation in
organization, so they can easily fill up the form and search rooms.

9
Hotel Management

 So, Online Hotel Management is a web based application made in the Asp.Net. So
with the help of this project user can applied for the vacant or empty rooms get
email about related status of rooms.
1.3 SCOPES

Online Hotel Management is a totally web based application made in Asp.Net. With
the help of this project a user can fill up the room related forms like Personal
information, Professional information, info etc are the various kinds of Details are
there. With the help of this forms customer can fill up the forms accurately, and
admin can also know about the customer and admin feels that this candidate is
appropriate for that particular post so admin can approve the customer for the
Website Member. So this process is a very fast process and accurate also.

As we know that online Hotel Management is a web based application. So user

which is operate this software much of knowledge about the internet and how to
operate the internet.

User have to fill up the right data or information in the forms and it is accurate there
is a no mistake in the fill up.

2. PROJECT MANAGEMENT

10
Hotel Management

2.1 PROJECT PLANNING & SCHEDULING

2.1.1 Project Development Approach

To solve actual problems in an industry setting, a software development strategy must be
incorporated that encompasses the process, methods and tools for software engineering.
This strategy is often referred to as Software Process Model or Software Engineering
Paradigm. A software process model for software engineering is chosen based on the
nature of project and application, the methods and tools to be used and the controls and
deliverables that are required.

For the development and implementation of web based module several distinct approach
are in practice. Among them, we have chosen a very popular one, The Classical System
Development Life Cycle Model or the Waterfall Model. This approach is classically

11
Hotel Management

thought of as a set of six interrelated activities that make up the entire system
development life cycle.

Water Fall Model:

This is also called Classic Life Cycle Model or Linear Sequential Model or Software
Development Life Cycle Model (SDLC). This model has the following activities:

1. System Information Engineering and Modeling

2. Software Requirement Analysis
3. System Analysis and Design
4. Code Generation
5. Testing
6. Maintenance

12
Hotel Management

1) System/Information Engineering and Modeling

As software development is large process so work begins by establishing requirements
for all system elements and then allocating some subset of these requirements to
software. The view of this system is necessary when software must interface with other
elements such as hardware, people and other resources. System is the very essential
requirement for the existence of software in any entity. In some cases for maximum
output, the system should be re-engineered and spruced up. Once the ideal system is
designed according to requirement, the development team studies the software
requirement for the system.

13
Hotel Management

2) Software Requirement Analysis

Software Requirement Analysis is also known as feasibility study. In this requirement
analysis phase, the development team visits the customer and studies their system
requirement. They examine the need for possible software automation in the given
software system. After feasibility study, the development team provides a document that
holds the different specific recommendations for the candidate system. It also consists of
personnel assignments, costs of the system, project schedule and target dates.
The requirements analysis and information gathering process is intensified and focused
specially on software. To understand what type of the programs to be built, the system
analyst must study the information domain for the software as well as understand
required function, behavior, performance and interfacing. The main purpose of
requirement analysis phase is to find the need and to define the problem that needs to be
solved.

3) System Analysis and Design

In this face, the whole software development process, the overall software structure and
its outlay are defined. In case of the clients/server processing technology, the number of
tiers required for the package architecture, the database design, the data structure design
etc are all defined in this phase. After designing part a software development model is
created. Analysis and Design are very important in the whole development cycle process.
Any fault in the design phase could be very expensive to solve in the software
development process. In this phase, the logical system of the system product is
developed.

4) Code Generation
In Code Generation phase, the design must be decoded into a machine-readable form. If
the design of software product is done in a detailed manner, code generation can be
achieved without much complication.

14
Hotel Management

5) Testing
After code generation phase the software program testing begins. Different testing
methods are available to detect the bugs that were committed during the previous phases.
A number of testing tools and methods are already available for testing purpose.

6) Maintenance
Software will definitely go through change once when it is delivered to the customer.
There are large numbers of reasons for the change. Change could happen due to some
unpredicted input values into the system. In addition to this the changes in the system
directly have an effect on the software operations. The software should be implemented
to accommodate changes that could be happen during the post development period.

2.1.2 Project Plan

In this project, we went through Module Wise Completion. First we did analysis of first
module; we went through all the requirements for first module that is File Upload
Module. By this analysis we decided field of all the tables of File Upload Module. Then
we started Database Design. After competing it we started with the design of all forms of
this module. Then we did coding and finally validations and testing of forms that we
made.

After completion of the first module we started the same procedure for the Searching
Module. Between this we did settings forms e.g. Change theme, change background
color of the main screen etc. There was continuously interaction with the client that was
very beneficial for us.

When we completed whole project we started testing the whole project for final
verification. Then we started documentation of our project. Finally, we completed the
project with as per requirement.

15
Hotel Management

2.1.3 Schedule Representation

Work `Task Jan-12 Jan-26 Feb-30 Mar-15 Mar-30 Apr-25

Specification

DB Study

GUI Design

Code DB Part

Code GUI

Integrating &
Testing

Manual

16
Hotel Management

2.2 RISK MANGEMENT

2.2.1 Risk Identification

 Technical Risks
Technical risks threaten the quality and timeliness of the software to be produced. If a
technical risk becomes a reality, implementation may become difficult or impossible.
Technical risks identify potential design, implementation, interface, verification, and
maintenance problems.

 Business Risks
Business risks threaten the visibility of the software to be built. Business risks often
jeopardize the project or the product. Candidates for the top five business risks are
(1) Building an excellent product or system that no one really wants.
(2) Building a product that no longer fits into the overall business strategy for the
company
(3) Building a product that the sales force doesn’t under stand how to sell
(4) Losing the support of senior management due to a change in focus or a change
in people and
(5) Losing budgetary or personnel commitment.
 Product Size
Risks associated with the overall size of the software to be built or modified.

 Process definition
Risks associated with the degree to which the software process has been defined and is
followed by the development organization.

17
Hotel Management

2.2.2 Risk Analysis

 Risk Table.

Risks Category Probability Impact

Delivery deadline will be tightened BU 50% 2

End-Users resist system BU 40% 3
Customer will change requirements PS 80% 2
Technology will not meet exceptions TE 30% 1
Staff Inexperienced ST 30% 2
Lack of training on tools DE 80% 3
Less reuse than planned PS 70% 2

Category: Impact values:

BU - Business impact 1 - catastrophic
PS - Product Size 2 - critical
TE – Technology to be built 3 - marginal
DE – Development Environment 4 - negligible
ST – Staff size and experience

 In any software the analysis part is the most important part. In risk
management the programmer or software developer can think seriously
about the risk like what kind of risks are there in the project if the risks are
solvable or not or what is the solution or which way he or she can solve the
risk this the main things comes into the analysis part . if this part is good
means developer can analyze the risk so there is a no chance of risk and if
possibly risk is come so it is easily solve

 So if developer or programmer can analyze about the risks related to their

project there is a no or less chance of errors and make a nice project. So
risk analysis is the good part to remove the risk or prevent your project to
future risks.

18
Hotel Management

2.2.3 Risk Planning

To assist the project team in developing a strategy for dealing with risk, an effective
strategy must consider three issues:
 Risk avoidance.
 Risk Monitoring.
 Risk management and contiguous planning
 Risk Mitigating
 Meet with current staff to determine causes for turnover
 Mitigate those causes that are under our control before the project starts.
 Once the project commences, assume turnover will occur and develop techniques
to ensure continuity when people leave.
 Organize project teams so that information about each development activity is
widely dispersed.
 Define documentation standards and establish mechanisms to ensure that
documents are developed in a timely manner.
 Assign a backup staff member for every critical technologist.

 Risk Monitoring
 General attitude of team members based on project pressures.
 The degree to which the team has jelled.
 Interpersonal relationships among team members.
 Potential problems with compensation and benefits.
 The availability of jobs within the company and outside it.
 RMMM Plan
 A risk management strategy can be included in the software project plan or the risk
management steps can be organized into a separate Risk Mitigation, Monitoring and
Management Plan.
 The RMMM plan documents all work performed as part of risk analysis and is used
by the project manager as part of the overall project plan.

19
Hotel Management

2.3 ESTIMATION
2.3.1 Effort Estimation

Today software is the most expensive element of virtually all computer-based systems.
For complex, custom systems, a large cost estimation error can make the difference
between profit and loss. Cost overrun can be disastrous for the developer.

Too many variables-human, technical, environmental, political-can affect the ultimate

cost of software and effort applied to develop it. However, software project estimation
can be transformed from a black art to a series of systematic steps that provide estimates
with acceptable risk.

To achieve reliable cost and effort estimates, a number of options arise:

 Delay estimation until late in the project.

 Base estimates on similar projects that have already been completed.
 Use relatively simply decomposition techniques to generate project cost and effort
estimates.
 Use one or more empirical models for software cost and effort estimation.

20
Hotel Management

The COCOMO Model

Like all estimation models for software, the COCOMO models require sizing
information. Three different sizing options are available as part of the model hierarchy:
object points, function points, and lines of source code.

Like functional points, the object point is indirect software that is computed using counts
of the number of

(1) Screens (at the user interface),

(2) Reports,
(3) Components likely to be required to build the application.

Once complexity is determined, the number of screens, reports, and components are
weighted according to Table above. The object point count is then determined by
multiplying the original number of object instances by the weighting factor in table above
and summing to obtain a total object point count. When component based development or
general software reuse is to be applied, the percent of reuse (%reuse) is estimated and the
object point count is adjusted:

NOP = (object points) X [(100 - %reuse) / 100]

Where NOP is defined as new object points. To derive an estimate of effort based
on the computed NOP value, a “productivity rate” must be derived. Table below
presents the productivity rate

PROD=NOP / person-month

For different levels of developer experience and development environment

maturity. Once the productivity rate has been determined, an estimate of project
effort can be derived as

Estimated effort = NOP/PROD

21
Hotel Management

2.3.2 Cost Analysis

Cost-benefit analysis is a term that refers both to:

 A formal discipline used to help appraise, or assess, the case for a project or
proposal, which itself is a process known as; and
 An informal approach to making decisions of any kind.

A cost-benefit analysis `is necessary to determine economic feasibility. The Primary

objective of the cost-benefit analysis is to find out whether it is economically worthwhile
to invest in the project. If the return on the investments is good, then the project is
considered economically worthwhile.

Cost-benefit analysis is performed by first listing all the costs associated with the project.
Costs consist of direct costs and indirect costs. Benefits can be broadly classified as
tangible benefit and intangible benefits. Tangible benefits are directly measurable and
intangible are not.

The sum of all costs is compared with the sum of all the savings (tangible and intangible).
It is not always easy to assign money value to intangible benefits. It is arrived at by
discussion amongst users of the system.

22
Hotel Management

3. PROJECT
REQUIREMENT STUDY

23
Hotel Management

3.1 USER CHARACTERISTICS

The user must have basic knowledge of the Computer. User must be familiar with all the
application whose documents are used in the system. The user must be familiar with these
computer based system and their operations done in the system.

3.2 HARDWARE AND SOFTWARE REQUIREMENTS

3.2.1 Hardware Requirement

Server Side Configuration

Processor : Pentium IV or above (Preferred Dual Core)
Disk Capacity : 20 GB or above
Memory : 512 RAM
Monitor : should support 800X600 Resolution
Ethernet Card : Ethernet or compatible network connection to clients
Client Configuration
Machine capable of running web browser (e.g. Microsoft Internet Explorer,
Mozilla Firefox)
Compatible Network Connection to Server
3.2.2 Software Requirement

Server Side Configuration

Software Needed : Visual Studio .Net 2008 (Frame Work 3.5)
Microsoft SQL Server 2005
Operating System : Windows 2000 or Higher Server OS

Client Configuration
Windows98 or higher OS
Compatible web browser

24
Hotel Management

4. SYSTEM ANALYSIS

25
Hotel Management

4.1 REQUIREMENTS OF NEW SYSTEM

 The company wants to develop web application to be accessed at remote place

also.

 Time and work of Job Seeker & Job Provider can reduced

 The system must be authorized; no unauthorized user can access this application.

 The system must be accessible to each branches of company.

 The system must be able to store Resume details, Seeker details & Provider
details etc.

 Advanced Searching facilities must be included. Seeker can search job by

location, by Job Category, by Company name etc.

 Similarly Admin can search all details about Seekers, New Jobs Posted and Job
Providers etc.

 The system should be convenient and work according to the Company

Requirements.

 System engineering provides the appropriate mechanism for understanding what

the customer wants ,analyzing need, assessing feasibility ,negotiating a reasonable
solution, specifying the solution unambiguously, validating the specification and
managing the requirements as they are transformed into an operational system.
The system requirement engineering process can be described into following
distinct steps:

26
Hotel Management

 Requirement Analysis

In Requirement analysis, we met to the company head and project guide. We

discussed about their requirements and the problems they are facing with existing
system.
 Fact Finding Technique

During requirement determination phase, the system analyst has to find out how
the current system works and what is expected from a new system. For that it is
required to spend considerable time in talking with users and gathering all
relevant information on the project.
 Information Sources

Main sources of information are:

 User of the system.
 Documents used in the organization.
 Procedure manuals and rulebooks, which specify how various activities,
are carried out in the organization.
 Various reports used in the organization.

 Methods of Searching Information:-

Interviewing Technique
The primary purpose of interviewing is to obtain both quantitative and qualitative
data regarding user requirements, policies, procedures and practices.

Questionnaires
Detailed questionnaires are useful to gather quantitative information. They are to
substitutes for interview, as questionnaires do not get qualitative information. The
short a questionnaire, the higher is the probability of getting replied back quickly.

27
Hotel Management

 Requirement Specification
The term specification means “different things to different people”.
Analysis of data will describe the system to determine how well it is performing,
what requirements must be met, and strategies for fulfilling them.
Following activities are important and must be performed correctly.
 Analysis of actual data
The data collected during the fact finding study and included in data flow and
decision analysis documentation are examined to determine how well the system
is performing and whether it will.
Meet the organization’s demand.
 Identification of essential requirements
Features that must be included in the new system, ranging from operational
details to performance criteria, are specified.
4.1.1 Functional Requirement.

 The user fill up the data that data store in the back end and the administrator can
easily watch all the process.

4.1.2 Non-Functional Requirements

 The database must be affected accordingly by the user’s interactions and only
authorized use can access the forms and operations.

 In case of sudden disaster the user must be able to recover the project. It should be
reliable in case of disaster.

 Reliability
Reliability could be defined as an extend to which application can be perform its
intended function with required precision. It is evaluated by measuring the
frequency and severity of failure and the ability to recover from failure. Thus the

28
Hotel Management

application should be as reliable as possible to overcome the failure and recover

from it.
 Maintainability
The application to be developed should be easily maintained and should locate
undiscovered error and fix them as soon as possible. For maintenance of the
application the contact number of the application provider would be given to the
end user to resolve the queries.
 Portability
Portability means an effort to transfer the application from one hard ware and/or
software system environment to another. Our application is to be developed in
ASP.Net, so the application can be install on various Windows Platform but the
.Net framework needs to be installed.

 Efficiency
The application should make optimal use of system resources. Also the runtime
performance of the system should be considered.
 Effective storage, search and retrieval from the exhaustive database.
 It has an attractive GUI with emphasis on being user-friendly.

4.1.3 Domain Requirements

Only the administrator should be able to delete the records no other users can delete
records from project .The authorization of users must work properly.
Software Requirement Analysis
The requirements gathering process is intensified and focused specifically on software.
Software requirements analysis encompasses understanding the information domain for
the software as well as required function, performance, behavior and interfacing.
Requirements for both the system and the software are documented and reviewed with
the customer.

 Design

29
Hotel Management

Software design is a multi-step processes that focus on four distinct attributes of a

program; data structure, software architecture, interface representation and procedural
details. The process translated requirements into a representational the software that can
be assessed for quality before code generation begins. The design is documented and
becomes part of the software configuration.
 Code Generation

The design is translated into a machine – readable form. If design is performed in a

detailed manner, code generation can be accomplished mechanistically.

 Testing

The testing process focuses on the logical internals of the software, assuring that all
statements have been tested, and on the functional externals i.e. conducting tests to
uncover errors and ensure that defined input will produce actual results that agree with
required results.

 Maintenance

Software maintenance applies to following phases in the existing program

 Change in software due to errors.
 Change in software because the software must be adapted to accommodate
changes in its external environment.
 Change in software when the customer requires functional or performance
enhancements.

4.2 FEASIBILITY STUDY

30
Hotel Management

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

 As from the feasibility study that we carried out, we can say that the system
contributes to the over all objectives of the organization for which the system is being
developed.

 An important outcome of the preliminary investigation i.e. after defining the scope of
the project, the determination that the system requested is feasible or not is required
to done.

 4.2.2 Can the system be implemented using the current technology and within
the given cost and constraints?

 The system has been developed using the current technologies and maintaining the
given specification and the requirements by the organization.

 From the study of Economic Feasibility we can say that the system that has been
developed can be implemented with the given cost and constrains.

 From the study of Technical Feasibility, the system developed can be implemented
using the current technologies.

4.2.3 Can the system be integrated with other systems that are already in place?

 As said earlier that this is a system of managing the pre- production and post-
production process.

 So this is a system that can be used separately. So from the study Operational
Feasibility we can say that it has been developed in such way that it can be integrated
with other system and also with the current system that is already in place. But as this
system varies with the type of organization so it definitely depends on the type of
organization with whose system the new system can be integrated.

4.2 REQUIREMENTS VALIDATIONS

31
Hotel Management

 It means that the developed software is as per requirement or not? Simply stating
whatever we are doing is right or wrong as per requirements?

 Here we check each and every requirement and compare with our product and that it
satisfies the user need.

4.3 FUNCTIONS OF SYSTEM

4.3.3 Use Cases

 Use case specifies the behavior of the system. Use case diagrams show the various
actors and their roles which they have to perform in the system.

 Use case diagrams overview the usage requirements for a system. They are useful for
presentations to management and/or project stakeholders, but for actual development
you will find that use cases provide significantly more value because they describe "t
he meat" of the actual requirements.

4.4 Data Dictionary

Data is the key to the overall system design and must be structured to meet the user
requirement. The collection of structured data builds up data dictionary, which is an
important tool in data flow analysis. The complete set of data definitions provides the
basis of the data dictionary. It facilitates cross-referencing and assessment of the
implication of changes. Each data item is uniquely identified by its definitions but
referred by different name at different tables.

1. Admin Login

32
Hotel Management

Fields Name Type Constraint

AdminName nvarchar(50) Auto Incre

Password nvarchar(50)

2. City

Fields Name Type Constraint

CityId bigint Auto Incre

CityName nvarchar(50)

3. Hotel

33
Hotel Management

Fields Type Constraint

HotelId bigint Auto Incre.

HotelName nvarchar(100)

CityId bigint

Address Text

State nvarchar(50)

Phone nvarchar(50)

HotelDiscription Text

Email nvarchar(100)

ImageUrl nvarchar(250)

4. Hotel Image

Fields Type Constraint

ImageId Bigint Auto Incre
HotelId Bigint
ImageUrl nvarchar(200)

5. Hotel Room

34
Hotel Management

Fields Type Constraint

HotelRoomId Bigint Auto incre.

RoomTypeId Bigint

HotelId Bigint

NoOfRoom Bigint

RoomPrice Numeric(18, 2)

6. Message

Fields Type Constraint

MessageID Bigint Auto incre.

HotelID Bigint

SenderName Nvarchar(50)

SenderEmail Nvarchar(50)

SenderPhone Nvarchar(50)

Message Text

SendDate Datetime

35
Hotel Management

DATA FLOW DIAGRAM

 Basic explanation about Data flow diagram:-

As information moves through software, it is modified by a series of

transformations. A Data Flow Diagram (DFD) is a graphical technique that
depicts information flow and the transformations that are applied as data move
from input to output. The data flow diagram is know as a data flow graph or a
bubble chart.

The Data Flow Diagram may be used to representation a system or

software at any level of abstraction. In fact, DFDs may be used partitioned into
levels that represent increasing information flow and functional detail. Therefore,
the DFD provides a mechanism for functional modeling as information flow
modeling.

The Data Flow Diagram (DFD) serves two purposes:

1) To provide an indication of how data are transformed as move

through the system
2) To depict the functions that transform the data flow. The DFD
provides additional information that is used during the analysis of the
information domain and serves as a basis for the modeling of function.

A Level 0 DFD also called as fundamental system model or a context

model, represents the entire software element as a single bubble with input and
output data indicated by incoming and outgoing arrows respectively. Additional
processes and information flow paths are represented as the level 0 is partitioned
to reveal details. Each of the proves represents at level 1 is sub function of the
overall system depicted in the context model. Each of the process may be refined
are layered to depict more detail. Information continuity must be maintained in
every layer, that is input and output to each refinement must remain the same.

Explanation of main symbols which are used in data flow diagram is given below:

36
Hotel Management

1)

 This shape is used in data flow diagram for

represent a particular process.

2)

 This shape is used in data flow diagram for

represent a particular database.

3)

 This shape is used in data flow diagram for

represent a input/output process.

4)

 This arrow shape is used in data flow

diagram for represent a flow of data.

 Context Diagram :-

37
Hotel Management

 First leval Client Module Data Flow Diagram:-

38
Hotel Management

 Registration Process:-

39
Hotel Management

 Login Process:-

40
Hotel Management

 Second Leval Admin Module Data Flow Diagram:-

41
Hotel Management

E-R DIAGRAM

42
Hotel Management

Diagrams are one of the better ways to communicate different of a

components of a system. They are also too easy to understand by everyone. They
offer an overview of the entire system. An E-R diagram is known as Entity
relationship diagram. An E-R diagram is graphical method of representing entity
classes, attributes and relationships.

An ERD is a model that identifies the concepts or entities that exist in a

system and the relationships between those entities. An ERD is often used as a
way to visualize a relational database: each entity represents a database table, and
the relationship lines represent the keys in one table that point to specific records
in related tables. ERDs may also be more abstract, not necessarily capturing every
table needed within a database, but serving to diagram the major concepts and
relationships. This ERD is of the latter type, intended to present an abstract,
theoretical view of the major entities and relationships needed for management of
electronic resources. It may assist the database design process for an e-resource
management system, but does not identify every table that would be necessary for
an electronic resource management database.

An E-R diagram uses six basic symbols:

1) A rectangle to denote an entity or entity set.

2) A diamond to denote a relationship between two entities.

3) An oval to denote attributes.

4) A '1' to denote a single occurrence.

5) An 'M' to denote multiple occurrences.

6) A line which links attributes to an entity or entity set and entity sets to
relationships.

When an E-R diagram is built. The first step is defining entities. The next
step is to define the relationship between the entities. The final step to identify the
attributes that belong to each entity. Once the E-R diagram is completed. The
entities will become the files (or table).

There are three types of relation.

43
Hotel Management

1) One to One Relationship (1:1).

2) One to Many Relationship (1:M).
3) Many to Many Relationship (M:M).

This entity-relationship diagram depicts the major concepts and

relationships needed for managing electronic resources. It is neither a complete
data model depicting every necessary relational database table, nor is it meant to
be a proscriptive design for implementations of electronic resource management
systems. Alternate models may capture the necessary attributes and relationships.

E-R Diagram of our project is drawn below.

 Customer Purchase the Products (One to Many):-

44
Hotel Management

 Many Products add to Shopping cart (Many to Many):-

 User gives the Feedback (One to One):-

45
Hotel Management

 User gives the Review on product (One to One):-

46
Hotel Management

 Customer Purchase the Products (One to Many):-

47
Hotel Management

 Many Products add to Shopping cart (Many to Many):-

48
Hotel Management

 User gives the Feedback (One to One):-

49
Hotel Management

 User gives the Review on product (One to One):-

50
Hotel Management

5. SYSTEM DESIGN

51
Hotel Management

5.1 DATABASE DESIGN / DATA STRUCTURE DESIGN

5.1.1 Tables and Relationship

 In my Project Online Hotel Management I used VISUAL STUDIO 2008 as a

front end and use SQL server 2005 as a backend.

 Front end is mainly used for the designing purpose or designing the various kinds
of forms and implement the logic. and the backend is mainly used for them to
store the data, records, or the information.

 I make all the tables in the SQL Server 2005. My table names are Hotel Rooms,
Hotel Info., etc. are the tables I make to store the records, data, information in the
back end means in the SQL Server 2005.

 So , these tables are make in SQL Server 2005 and these tables are directly
connected to the front end so , when user or the candidate fill up the job
application forms so the records or the data or the information of the candidate
stored in the tables means in the back end.

 These all the tables are store the records, and administrator are able to watch all
the data . this is a very beneficial for the organization as well as for the candidate,
because the candidate fill up the data that’s store in the back end means in the
tables so, admin can easily show the data and if admin fills that the candidate is

52
Hotel Management

appropriate for the vacant or for the empty jobs admin can call up that person for
the interview.

 Now we talk about the tables and how this tables work in a back end that we can
know but the main thing is the relationship of the tables.

 That’s the most important thing for the back end. in my project there is a
relationship between the tables means all the tables are connected with each other
so all the records or the data or the information can easily stored and there is a no
chance of the mistakes in the tables.

 The Relationship between the tables is also considered as a security part if the
records are not stored properly so candidate can not able to work further so it can
avoid the chance of the dummy records.

5.2 INPUT OUTPUT AND INTERFACE DESIGN

Input
Input of the system is the Login name and then User can search different Hotels. The
admin can controls all details of Hotels and its services. When Admin is logged in, He
can search different details of other users & other information. In addition to this he
can email to other users to their Email Id.

Output
Output of the system is Search Results for Different Details like Feedback, other
information & Email posted by administrator. User can upload details of files. User
can also edit Resume and that save back to the server

53
Hotel Management

Interface Design
The Interface of the system is fully GUI based. Here I am showing the some pages of
the system. This makes the user very comfortable to use the system.

5.2.1 Access Control and Security

An interface is the common boundary between the user and the computer system
application – the point where the computer and the individual interact.

Purpose of Interface
The systems analyst’s objective is to design an interface that will accomplish the
following purposes:
 Tell the system what action to take.
 Facilitate use of the system.
Allow user to accomplish processing actions or activities efficiently and
effectively, and in manner they perceive as being a natural and reasonable way to
request and carry out activities; include the user of methods that will not grow
tiresome or unacceptable to frequent users who become familiar with the system
but that will facilitate equally effective use by novice users.
 Avoid user errors.
Prevent the taking of any action that will create a processing error or interrupt the
expected actions of the computer system.

 Receiving of Messages
An important part of the interface is the communication of messages between
system and user. Individuals want to know when to initiate or take actions, the
status of certain events and activities, and when a task is completed.

54
Hotel Management

6. IMPLEMENTATION
PLANNING AND DETAILS

55
Hotel Management

6.1 SECURITY FEATURE

 Online Hotel Management is developed in ASP.NET (.NET Framework 3.5) and

the backend is SQL Server 2005 database which provides maximum security.
Security is a key feature of SQL Server 2005, which provides confidentiality,
integrity, and availability of mission-critical data.

 User authentication feature in Online Hotel Management provides authentication

so that any unauthorized user can not use this application.

6.2 CODING STANDARDS

 Code conventions are important to programmers for a number of reasons:

 60% of the lifetime cost of a piece of software goes to maintenance
 Hardly any software is maintained for its whole life cycle by original author.
 Code convention improves the readability of the software, allowing engineers to
understand new code more quickly and thoroughly.
 If you ship your source code as product, you need to make sure it is as well
packaged and clean as any other product you create.

56
Hotel Management

7. TESTING

57
Hotel Management

Software Testing is the process used to access the quality of computer software.
Software testing is an empirical technical investigation conducted to provide stakeholders
with information about the quality of the product or service under test, with respect to the
context in which it is intended to operate. This includes, but is not limited to, the process
of executing a program or application with the intent of finding software bugs. Quality is
not an absolute; it is value to some person. With than in mind, testing can never
completely establish the correctness of arbitrary computer software; testing furnishes a
criticism or comparison that compares the state and behavior of the product against a
specification. An important point is that software testing should be distinguished from
separate discipline of Software Quality Assurance, which encompasses all business
process areas, not just testing.

A software system must be tested before thoroughly before implementation so that

maximum number of errors is uncovered before implementation begins. There are many
techniques and methods of testing software some focusing on the procedural design and
others on the fundamental requirements.

7.1 TESTING PLAN

The test plan identifies a testing task set, the work products to be developed, and the way
in which results are to be evaluated, recorded, and reused. A Intranet Application Test
Plan identifies:

 A task set to be applied as testing commences,

 The work product to be produced as each testing task is executed, and
 The manner, in which the results of testing are evaluated, recorded and reused
when regression testing is conducted.

58
Hotel Management

7.2 TESTING STRATEGY

Figure 7.1 Test Plan

7.2.1 Software Testing

Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design, and coding. Testing represents an interesting
anomaly for the software. The testing phase involves testing of the system using various
test data. Preparation of test data plays a vital role in system testing. After preparing the
test data, the system under study is tested using those test data. Errors found were
corrected and corrections were recorded for future references. Thus, a series of testing is
performed on the system before it is ready for implementation.

The development of the software systems involves a series of production activities where
opportunities for injection of human fallibility are enormous. Errors may begin to occur
at very inception of the process where the objectives may be erroneously or imperfectly
specified as well as in later design and development stages. Because of human inability to

59
 Hotel Management

perform and communicate with perfection, software development is followed by a quality

assurance activity.
There are two general strategies for testing software the strategies of code testing and
specification testing.

 Code Testing

The code-testing strategy examines the logic of the program. Test cases are developed

that are used to execute every instruction in the program or module; that is, every path

through the program is tested. A path is specific combination of conditions that is handled

by the program.

 Specification Testing

In specification testing analyst examines specifications stating what the program should
do and how it should perform under various conditions. Test cases are developed for each
condition or combination of conditions and submitted for processing. By examining the
result, the analyst can determine whether the program performs according to its specified
requirements.

This strategy treats the program as if it were a black box: the analyst does not look into
the program to study the code and is not concerned about whether every instruction or
path through the program is tested.

60
Hotel Management

7.3 TESTING METHODS

Black Box Testing

Black box testing treats the software as a "black box," without any knowledge of internal
implementation. Specification-based testing aims to test the functionality of software
according to the applicable requirements. Thus, the tester inputs data into, and only sees
the output from, the test object. This level of testing usually requires thorough test cases
to be provided to the tester, who then can simply verify that for a given input, the output
value, either "is" or "is not" the same as the expected value specified in the test case.

White Box Testing

White box testing is when the tester has access to the internal data structures and
algorithms. White box testing includes creating tests to satisfy some criteria of
code coverage. For example, the test designer can create tests to cause all
statements in the program to be executed at least once.
White box testing methods can also be used to evaluate the completeness of a test suite
that was created with black box testing methods. This allows the software team to
examine parts of a system that are rarely tested and ensures that the most important
function points have been tested. Two common forms of code coverage are function
coverage, which reports on function executed and statement coverage which reports on
the umber of lines executed to complete the test. They both return coverage metric,
measured as a percentage.

Following are the list of tests that were conducted:

Unit Testing
 Unit testing tests the minimal software component, or module. Each unit (basic
component) of the software is tested to verify that the detailed design for the unit has
been correctly implemented.

61
Hotel Management

 In this testing we had test the programs making up a system. For this reason it is also
called program testing. The Test Configuration module consists of sub modules like
adding of a form, removing of a form, etc.

 The test cases needed for unit testing should exercise each condition and option.
While adding manual question to each test subject, it should be checked with total
number of question with that difficulty level specified in the Test Configuration.
 Unit testing can be performed from the bottom up, starting with the smallest and
lowest-level modules and proceeding one at a time or it can be performed from top
down which begins with upper level module.

Integration Testing

 Integration testing is the phase of software testing in which individual software

modules are combined and tested as a group. It follows unit testing and precedes
system testing.
 Integration testing takes as its input modules that have been unit tested, groups them
in larger aggregates, applies tests defined in an integration test plan to those
aggregates, and delivers as its output the integrated system ready for system testing.
 The purpose of integration testing is to verify functional, performance and reliability
requirements placed on major design items. Test cases are constructed to test that all
components within assemblages interact correctly, for example across procedure calls
or process activations, and this is done after testing individual modules, i.e. unit
testing.

System Testing
 This testing strategy tests the integration of each module in the system. It also tests to
find discrepancies between the system and its original objective, current specification
and systems documentation.
 The preliminary concern is the compatibility of individual modules.

62
Hotel Management

7.4 TEST CASES

7.4.1 Purpose
The purpose of the test cases is to test the various input and to see whether the output
produce any errors or not. There are different test cases according to the system. It is
tested with different types of value like single value, multiple value and se it can generate
expected output.

63
Hotel Management

8. SCREENSHOTS AND USER

MANUAL

64
Hotel Management

Home Page

In the above page how we can see this is the home page of this site so we can start
from here and it also provides the whole information about the site map.

65
Hotel Management

Hotel’s Pose Page

This is the all hotel page so we get all informtion about all the hotels and this page
contains the all hotels photo so we can directly goto any hotels description by just clicking
on the any hotels photo so that means this page makes verry easy services and this page
helps to make work easier and faster

66
Hotel Management

Send Query Page

This page allows you to send any type of request to the hotel so and also you
can send any suggestion to hotel so next time any hotel owner can emprove its services so
next time you get more comfort services

67
Hotel Management

Hotel Description

This page gives you all the description about the hotel or all the hotel so you
can get totally information about the hotels and also about this site also

And also this page provides the descriptive description about the all the
hotel and you can see the all available facilities of hotels so you can easily chose the hotel
from the wide list of hotels

68
Hotel Management

Services

69
Hotel Management

70
Hotel Management

9. CONCLUSION
AND DISCUSSION

9.1 CONCLUSION

This web application provides easy way to manage document online. This application
developed is designed in such a way that any further enhancements can be done with
ease.

71
Hotel Management

This application is going to be used for our college to easily manage document at remote
place. So, we are very happy to develop this web application as it provides all the
requirements of our college.

72