Minakshi

HOTEL
MANAGEMENT
SYSTEM
BCA- 0900318 IIHST2019BCA318 Page 1

CERTFICATE
This is to certify the project work entitled “ HOTEL
MANEGEMENT SYSTEM” submitted to “ P. D. Mahila Degree
College( C. S. J.M. University ,Kanpur) in partial requirement
for the summer training.
The matter embodied in this project is authentic and is
genuine work done by the student and has not been
submitted whether to this University or to any other
University / institute for the fulfillment of requirement of any
course of study.
Date-
Signature
Mr. SUPARV PRADHAN

(Head of department)

ACKNOWLEDGEMENT
No project can be successful without the valuable suggestion of teachers

and help of classmates &friends. Specially thanks to Sayjal & Geeta without
help them I am unable to complete my project Hotel Management System.
My project is no different in this aspect. I am greatly indebted to my teacher
and several of my
classmates & friends who indirectly helped me in this endeavors of mine. I

would like to thank all of my friends because without of their support it was
not possible.
We would like to thanks whole teaching staff of Hi-tech Academy, who

have contributed greatly to the success of this project. First of all, we would
like to express our sincere thanks to Ajay Sharma Sir & Akash Sir.
My honorable project guide, I am especially indebted to. I am also

thankful to my teacher Mr. Suparv Pradhan Sir ( H O D ) Computer Deptt
who have also helped me in my project . It was only because of their
encouraging nature that I was able to successfully complete project.
Km Minakshi
BCA Vth Sem

Introduction
Hotel Management system operates a global online hotel reservation system
for business and leisure travelers. To compete with the international e-
marketplace, a great deal of attention should pay towards the optimization of
user requirement to generate recommended hotel alternative.
1. Hotel management system gives us feasibilities for pre – reserved

benefits when be travelling outside, we can reserve hotel by this project
at our home.
2. Developed an intelligent e –marketplace for the tourism based on fuzzy
to serve the customer who wants to travel but has no idea about the
accommodation.
3. customer can book the rooms through phone or directly coming to hotel
for future. cancellation option use to cancel the booked room after the
customer confirmation to cancel the booked rooms.
4. The details of the hotel management system including the tourism

place, religious place, fooding place , health spas, according control etc.
are well described in my project.
5. During the room booking and check-in the room available screen show
the status of the room whether rooms are booked or vacant or out of
order. Using the screen we can check the available of the room of the
particular date.

OBJECTIVE
During the past several decades personal function has been
transformed from a relatively obscure record keeping staff to central
and top level management function .there are many factors that have
influenced this transformation like technological advance,
professionalism, and general recognition of human begins as most
important resources.
 A computer based management system is designed to handle all

the primary information required to calculate monthly
statements. Separate database is maintained to handle all the
details required for the statement calculation and generation.
 This project intends to introduce more user friendliness in the
various activities such as record updating, maintenance and
searching .
 The searching of record has been made quite simple as all the
details of the customer can be obtained by simple keying in the
identification of that customer.
 Similarly, record maintenance and updating can also be
accomplished by using the identification of the customer with
all the details being automatically generated. These details are
also being updated in the master file thus keeping record
absolutely up-to-date.
 The entire information has maintained in the database or files
and retrived the necessary information which can be entire
activity is to automate the process of day to day activities of
hotel like:-
1) Room activities.
2) Admission of a new customer
3) Assign a room according to customer demand
4) Checkout of a computer and releasing the room
5) Finally compute the bill etc.
6) Package available
7) Advance online booking
8) Online cancellation.
9) List of regular customer
10)email facility
11)feedbacks
This project have some more features:
 System connectivity
 No data duplication
 No paper work required
 Time efficient
 Cost efficient
 Automatic data validation
 User friendly environment
 Fast data insertion and retrieval
 Easy performance check

ABSTRACT
A HOTEL MANAGEMENT is very useful software for managing the hotel
online.
In today’s world online booking is very wide trend. With the help of this
software you can book online room as yours required.
This is software which has mainly made for management of a Hotel. The
software has been designed with front-end as asp.net and backend as C#. The
project hotel management manages and maintains the record of customers and
rooms of the hotel.
Customer can book the room through this software. The rooms have different
categories such as A.C., non-A.C. etc. So There charges and records will be
maintained by this software. This software made in a user friendly interface so
everyone can understand and use easily.
Through this project administration can manage their programs in effectively
way.

PROJECT ANALYSILS
Analysis is an important part of any project. If Analysis is not done properly
then the whole project moves in the wrong direction. It also provides a
schedule for the proper project work.
Analysis task divided into 3 areas :
Problem Recognition
Feasibility Study
Requirement Analysis
Problem Recognition:
It is the phase in which the Current need for the System is to be defined. This
site of Computer Peripherals & Consumables has all the up to date
information.
Feasibility Study
Feasibility study is a test of a system to its work ability, ability to meet user
needs and effective use of resources. In this section we consider the economic,
technical and behavioral factors as per the proposed system
Economic Feasibility:-.
In this section we determine the cost analysis. How our system can effected to
the user, how it can be helpful for organization. By this we increase the overall
speed of software installation & maintenance cost is very low. Our proposed
system can on normal computer system configuration. We can use further
according to the needs; this feature saves the human resources and their
efforts.
Technical feasibility :-
In this section we consider on the technical efforts of the proposed system. By

this, we mean whether the technology needs is available and if available
whether it is reusable. Yes our system can adjust according to the organization
need; it will be proper run if technology will change. Our proposed system can
easily run on above minimum configuration –
Software requirements Hardware requirements

Operating system; windows Processor; any
or Linux or MAC
User interface; HTML,CSS Hard disk ;10 GB minimum
Programming language; c# RAM; 256 mb or more
Database, MYSQL Any screen
Behaviors feasibility ;-
As we know that behavioural feasibility is related to human or personal related

in an organization in this section we analysis the how our proposed system
impact on to the organization. There are some points to arise during the
behavioural study –
 User friendly system;-.
Our project will be fully GUI application . user can easily understand the
meaning of particular tools. User required just setting the properties
according to need.
 Reusable ;-
It is reusable for every user. They can implement & set the property according
to own choice.
 Interaction between new system and exiting system;-
Interaction between new system and exiting will be very easy a demo will
be needed for existing users.

SDLC
To understand system development, we need to recognize that candidate
system has a life cycle, just like a living system or a new product. System has a
life cycle just like a living system or a new product.
System development has a life cycle has various activities. These activities are
highly interrelated . One must know what the problem is before it can be
solved.
A process consisting of the tow major steps of system analysis and design start
when management in or sometimes system development feel that a new
system or an improvement in the existing system is required.
Like many processes, the development of information system follows a like

cycle. Thus “SDLC’’ is classically thought of as a set of active ties that analyses
and implement on information system.
Project identification and selection –
This is the first phase in the SDLC. In this phase, someone identifies the need
for a new system or information needs. The organization information system
needs may result from request to deal with problem in current, from the desire
to problem in current , from the desire to problem perform addition task , or
information technology could be used to an existing .
When the request is mode, the first process that takes place dividing it
three
different parts. There are
 Request clarification
 Feasibility study
 Request approval

 Request clarification – Many request from employees and users in the
organization are not clearly defined.
 Feasibility study- An important outcome of request is feasible. There are

three in this study.
 Technical feasibility
 Economic feasibility
 Operation feasibility
 Request approval- It is not necessary that all requested are feasible. After a
project request is approval , its cost, priorities, completion time and
personal requirements used for initiation of development.
2 .Project planning
This is the second phase of SDLC. The two major activities in this phase are
the formal of the system problem and the presentation of reasons why the
system should or should not be developed by the organization.
The project leader and initial team of system analysis also produce a specific
plan, which the term will follow along with the SDLC steps. This baseline
project plan customizes the standardized SDLC and specifies the time and
resources needs for its execution.
The formal definition of a project is based on the likelihood that the

organization’s information system department is able to develop a system that
will solve the problem and determine whether the costs of developing the
system outweigh the benefits it could provide.

3. Requirement Analysis
Before the requirement analysis, one must know what the problem is before it
can be solved. The bases for a candidate system are recognition of a need for
improving an information system. After the definition of problem, an initial
investigation in conducted for various operations performed by a system and
their relationships within and outside the system. Depending on the results of
the initial investigation, the survey is expended to a more detailed feasibility
study. A feasibility study is a test of a system proposal according to its
workability, impact on the organization, ability to meet user needs and
effective use of resources. The objective of a feasibility study is not to solve the
problem but to acquire a sense of its scope.
 Statement of the problem

 Summary of finding and recommendations
 Details of finding
 Recommendations and conclusion
4.Design of system
The most creative and challenging phase of the system development life cycle
is system design. The term design describes a final logical system. Design phase
of software development deals with transforming the customer requirement
into a logical system. A good software design is seldom arrived through a
single step procedure but goes through series of steps. We can broadly classify
various design activities into two important parts-
 Preliminary design

Detailed design
A large number of software design techniques are available. Judging the

goodness of a design involves many subjective factors which depend on the
particular application.
5 .Coding
The input to the coding is the design document. During the coding phase,
different modules identified in the design document are coded according to
the module specification. After a module has been coded, code walk through
are carried out to ensure as possible during code inspection.
The following are some standards for coding:
 Name of the module

 Internal documentation of source code
 External documentation of source code
 Modification history
 Uniform appearance of the code
6. Software Testing
The testing of newly developed software, prior to its actual use, is commonly
followed practice.
It is the process of executing program with the intention of finding errors.

Testing a program consists of providing the program with a set of test inputs

and observing the behavior of program as per the use requirement. If the
program fails to behave as p- the user requirement, then the conditions under
which a failure occurs are noted for correction.
7. Implementation
The implementation phase is less creative than system design. It is primarily

concerned with user training, site preparation and file conversion.
when the candidate system is linked to terminals or remote sites, the

telecommunication network and tests of the network along with the system
are also included under implementation.
There are three types of implementation.
 Implementation of a computer system to replace a manual system.

 Implementation of a new computer system to replace an existing
one.
 Implementation of a modified application(software) to replace an
existing one using the same computer.
8.Maintenance
Software maintenance follows conversion to the extent that changes are

necessary to maintain satisfactory operation relative to changes in the user’s
environment or corrections to problems that surface late in the system’s
operation.

Maintenance is the enigma of system development. It holds the software
industry captive, tying up programming resources. There are a number of
problems with maintenance ,
e.g.
 Maintenance is not as rewarding as developing system.

 There are minimal standards for maintenance
 Few tools techniques are available for maintenance
 * A good test plan is tacking
 Procedures and guidelines are poorly defined.
 Maintenance is viewed as a necessary evil often delegated to junior
programmers.

Architectural framework of Hotel Management system
1.Database-
The database is a fundamental part of the system. It is also called as

the working storage and it works hand in hand with both the knowledge
base and the inference engine as a means of storing data. It stores all
important and detailed information of the HMS and that of the
administrator. Besides, it stores the detail set of prerecorded messages
dropped by user, which are suitable for different guidance cases. In
addition, the database server has both temporal validity and precise
timing constrains which allows it to store the most recent data and effect
instant changes as soon as they occur.
2. Web server-
This is the gateway application that enables you and your applications to
send/receive internet messages through internet devices to your
computer. It has an easy to use user interface, and an excellent internal
architecture. The designed system is a web based application, therefore,
there is a need to put up a web server. The web server used in the
research work is internet information services IIS.
3. Network signal-
This layer is an intermediate layer between the designed framework and
the online client who is accessing the application from his own personal
network LAN or the wide area network (WAN).
4.Users of the designed system- the user of the designed system can
access the HMS with either their personal computers or their phones.

Database design of online computerized hotel management system
This helps to manage or structure their data in a logical

way. In addition, database design is a process to produce detailed data
model of a database. The detailed data model consists of detailed value
parameters, attributes, primary key, foreign key and relationship
between entities. The designing of the database needs an excellent
developer’s understanding of two criteria which are the domain area and
database development. Effective database designed can assist developer
to perform well from the beginning .in addition, it can reduce costs and
time during development process. An excellent database development is
important to get an optimal performance and high productivity. In order
to achieve the quality to system
Conceptual modeling of online computerized hotel management

system
The emphasis of logical database model is on logic,

which is a readable method and useful for representing the knowledge.
This can be done through the conceptual modeling conceptual modeling
is process to model data of domain, conceptual modeling is a well –know
technique of data modeling. It represents domain entities meaning of the
data, concepts or terms used by domain experts, function or relationship
between concepts.

USER INTERFACE(UI) OF ONLINE HOTEL MANAGEMENT
SYSTEM:
The user interface is very important part of the system. This helps every
member of the system to interact with each detail properly. As we have
shown several use cases in this system.
We have developed these interfaces to interact with the system.
Login Page:
Owner or Manager need to log in using login id and password.
Customer Page:
Can view their details as well as Booking details.
Receptionist Page:
He can Offline Book the available room at the hotel.
Payment Page:
This interface helps in paying the money via several modes.
There are mainly Seven Entities Owner, Manager, Employee, client, hotel,
Payment, book. These five entities would manage the whole
system. There are mainly Seven Entities Owner, Manager, Employee,
client, hotel, Payment, book.
These five entities would manage the whole system.
Owner:
The owner is a super user of the system. The owner is just like admin. The
owner has all right to view and modify the data in the system. The owner
has followings attributes.
Owner ID:

This is numeric 14 digits number which is unique to every admin.
OwnerID is the primary key to admin table in the database.
Name:
This attribute would hold the name of the owner. The name is varchar
type variable which holds the data length up to 250 characters.
Email:
This is an essential attribute of the table. Every owner must have a
working email id to keep in contact with employees. This field has
validation only email formatted values will be stored.
Contact.:
This is multi valued attributes which mean every owner can have more
the one mobile number in database.
Address:
This attribute would hold the address of the owner. Each employee must
provide the address.
Manager:
The manager is a secondary user of the system. The manager can view
hotel details, manage employee, booking, solve client’s problem. The
manager has followings attributes.
ManagerID:
This is numeric 14 digits number which is unique to every Manager.
ManagerID is the primary key to Manager table in the database.
Name:
This attribute would hold the name of the manager. The name is varchar
Email:

This is an essential attribute of the table. Every Manager must have a
Contact.:
This is multi valued attributes which mean every manager can have more
Address:
This attribute would hold the address of admin. Each employee must
provide the address. Admin address is verified via Human resource team.
Employee:
The employee is another user of the system. An employee can view hotel
details, verify the online booking room availability for clients. The
employee has followings attributes.
EmpID:
This is numeric 14 digits number which is unique to every Employee.
EmpID is the primary key to Employee table in the database.
Name:
This attribute would hold the name of Employee. The name is varchar
Email:
This is an essential attribute of the table. Every employee must have a
Contact.:
This is multi valued attributes which mean every employee can have more
Address:
This attribute would hold the address of the employee. Each employee
must provide the address.
Client:
The client is the basic end user of our system most of the business is done
through them. Clients would book the desired hotel room. The client
would provide the feedback. The client has following attributes.
ClientID:
This is numeric 14 digits number which is unique to every Client. ClientID
is the primary key to client table in the database.
Name:
This attribute would hold the name of clients. The name is varchar type
variable which holds the data length up to 50 characters.
Email.:
This is an essential attribute of the table. Every client must have a
working email id. This field has validation only email formatted values
will be stored.
Address:
This attribute would hold the address of clients. Address of clients would
help us to connect with them and visit the location. This would provide
better services.
Hotel:
Every hotel registered with the system has the information in this entity.
Hotel is the main concern of system.
HotelID:

This is numeric 14 digits number which is unique to every Hotel. HotelID
is the primary key to case table in the database. Each hotel is uniquely
identified using this id.
Name:
For customer point of view, every hotel does have its name. The name is
very important.
No Of Rooms:
Every hotel has many rooms. To make it easy for the customer. And check
availability no. of rooms should be in the database.
Address:
This attribute would hold the address of the hotel. Address of Hotel
would help the client to find it easy and visit the location. This would
provide better services.
Book:
Before going to book any room. The client should check the availability. If
the desired room is available. They can book it.
BookID:
This is numeric 14 digits number which is unique to every Booking.
BookID is the primary key to case table in the database. Each Payment is
uniquely identified using this id.
RoomNO:
With reference to hotel booking must have room no.
Date:
This would hold the date of the transaction.
Payment:

Payment Entity store the data about payment. Every payment data is
here. Any conflict can be resolved by looking to this.
Payment ID:
This is numeric 14 digits number which is unique to every Payment.
PaymentID is the primary key to payment table in the database. Each
Payment is uniquely identified using this id.
BookingID:
This is a reference to a booking. This would help the admin to find this
payment is against booking.
Date:
This would hold the date of the transaction.
Transaction No.:
The transaction number is reference no given by the bank.
Status:
Status of every transaction either it would be pending or confirm is being
updated in this field.

DESIGN DATA DICTIONARY FOR ER-DIAGRAM OF
ONLINE HOTEL MANAGEMENT SYSTEM:
The data dictionary is useful in case of development.
Table Name: OwnerMaster

Primary Key: OwnerID
Description: To store the details of admin
Serial No. Fields Datatype Description
1. OwnerID Integer Primary key
2. Name Varchar
3. EmailID Varchar
Multiple contacts can exist
4. Contact. Integer for single admin
5.
Address Varchar
Table Name: ManagerMaster
Primary Key: ManagerID
Description: To store the details of General Manager
Serial
No. Fields Datatype Description
1. ManagerID Integer Primary key
2. Name varchar
3. Email varchar
Multiple contacts can
4. Contact. Integer exist for single admin
5. Address varchar

Table Name: EmployeeMaster
Primary Key: EmployeeID
Description: To store the details of Employee Details
Serial
1. EmployeeID Integer Primary key
2. Name varchar
3. Email varchar

4. Contact. Integer for single admin
5. Address varchar
Table Name: ClientMaster

Primary Key: ClientID
Description: To store the details of Clients
Serial
1. ClientID Integer Primary key
2. Name Varchar

3. Email Varchar for single client
4. Address Varchar

Table Name: HotelMaster
Primary Key: HotelID
Description: To store the details of Property
Serial
1. HotelID Integer Primary key

2. Hotel Name Varchar
3. Address Varchar
Number of
4. rooms Integer
Table Name: BookMaster

Primary Key: BookID
Description: To store the details of Payment
Serial
1. BookID Integer Primary key
2. Room No. Integer
3. Date Date

Table Name: PaymentMaster
Primary Key: PaymentID

Description: To store the details of Payment
Serial
1. PaymentID Integer Primary key
2. BookID Integer Foreign key to BookMaster
3. Date Date
Transaction
4. No. Varchar
5. Status Varchar

SYSTEM DESIGN
System design goes through two phases of development : logical design and
physical design. Logical design defines the boundaries of the system. It
describes the inputs, outputs, databases, and procedures that meet the users
requirements. Following logical design is physical design that produces the
working system by defining the design specification. Thus it aims at providing
the best possible easy ways so that a person with minimum knowledge of
operating system (window) can operate the same with out any hassle. As a
general user one needs to have the following satisfaction in the software or in
the development system.
The phase of system design comes after the analysis. It is to schedule or plan a
new system i.e. the analyst plans the input and output of the new system, its
logic and physical devices to receive data generate information and store the
result. In this phase, it is specified how to meet requirement of the user as
pointed out during the system analysis phase. Since system design involves all
the aspects of the system, it is needed a very exhaustive design for all kind of
the system. Consequently, the designing needs to be done module wise. When
the design involves the inputs, output, files and procedures used to achieve the
objective of the system, it is called the logical design. When the design involves
the actual implementation of the system programs to actual implementation of
the system programs to accomplish the task, it is called the physical design.
System design is divided into three heads-
(a) input design
(b) output design

Input design
It consists of data preparation, data capture and data entry. Care is taken to
minimize the data to be captured. No redundant data is to be captured. The
layout of the input document should be such that it is easily understandable by
the operator.
Output design
The objective of the output design is to produce timely, accurate and relevant
information in a user understandable manner. It is the most direct method of
communicating the result of the system to the user.
User interface design
User interface design creates an effective communication medium between a

human and a computer, following a set of interface design principles, design
identifies interface objects, actions and then creates a screen layout that forms
the basis for a user interface prototypes. User interface design is very important
because if the software is difficult to use, if it forces the user into mistakes, or if
frustrates users efforts to accomplish users goals user would not like to use it,
regardless of the computational power it exhibits or the functionality it offers
because it molds a users perception of the software, the interface has to be
right.
We have also designed some forms for the interaction of the user with the
system these forms are shone on the following pages with small description
and coding of each form.

MODULES
 Login module
 Home module
 Front office module
 Banquet module
 House- keeping module
LOGIN MODULE
1. login
2. new user
3. change password
a) LOGIN- registered users can login into the application by using
their username and password.
b) NEW USER- user can create new user by giving the details.
i.e. name, permission, password etc
(c) CHANGE PASSWORD- registered users can change their
password(permission granted only for admin)
HOME MODULE
 Rooms layout
FRONT OFFICE MODULE
a) Masters
b) Transactions
c) Reports

1.MASTERS
 Hotel profile
 Tax master
 Charges master
 Room type master
 Rooms master
 Floor master
 Country
 State
 City
 Proof type
HOTEL PROFILE
This is to enter the details of our hotel (i.e.hotel name address, phone
no,email,etc)
Tax master- this is to enter the tax details of our hotel (i.e. tax name,
percentage)
Charges master- this is to enter the charges details of our hotel(i.e. charge
type and amount
Room type master- this is to enter the room type details of our hotel.
Room s master- this is to enter the rooms details of our hotel
Floor master-this is to enter the floor details of our hotel
Country- this is to enter the country names

States- this is to enter the states
City- this is to enter the city details.
Proof type- this is to enter the proof type details of customers.
2. transaction-
 Booking
 Check-in
 Check-out
 Availability
 Night audit
Booking
This is to enter the personal information, check-in information, and
billing information details of our customers. Customers can book the
rooms through phone or directly coming to hotel for future. Cancellation
option used to cancel the booked rooms after the customer confirmation
to cancel the booked rooms.
Check-in
Check-in details will be entered while the customers arrival to the hotel.
Customer invoice will be generated when the customer check-in to hotel.

Check out
This is to enter the check-out details of customer while they check-out
from the hotel. There are two option to check-out they are, full and
partial check-out. Partial checkout is while customer want to check out
rooms partially from the multiple number of rooms. Check-out bill will
be generated during the customer check-out.
Room availability-
During the room booking and check-in the room availability screen
shows the status of the rooms whether rooms are booked or vacant or
out of order using this screen we can check the availability of the rooms
on the particular data range
3.Report
Master report
 Hotel profile report
 Transaction reports
 Reservation report
 Customer room stay view report
House keeping
a) Masters
b) Transaction
c) Reports
 Master –
 House keeping status
 Stock entry
Stock entry-this is to enter the stock details of the house keeping things. By
using this we are well informed number of stocks availability and make
purchase for future needs.
2. Transactions-
 Stock issuep
 Room servicing
 Room servicing history
 Complaints
Stock issue- this is to issue the stocks to housekeeping employees whenever

they need for housekeeping and all other needs.
Room servicing- this is to assign the work and rooms to employees to clean or
service the rooms
Room servicing history- by using the particular date range we can check the
complete history of the house keeping words by employees.
Complaints- this is to manage the complaints given by the customers about

the problems or services in their staying rooms, after solving their complaints
complaint status will be updated.

DATA FLOW DIAGRAM
Data flow design is concerned with designing a sequence of
functional transformation that converts system imports into the
required outputs. The design is represented as data flow diagram
illustrated how data flows through a system and how the output is
derived from the input through a sequence of functional
transformations.
Data flow diagrams are useful and intuitive way to describing a
system. They are normally understandable without special training,
especially if control information is excluded. They show end-to-end
processing. That is the flow of processing from when data enters the
system to where it leaves the application can be traced.
ADMIN

Data Flow Diagram

Relationship diagram for hotel management
system..

E-R DIAGRAMS-
ADMIN TABLE-

HOTEL APPLICATION

ZERO LEVEL DFD – HOTEL MANAGEMENT
SYSTEM

Process of Hotel :
start
Car application
RFID reader is triggered by sensor pluse
To work
Detecting tag
Yes
Reading the tag data and send information to

the computer host
The computer host check

the validity
no yes
Customized triggered to guide the next tap Lane controller is rising and let the car passing

E-R diagram
Customer
First name
address id
surname
Creditcar dno
guests
postcode
Telephon eno
eenono eno
reques book
t
rooms reservation
reserved
Price/night
Satalite tv
fullmeal
checkout
Payment Creditcar
internet
Room type method dno
Room no Booking id

Flow Chart :

PROJECT RISK
Risk analysis and management are a series of steps that help a software team to
understand and manage uncertainty.
Many problems can infect a software project.
A risk is a potential problem -- it might happen, it might not.
But, regardless of the outcome, it's a really good idea to identify it, assess its
probability of occurrence, and estimate its impact.
Risk management aims at dealing with all kinds of risks that might affect a
project.
Type of risk
Risk identification is a systematic attempt to specify threats to the project plan.
By identifying known and predictable risks the project manager takes step
toward avoiding them when possible and controlling them when necessary.
One method for identifying risks is to create a risk item checklist.
The checklist can be used for risks identification and focuses on some
subset of known and predictable risks in the following generic subcategories:
Product size - risks associated with the overall size of the software to be
built or modified.

Business impact - risks associated with constraints imposed by management
or the marketplace.
Customer characteristics -risks associated with the constraints of the

customer and the developer’s ability to communicate with the customer in a
timely manner.
Process definition -risks associated with the degree to which the software
process has been define and is following by the development organization.
Development environment -risks associated with the availability and quality

of the tools to be used to build the product.
Technology to be built -risks associated with the complexity of the system

to be built and the "newness" of the technology that is packaged by the
system.
Staff size and experience -risks associated with the overall technical and
project experience of the software engineers who do the work.
Product size - risks associated with the overall size of the software to be
built or modified.
Business impact - risks associated with constraints imposed by management

or the marketplace.
Customer characteristics -risks associated with the constraints of the

customer and the developer’s ability to communicate with the customer in a
timely manner.
Process definition -risks associated with the degree to which the software
process has been define and is following by the development organization.

Development environment -risks associated with the availability and quality
of the tools to be used to build the product.
Technology to be built -risks associated with the complexity of the system

to be built and the "newness" of the technology that is packaged by the
system.
Staff size and experience -risks associated with the overall technical and
project experience of the software engineers who do the work.

Activity Chart
Activity diagram is another important diagram in UML to described dynamic
aspects of the system . Activity diagram is basically a flow chart to represent
the flow from one activity to another activity.The activity can be described as
an operation of the system.
So the control flow is drawn from one operation to another. This flow can be
sequential, branched or concurrent. Activity diagrams deals with all types of
flow control by using different element like fork, join etc.
 Project start
 Planning of project
 Detail study of project
 Designing of system
 Detail description of system
 Module design
 System flow
 Data base design
 Implementation in document
 Final presentation

Diagram of Activity Chart

E-R Diagram Relationship
An entity – relationship model (ER model) describes inter related things of
interest in a specific domain of knowledge. An ER model is composed of entity
types (which classify the things of interest) and specifies relationship that can
exist between instances of those entity types.
In software engineering an ER model is commonly formed to represent things

that a business needs to remember in order to perform business process.
Consequently, the ER model becomes an abstract data model that defines a
data information structure that can be implemented in a database, typically a
relational database.
Entities may be characterized not only by relationships, but also by additional

properties (attributes), which include identifies called “ Primary keys”.
Diagrams created to represent attributes as well as entities and relationship
may be called entity- attribute- relationship diagrams, rather than entity –
relationship models.
An ER model is typically implemented as a database. In a simple relational

database implementation, each row of a table represents one instance of an
entity type, and each field in a table represents an attribute type. In a relational
database a relational between entities is implemented by storing the primary
key of one entity as a pointer or “ Foreign key” in the table of another entity.
Entity
Primary key
Relationship set
Attribute set

Implement & Maintenance
This is the most important phase of the system Development Life Cycle, where
the actual implementation of the designed system occurs. Implementation is a
process that includes all those activities that take place to convert an old
system to a new system. There are three types of implementation:
 Implementation of computer system to replace a manual system: The

problem that re encountered are converting files, training users, creating
accurate files and verifying printouts for integrity.
 Implementation of new computer system to replace an existing one: This
is usually a difficult conversion If it is not planned properly the e can be
many problems. So large computer system have taken as long as a year to
convert.
 Implementation of modified application to replace an existing one using
the same computer: This type of conversion is relatively easy to handle
provided there are no major changes in the files.
Post Implementation Maintenance:
The maintenance phase is the last phase of the system development life
cycle. Yet a life cycle is circular in that the last activity leads back to the
first. This means that the process of maintaining an information system is
the process of returning to the change implemented.
Four major activities occur within maintenance:
 Obtaining maintenance request

 Transforming requests into changes
 Designing changes
 Implementing changes
Obtaining maintenance request require that a formal process be established

whereby user can submit system change requests. Most companies have some
sort of document to request new development, to report problems, analysis
must be conducted to gin an understanding of the scope of the request. It must
be determined how the request will affect the current system and duration of
such project. Next, a change request can be transformed into a formal design
change, which can then be fed into the maintenance implementation phase.
There are several type of maintenance that you can perform on an information
system. These are:
 Corrective Maintenance
 Adaptive Maintenance

Testing
Testing Objective : As we know GENERATOR is a plug- in to in design CS2
on windows and Macintosh. The layout to be created based on the selected
variations. While placing the images, they are divided into small, medium and
large image box categories. Different aspect is care of like alignment of image
boxes on the layout, page Margin, proper spacing between images, scaling of
images, Arrangement of images in different variations etc.
The testing objective of the GENERATOR is to verify application on

following aspects:
 Functional correctness of the application

 Usability aspects of the dialogs
 UI testing of the application
 Performance ( at the time of creating variation and layout )
Testing methodology :
The following Methodologies would be used to test Generator:
In this methodology different modules are tested against the specifications

produced during for the modules. Unit testing is essentially for the verification
of the code produced during the coding phase and its goal is to test the
internal logic of the modules. The programmer of the module typically does it.
Structural testing is best suited for this level.
User interface Testing : UI testing focuses on the appearance of the product

rather than its functional. The purpose of UI testing will be to validate all UI
elements included in the generator specification (as discussed with client ) the
overall look of the application should be appealing, consistent and user
friendly. All the UI element mentioned will be tested. Look and fell of the Mac
OS X and versions of the generator dialog should be there.
While Box Testing : In order to test loops, we used the loop testing
technique. Most of the loops used in this project belong to the category of

simple loops. We applied the following set of tests to test loops, where n is the
maximum number of allowable passes through the loop.
Skipped the loop entirely.
Allowed only one pass through the loop.
Allowed two passed through the loop
Allowed m passed through the loop where m< n.
Allowed n-1,n, n+1 passes through the loop.
Black Box Testing : when we know the specified function that a product has
designed to perform, tests can be conducted that demonstrate each function is
fully operational while at the same time searching for errors in each function.
A black box test examines some fundamental aspect of a system with little
regard for the internal logical structure of the software. Black box testing also
called behavioral testing, focuses on the functional requirements of the
software. Black box testing attempts to find errors in the following categories:
 Incorrect or missing functions.

 Interface errors.

Conclusion
Finally, in Online hotel management system, We have developed a
secure, user-friendly Hotel Management System. This System can take
care of each member whether its Owner or Customer.
This System will Help them to properly Manage their Hotel and help in
growth without creating and hassle. This System is completely secure
since every user is provided with user ID and Password so there is no
chance of any unauthorised access.
Online Payment, Booking and cancellation make it easier to use. So, using
this system will help in reducing the labour and provide more facility for
Customer to like Hotel and visit again and again.

Bibliography
1 . Web Links
www.google.com
http://www.scibd.com/doc/Internet Hotel Management
System
http://www.allbookez.com/ Hotel Management Project
Diagrams
www.wikipedia.com
2. Books
Software Engineering – Rajeev Mall
Software Engineering –K.K. Aggawal & Yogesh Singh
DBMS – korth
SQL Server 2008 – Unleased Publication


Minakshi

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Minakshi

Загружено:

Авторское право:

Доступные форматы

HOTEL

BCA- 0900318 IIHST2019BCA318 Page 1

Mr. SUPARV PRADHAN

BCA- 0900318 IIHST2019BCA318 Page 2

No project can be successful without the valuable suggestion of teachers

classmates & friends who indirectly helped me in this endeavors of mine. I

We would like to thanks whole teaching staff of Hi-tech Academy, who

My honorable project guide, I am especially indebted to. I am also

BCA- 0900318 IIHST2019BCA318 Page 3

1. Hotel management system gives us feasibilities for pre – reserved

4. The details of the hotel management system including the tourism

BCA- 0900318 IIHST2019BCA318 Page 4

 A computer based management system is designed to handle all

This project have some more features:

BCA- 0900318 IIHST2019BCA318 Page 6

BCA- 0900318 IIHST2019BCA318 Page 7

In this section we consider on the technical efforts of the proposed system. By

Software requirements Hardware requirements

As we know that behavioural feasibility is related to human or personal related

 User friendly system;-.

 Interaction between new system and exiting system;-

BCA- 0900318 IIHST2019BCA318 Page 9

Like many processes, the development of information system follows a like

Project identification and selection –

different parts. There are

BCA- 0900318 IIHST2019BCA318 Page 10

 Feasibility study- An important outcome of request is feasible. There are

The formal definition of a project is based on the likelihood that the

BCA- 0900318 IIHST2019BCA318 Page 11

 Statement of the problem

BCA- 0900318 IIHST2019BCA318 Page 12

A large number of software design techniques are available. Judging the

The following are some standards for coding:

 Name of the module

It is the process of executing program with the intention of finding errors.

BCA- 0900318 IIHST2019BCA318 Page 13

The implementation phase is less creative than system design. It is primarily

when the candidate system is linked to terminals or remote sites, the

There are three types of implementation.

 Implementation of a computer system to replace a manual system.

Software maintenance follows conversion to the extent that changes are

BCA- 0900318 IIHST2019BCA318 Page 14

 Maintenance is not as rewarding as developing system.

BCA- 0900318 IIHST2019BCA318 Page 15

The database is a fundamental part of the system. It is also called as

BCA- 0900318 IIHST2019BCA318 Page 16

This helps to manage or structure their data in a logical

Conceptual modeling of online computerized hotel management

The emphasis of logical database model is on logic,

BCA- 0900318 IIHST2019BCA318 Page 17

We have developed these interfaces to interact with the system.

These five entities would manage the whole system.

BCA- 0900318 IIHST2019BCA318 Page 18

BCA- 0900318 IIHST2019BCA318 Page 19

BCA- 0900318 IIHST2019BCA318 Page 21

BCA- 0900318 IIHST2019BCA318 Page 22

BCA- 0900318 IIHST2019BCA318 Page 23

Table Name: OwnerMaster

BCA- 0900318 IIHST2019BCA318 Page 25

1. EmployeeID Integer Primary key

Multiple contacts can exist

Table Name: ClientMaster

1. ClientID Integer Primary key