117238618 Online Hotel Reservation System

8/12/2019 117238618 Online Hotel Reservation System

1/13

ONLINE HOTEL RESERVATION SYSTEM

PROBLEM DEFINITION:

The main aim of the entire activity is to automate the process of day to dayactivities of Hotel like Room activities, Admission of a New Customer, Assign a room

according to customers demand, checkout of a computer and releasing the room and finally compute

the bill etc

INTRODUCTION AND PROBLEM DESCRIPTION:

! have tried my best to make the complicated process of HOTELRESERVATIONSYSTEM easy by simple modeling of "#$ diagrams The main purpose of my

e%ercise is performing each "sers activity in computeri&ed way rather than manually which is time

consuming

This pro'ect is used by two types of users

(nline "sers

Administrator )management of the Hotel*

(nline users can see the re+uired articles or news

Administrator can maintain daily updates in the hotel records Administrator

ismust be an authori&ed user He can further change the password There is the facility for

password recovery, logout etc

This system has been designed to computeri&e the following functions that are performed

Room -etail .unctions

(pening a New Room

#odification to room assigned

Check/in and check/out -etail .unctions

Admission of New customer

Check/out of customer

Room assigning related to customers need 0tatement of Customer -etails

Check/in customer/Check/out customer

Room -etails

Total number of Customers in the Hotel

!ndividual customer ReportSOFTWARE REQUIREMENT SPECIFICATIONS (SRS):

Purpose:

The software re+uirement specification will provide a detailed description of there+uirements for the online hotel reservation system This 0R0 will allow for a complete


2/13

understanding of the system and the clear understanding of the system functionality will

allow for the correct software to be developed for the end user .rom this 0R0, the system

can be designed, constructed, and finally tested

OVERVIEW:

The 0R0 is organi&ed into two main sections

(v era l l -esc r ip t io n

0p ec i f i c Re+ u i remen t s

Te O!er"## Des$r%p&%o'

This section describes the general factors that affect the product and its re+uirements

PRODUCT PERSPECTIVEThis online hotel reservation system is the stand/alone system !t !s totally self contained

H"r"re I'&er*"$es

This system will be placed on 1Cs throughout the hotel

So*&"re I'&er*"$es

!n this system, we maintain two data bases These databases include hotel rooms and

customers information These can be modified by the end users The room databases will

include the room numbers and if they are vacant or occupied The customers information

database maintains all the information about the customer such as name, number of

occupants, assigned room, default room rate, phone number, whether or not the room is

guaranteed, credit card number etcProu$& Fu'$ & %o's

Reservation and 2ooking system

Allows for typing in customer information

Has a default room rate that is ad'ustable

!ncludes a description field for the changed rate 3hen a customer checks in, the room number will be changed to occupied in the

database

Ability to modify a reservation

when a customer checks out the amount owed is displayed

records that room is vacant

records payment

allows for space to write customers feedback 4eneral #anager 0ervices

and Automated Tasks 0ystem

Reports generated to audit hotel occupancy, future occupancy and room revenue

5%ception reports listing to the normal cost

Allows addition, deletion and modification of information on rooms and rates


3/13

Creation of users and assigning passwords

U s e r C " r " $ & e r % s & % $ s

5ducational level of hotel reservation system computer software/low 5%perience of

this software/none Technical 5%pertise/little

Appor&%o'%'+ o* Re,u%re-e'&s

The audio and visual alerts will be deferred because of low importance at this time

Assu-p&%o's "' Depe'e'$%es

o The system is not re+uired to save the generated reports

o Credit card payments are not included

SPECIFIC REQUIREMENT

This section contains all the software re+uirements at a level of details ,that when

combine with the system conte%t diagram, use cases, and usecase descriptions, is sufficient

enables designers to design a system to satisfy those re+uirements

E.& er'" # I' & er * "$es

This system will use the standard input6output devices for a personal computer This includes

the following

7eyboard #ouse

#onitor

1rinter

User I'&er*"$es

The user interface screens are

Lo+%' / log into the system as a C0R or #anager

Reser!"&%o'8 Retrieve button, update6save reservation, cancel reservation, change

reservation, ad'ust room rate, accept payment type6credit card

Ce$/0%'8 #odify room stay )eg, new credit card*, check/in customer )with orwithout a reservation*, ad'ust room rate, special re+uests, accept payment type6credit

card

Ce$/ou&8 checkout customer and generate bill

Ho&e# P"1-e'&8 accept payment for room

Roo- ser!%$e/ Create order, modify order, view order, cancel order, generate meal

bill

Cus&o-er Re$or8 Add or update customer records

A-%'%s&er roo-s8 availability and rates

A-%'%s&er user8 create, modify, and delete users9 change password

Repor&s8 select, view, save, and delete reports


4/13

S o * & " r e I ' & e r * " $ e s

The system shall interface with an oracle or access database

H"r"re I'&er*"$es

The system shall run on #icrosoft 3indows based system

Co--u'%$"&%o' I'&er*"$e

The system shall be standalone product that does not re+uire any

communication interfaces

FUNCTIONAL REQUIREMENTS

.unctional re+uirements define the fundamental actions that system must perform

Two categories in .unctional Re+uirements

: Reservation6booking

; #anagement

R e s e r ! " & % o ' 2 B oo / % ' +

The system shall record reservations

The system shall record customer details

The system shall record the room number

The system shall display the default room rate

The system shall display whether or not the room is guaranteed

The system will generate uni+ue confirmation for each reservation

The system will record e%pected check in time and date and also e%pected check out

time and date

The system shall display the amount owed by the customer and record the payment

The system shall record the customer feedback

M " ' " + e - e ' &

The system shall display the hotel occupancy for a specified period of time

The system shall display the room revenue for a period of time

The system shall display an e%ception report where default room has been overridden

The system shall allow for the addition, deletion and also modification of information,

regarding rooms, rates, and user profiles

The system shall allow managers to assign user passwords

No'0*u'$&%o'"# Re,u%re-e'&s

This section defines the needs in terms of performance, logical database re+uirements,

design constraints, reliability, availability, security, maintainability, and portability

CHAN3E MANA3EMENT PROCESS

Changes to this document may be made after approval from the pro'ect manager and

the client approval officer


5/13

USE CASE DIA3RAM

A "se Case specifies the behavior of a system or a part of a system and is a

description of a set of se+uences of actions "se Case -iagram "se case diagram shows the

relationship among use cases within a system or semantic entity and their actors The

relationships area associations between the actors and the use cases, generali&ation betweenthe actors

Actors in (nline Hotel Reservation 0ystem

Client

Travel Agent

Hotel Receptionist

Hotel Administrator "se cases with brief description

I',u%re I'*or-"&%o':

The customer needs to interact with the hotel interface through the personal system

!t involves set of actions

Reser!e2Up"&e Reser!"&%o':

To reserve the room, the customer needs to interact with the website !f the

customer already reserved room, want some updates regarding the increase in occupancy, he

must able to update the data by using his login and password which can be provided by

the administrator

P"1 *or Ho&e#:

This involves set of actions !f the customer ready to book or reserve the room, he

needs to enter his complete details and occupancy level After furnish the details in the

form, he demanded to pay the advance That can be through credit card6debit card He must

enter the correct card number

C"'$e# Reser!"&%o':

The system software should support all the re+uests made by the each authori&ed

customer !f the customer not satisfied with the facilities and occupancy of each room after

few hours he checked in, he may want to cancel the reservation for remaining hours 0ystem

software must be in a position that the payment for the staying hours should captured and

cancel the reservation

Up"&e Ho&e# I'*or-"&%o':

According to the customer feedback, the administrator is update the hotel

information such as offers, discounts on rooms and meals provided by the hotel 3hen thecustomers checkout from the hotel, the database need to "pdate and show the availability to

the new customers

Re&ur' P"1-e'&:

This use case e%tends cancel reservation 3henever the customer wants to cancel

the reservation, system must cancel the reservation and return the payment which remains

5ach and every transaction made by the customer or administrator must be updated with the

customer database and room database This is the brief e%planation about the "se cases in the

hotel reservation system which helps in modeling the dynamic aspects of the system

4enerali&ation relationship e%ists between hotel receptionist and hotel administrator The

relationship between them like child and parent relation Here Administrator assumes as aparent whereas Receptionist acts as a child


6/13

USECASE DIA3RAM:

CLASS DIA3RAM

Class diagrams are the most common diagrams found in modeling ob'ect orientedsystems A class diagram shows a set of classes, interfaces, and collaborations and their

relationships This gives the static design view of the system

C#"ss:

A class is rendered as a rectangle with three components separated with hori&ontal

lines The top compartment is used for displaying the name of the class9 the ne%t two

compartments are used for listing attributes and operation of the class

C#"sses e$#"re *or Reser!"&%o' s1s&e-:

.acility Room Rate


7/13

Hotel

Room Type

5mployee

Travel Agent

Hotel 2ooking

Room Room 2ooking

1erson

Client

Credit Card

I'&er*"$es *or Reser!"&%o' S1s&e-:

2ooking is an interface which can be declared to provide the operations such as

do2ooking)*, cancel2ooking)* to the classes 5mployee, Travel Agent and Client where the

implementation of those methods can be done Here the relationship between the class andinterface is the reali&ation where classes reali&e the interface such that the interface give the

contract and the classes need to carry out that work This is the brief description about the

class diagram and the classes, interfaces declared for the online hotel reservation system


8/13


9/13

STATE CHART DIA3RAM

S&"&e $"r& D%"+r"-:

0tate chart diagrams are for modeling the dynamic aspects of the system A state chart

diagram shows a state machine 0tate chart diagram is useful to model the life time of

an ob'ect And it shows the flow of control from one state to another state

S&"&e M"$%'e:

A state machine is a behavior that specifies the se+uences of states an ob'ect goes

through during its lifetime in response to events

S&"&e:

A state is a condition or situation in the life of an ob'ect during which it satisfies some

condition, performs some activity, or waits for some event

E!e'&:

An event is the specification of a significant occurance that has a location in time andspace 0tate chart diagram commonly contains

0imple states and composite states

Transitions, including events and actions

D%"+r"- Des$r%p&%o':

.rom the diagram which is for reservation of room in a hotel, it is clear that there is a

transition from the idle state to composite state Composite state is a state in which again

the ob'ect undergoes different transitions throughout its life time 3henever the customer

interact with the window interface and make a re+uest for reservation, then the ob'ect stateschanges from idle to composite state !n composite state, the ob'ect moves from one state to

another until the customer reserved room by paying some amount in advance (nce the room

reserved, then the reservation letter may send to the customer mail id by moving its state

to transmitting

(nce the room reserved by the customer, then the ob'ect comes to the idle state again by

coming out of the composite state This is the brief description about the state chart diagram

for the hotel reservation system


10/13

ACTIVITY DIA3RAM

A$&%!%&1 D%"+r"-:

An activity diagram is essentially a fancy flowchart Activity diagrams and state

chart diagrams are related 3hile a state chart diagram focuses on an attention on an ob'ect

undergoing a process, an activity diagram focuses on the flow of activities involved ina single process The activity diagram show how the activities depend on one another

D%"+r"- es$r%p&%o':

The activities are rounded rectangles The activity diagram for the customer who

wants to check out of the room from the hotel with swim lanes can be shown in the diagram

5ach swim lane talks about each ob'ect ie which ob'ect is responsible for which activity A

single transition comes out of each activity, connecting it to the ne%t activity Here we are

dealing with customer and receptionist6administrator .rom the diagram, the activity started

by the customer ob'ect which starts as re+uest made by the customer wants to check out of

the room at desk top interface Then it given a form such that asking about the customer

details which are already loaded in the database !f the customer enters the information whichmatches with the database information, then the customer bill should be printed And then the

se+uence of activities is done step by step such that checkout customer, unassigned room,

finally gives the customer bill to the customer Then the customer gets the bill and simply

pays by the credit card and simply leaves the room !f the details entered by the customer at

the starting stage are not matched with the information from the database, the customer must

be informed that he didnt check into the hotel room


11/13

COMPONENT DIA3RAM

Co-po'e'& D%"+r"-:

!t helps to model the physical aspects of ob'ect/oriented systems A component

diagram shows the organi&ation and dependencies among a set of components 3e use the

component diagrams to model the static implementation view of a system This involvesmodeling the physical things that reside on anode such as e%ecutables, libraries, tables, files,

and documents A component diagram commonly contains


12/13

DEPLOYMENT DIA3RAM

Dep#o1-e'& D%"+r"-:

!t also helps in modeling the physical aspects of an ob'ect/oriented system A

deployment diagram shows the configuration of run time processing nodes and the

components that live on them .or most part, this involves the modeling the topology of

the hardware on which the systems e%ecutes

-eployment diagram commonly contains

Nodes

-ependency and association relationships

D%"+r"- Des$r%p&%o':

-eployment diagram for the online hotel reservation system mainly depicts the

processors which are widely distributed around the world and the components which are

configured them These all processors are connected through the device in the distributed

system Cache server is used to store the transactions which are done by the customer at thetime shortage of memory until the memory storage should e%tended The primary server is

placed at the head branch of hotel chain and remaining servers or processors are located

geographically dispersed and connected through the internet !n our pro'ect we assumes as we

have a chain of hotels which are at different places such as "7, "0 etc


13/13

SOFTWARE EN3INEERIN3

CASE STUDIES ONLINE HOTEL RESERVATION

SYSTEM

0"2#!TT5- 2=

C!N-H"#ATH!

:;#!>>?

Documents

117238618 Online Hotel Reservation System