hotel-management-system - copy.doc

8/13/2019 Hotel-Management-System - Copy.doc

1/64

HOTEL MANAGEMENT SYSTEM.


2/64

Abstract

Our Project is a software that can be used in the hospitality industry. Through this

software the Hotel administration can manage their loyalty programs in an effective way. The

Hotel Loyalty Programs can be used to entice guests into becoming a regular guest at the hotel.

These programs are especially beneficial to hotel chains, where the benefits of the program can

span over their entire hotel chain. Personalized service and rewards deliver eceptional

eperiences to guests, and ma!e them come bac! for more.

The scope of the project defines only those functionalities which are provided by

our project. On the other hand the scope of the users involved in the "ewards and Loyalty

Program is defined as the roles of each user in the system and their accessibilities to the different

elements and prospects within the system.

The project will include three main users who ta!e part in the wor!ing of the

system as a complete functionality. #onsidering the complete functionality and interactions

within the Hotel we will define the roles of each user along with their access permissions

towards the various elements of the system.

The various users participating in the system are as follows$

%i& The Hotel 'dministrator

%ii& The Hotel (ront )es! Office

%iii& The *ember % The customer of the hotel&


3/64

INTRODUCTION

This project includes three types of users i.e. the hotel administration, the hotel

front des! office and the customers of the hotel. This project wor!s primarily on the basis of the

type of membership cards the hotel administration provides to its customers who subscribed for

the hotel. These membership cards represent the points allocated to the customers who

subscribed for the hotel.

The subscription to the Hotel is offered to the customers of the hotel when they

ma!e their first reservation in the hotel. (or this the hotel maintains a subscription form and is

made available on the hotel+s website. The hotel can also maintain a paper form which can be

given to the new customers who have made their first reservation. The hotel can also opt to send

the subscription form through emails to the appropriate customers. The details of all the

customers are maintained by the hotel administration as a part of the hotel+s database. The hotel

is solely responsible on its decision on how to avail the subscription form to its customers.

's a hotel provides the hotel with three types of membership cards i.e. %i& ilver

%ii& -old and %iii& Platinum. The names of these membership cards can be edited as per the will

of the hotel. The number of different types in the membership cards can also be edited as per the

hotel+s choice.

The hotel administration will be given an address boo! table as a part of the

software which can be updated by the hotel staff in order to maintain the records of all the

subscribers of the Hotel+s Loyalty Program. This address boo! is supposed to be updated on a

regular basis to contain the updated membership details list of all the subscribers of the Hotel+s

Loyalty Program.

nitially when a customer of the hotel subscribes for the hotel+s "ewards and

Loyalty program, he/she is given a membership card of silver type. (rom this moment onwards

the customer will be a part of the "ewards and Loyalty Program that the hotel offers. Hence the

customer becomes a subscriber for the hotel+s "ewards and Loyalty program and can now

increase his points of loyalty by ma!ing more and more reservations in this hotel or by spending

on other hospitality services offered by the hotel. n this way the customer who is now a member

of the "ewards and Loyalty program of the hotel can increase his/her points by becoming a

regular customer to the hotel. *oreover by increasing his/her points the customer can improve


4/64

his/her membership type so as to avail nice offers and discounts from the hotel.

The subscribers to this program can view their points from time to time either

through the hotels+ website or through automated mails delivered by the hotel. This depends on

the hotels decision on how to implement the process of delivering updates to their subscribers.

0henever the subscribers have crossed the milestone of their respective

membership type, they are promoted to the net membership type and the new membership card

is posted to the respective subscriber+s official postal address. This posting of the membership

card is the responsibility of the front des! office of the respective hotel. 'll this happens when an

alert message triggers to the front des! office of the hotel as and when the milestones of any

subscriber is crossed. This automated reminder can benefit the hotel+s administration by reducing

their overhead of maintaining and updating their customers+ membership details. t also acts as a

prime factor in the process of maintaining consistency in updating the records. n this way it is

close to impossible for the management to miss on the updating of any membership account.

(igure$Overview of Proect


5/64

PRO!ECT O"ER"IE#$

This section involves the scope of the project and the scope of its users. The scope of

the project defines only those functionalities which are provided by the oftware. On the other

hand the scope of the users involved in the "ewards and Loyalty Program is defined as the roles

of each user in the system and their accessibilities to the different elements and prospects within

the system.

This ystem will include three main users who ta!e part in the wor!ing of the system

as a complete functionality. #onsidering the complete functionality and interactions within the

ystem we will define the roles of each user along with their access permissions towards the

various elements of the system.

The various users participating in the system are as follows$ %i& The Hotel

'dministrator %ii& The Hotel (ront )es! Office %iii& The *ember % The customer of the hotel

who subscribed for the Hotel&

Role Based Access

a) The Hotel Administrator

i& #onfigures The #onfiguration Page

The hotel administrator is responsible for deciding on the number of points to be

allocated per day stay and also the number of points allocated for each hospitality

service provided by the hotel. These hospitality services may include$ "eservation

charges, 'dd Ons, "estaurants, 1ars, hops, Other 2tra #harges depending on the

corresponding hotel.

ii& #reation Of ' 3ew *ember

The hotel administrator can create a new user in the "ewards and Loyalty Program by

approving the subscription submitted by the customer as legitimate only after

reviewing his/her details completely.


6/64

iii& #reation Of The ubscription (orm (or The "ewards 'nd Loyalty Program

The hotel administrator can design the subscription form for ma!ing it available to all

the customers who are new to the hotel. Having made their first reservation, these

customers are provided with the subscription form.

iv& *a!ing The ubscription (orm 'vailable To The 3ew #ustomers

The hotel administrator can do this in three ways as mentioned below$

The form can be made available on the hotel+s website.

The form can be mailed to his new customers % i.e. those customers who have

just made their first reservation in the hotel &.

The form can be handed over in hand at the time when the customer ma!es

his/her reservation for the first time in the hotel.

v& *anage 2isting *embers

The hotel administrator has the access to all his subscribers+ information and

can therefore communicate with them. He can send automated messages to his

eligible subscribers about any offers or discounts which are announced.

The hotel administrator can send alert messages to the eisting "ewards and

Loyalty members % i.e. customers who have subscribed for the "ewards and

Loyalty Program & regarding their membership epiry issues.

The hotel administrator maintains the details of all the members of the hotel+s

"ewards and Loyalty Program.

'part from details in the form of data records and tables li!e address boo! the

hotel administrator also maintains and generates reports for details of all the

subscribers to the hotel+s "ewards and Loyalty Program.

vi& *aintains nformation 'bout #ards To 1e ent

The hotel administrator maintains a list of all the cards that are to be delivered to the

respective members of the "ewards and Loyalty Program along with their complete details. This


7/64

list may include members who have lost their membership cards and also the new members of

the "ewards and Loyalty Program.

vii&"eward "edemptionThe hotel administrator maintains all the details of reward redemption and the

members associated with this functionality.

b) The Hotel Front Desk Office

i& )elivers *embership #ards To *embers

The (ront )es! Office is prompted when there is a member whose

membership points cross the milestone of the respective membership card

type. n this case the front des! office is responsible for delivering the updated

card to the respective member of the "ewards and Loyalty Program.

The (ront )es! Office is also responsible for delivering membership cards to

all the members of the list given by the hotel administrator. This list includes

the members who have lost their membership cards and have applied for new

ones and also those members who are new to the "ewards and Loyalty

Program and are yet to receive their default membership cards.

c) The Member

i& 4iew The *ember+s Profile Page

The members i.e. the customers who have subscribed for the "ewards and Loyalty

Program of the hotel can view their profile page in the hotel+s website under the"ewards and Loyalty section. This profile page also contains the "ewards and

Loyalty points of the member along with the membership details.

ii& 'pply (or ' 3ew *embership #ard

The member can apply for a new membership card in case he/she loses their card.


8/64

iii& nteract 0ith The (ront )es! Office

The member can interact with the front des! office of the hotel for any !ind of

en5uiries.

d) The System ( our Softare )

i& *aintains The #onfiguration Page

The latest configuration details are maintained. These details are available for the

hotel administrator to modify whenever necessary. The hotel administrator can find

these details on the configuration page in the "ewards and Loyalty section of the

hotel+s website.

ii& *aintains ' 4iew/*odify Page

This page is only available for the hotel administrator to modify or update its

members+ membership details.

iii& *aintains ' earch Page

This is provided for the hotel administrator and the hotel front des! office. Through

this a search can be made possible for a member+s details or for a particular

reservation+s details.

iv& *aintains ' "eports Page

Through this the system generates reports for the different users and also for the

different reservations related to the hotel. This pages accessibility can be defined by

the hotel administrator.


9/64


10/64

SYSTEM ANALYSIS

PROPOSED SYSTEM$

e=ee "ewards and Loyalty is a software that can be used in the hospitality

industry. Through this software the Hotel administration can manage their loyalty programs in an

effective way. The Hotel Loyalty Programs can be used to entice guests into becoming a regular

guest at the hotel. These programs are especially beneficial to hotel chains, where the benefits of


11/64

the program can span over their entire hotel chain. Personalized service and rewards deliver

eceptional eperiences to guests, and ma!e them come bac! for more.

The system will be divided into the following subsystems.

>ser

-et nformation

e=ee Loyalty and "ewards is a 0eb 'pplication. n this system administrator

collects the information from different hotels. e=ee Loyalty and "ewards system administrator

contacts the specified rooms and collects the information and update the information time to time

and store in database in a fleible manner.

RE*UIREMENT ANALYSIS & SPECI%ICATION$

The scopes of e=ee Loyalty and "ewards are$

The scope of the project defines only those functionalities which are provided by the

e=ee "ewards and Loyalty oftware. The scope of the users involved in the "ewards and Loyalty Program is defined as the

roles of each user in the system and their accessibilities to the different elements and

prospects within the system..

The scope of this system includes planning and designing. The contents are as follows$

User Mo'+(e Tas,s$

#reate a separate *enu item in e=ee(rontOffice application called ?Loyalty and

"ewards@

n that create the following sub menu items viz.,


12/64

Me)+ Str+ct+re

Lo-a(t- a)' Rewar's

#onfigure

*embership Levels

Points

o *etric Types

o Aualification *etrics

o Points 'llocation

o Points Purchase

o "ewards

*embership )etails

'dd/4iew/*odify

earch

"eports

%EASIILITY STUDY

TECHINICAL %EASIILITY$

2valuating the technical feasibility is the tric!iest part of a feasibility study. This is

because, .at this point in time, not too many detailed design of the system, ma!ing it difficult to


13/64

access issues li!e performance, costs on %on account of the !ind of technology to be deployed&

etc. ' number of issues have to be considered while doing a technical

analysis.

i& >nderstand the different technologies involved in the proposed system$

1efore commencing the project, we have to be very clear about what are the technologies

that are to be re5uired for the development of the new system.

ii& (ind out whether the organization currently possesses the re5uired technologies$

o s the re5uired technology available with the organizationB

o f so is the capacity sufficientB

(or instance C

?0ill the current printer be able to handle the new reports and forms re5uired for the new

systemB@

OPERATIONAL %EASIILITY$

Proposed projects are beneficial only if they can be turned into information

systems that will meet the organizations operating re5uirements. imply stated, this test of

feasibility as!s if the system will wor! when it is developed and installed. 're there major

barriers to mplementationB Here are 5uestions that will help test the operational feasibility of a

project$

s there sufficient support for the project from management from usersB f the current

system is well li!ed and used to the etent that persons will not be able to see reasons for

change, there may be resistance.

're the current business methods acceptable to the userB f they are not, >sers maywelcome a change that will bring about a more operational and useful systems.

Have the user been involved in the planning and development of the projectB

2arly involvement reduces the chances of resistance to the system and in

-eneral and increases the li!elihood of successful project.


14/64

ince the proposed system was to help reduce the hardships encountered. n the eisting

manual system, the new system was considered to be operational feasible.

ECONOMIC %EASIILITY$

2conomic feasibility attempts < weigh the costs of developing and implementing a

new system, against the benefits that would accrue from having the new system in place. This

feasibility study gives the top management the economic justification for the new system.

' simple economic analysis which gives the actual comparison of costs and

benefits are much more meaningful in this case. n addition, this proves to be a useful point of

reference to compare actual costs as the project progresses. There could be various types of

intangible benefits on account of automation. These could include increased customer

satisfaction, improvement in product 5uality better decision ma!ing timeliness of information,

epediting activities, improved accuracy of operations, better documentation and record !eeping,

faster retrieval of information, better employee morale.


15/64

SYSTEM DESIGN

DATA %LO# DIAGRAMS

)ata flows are data structures in motion, while data stores are data structures.

)ata flows are paths or Dpipe lines+, along which data structures travel, where as the data stores

are place where data structures are !ept until needed.


16/64

)ata flows are data structures in motion, while data stores are data structures at

rest. Hence it is possible that the data flow and the data store would be made up of the same data

structure.

)ata flow diagrams is a very handy tool for the system analyst because it gives

the analyst the overall picture of the system, it is a diagrammatic approach.

' )() is a pictorial representation of the path which data ta!es (rom its initial

interaction with the eisting system until it completes any interaction. The diagram will describe

the logical data flows dealing the movements of any physical items. The )() also gives the

insight into the data that is used in the system i.e., who actually uses it is temporarily stored.

' )() does not show a se5uence of steps. ' )() only shows what the different

process in a system is and what data flows between them.

The following are some )() symbols used in the project

2ternal entities

)'T'(LO0

RULES %OR D%D$

(i the scope of the system by means of contet diagrams.

Process$ ' transaction of information thatresides within the bounds of the systemto be module.

)'T'TO"2$ ' repository of data that is tobe stored for use by one or more processes,may be as simple as buffer of 5ueue or as arelational database.


17/64


18/64

L242LE; $ >1FT2* L242L )'T'(LO0 (>3#TO3'L

L242LE< $ (L2 L242L )2T'L )'T' (LO0.

The input and output data shown should be consistent from one level to the net.

LE"EL/0$ SYSTEM INPUT1OUTPUT LE"EL

' levelE: )() describes the systemEwide boundaries, dealing inputs to and outputs from

the system and major processes. This diagram is similar to the combined userElevel contet

diagram.

LE"EL/2$ SUSYSTEM LE"EL DATA %LO#

' levelE; )() describes the net level of details within the system, detailing the data

flows between subsystems, which ma!eup the whole.

LE"EL/3$ %ILE LE"EL DETAIL DATA %LO#

'll the projects are feasible given unlimited resources and infinite time. t is both

necessary and prudent to evaluate the feasibility of the project at the earliest possible time.

(easibility and the ris! analysis are pertained in many ways. f project ris! is great.


19/64

DATA DICTIONARY


20/64


21/64


22/64


23/64


24/64


25/64

ER DIAGRAMS

UNI%IED MODELING LANGUAGE DIAGRAMS

The unified modeling language allows the software engineer to epress an

analysis model using the modeling notation that is governed by a set of

syntactic semantic and pragmatic rules.

' >*L system is represented using five different views that describe the

system from distinctly different perspective. 2ach view is defined by a set

of diagram, which is as follows.

>ser *odel 4iew

i. This view represents the system from the users perspective.

ii. The analysis representation describes a usage scenario from the

endEusers perspective.

tructural model view

n this model the data and functionality are arrived from inside the

system.

This model view models the static structures.

1ehavioral *odel 4iew

t represents the dynamic of behavioral as parts of the system,

depicting the interactions of collection between various structural

elements described in the user model and structural model view.

mplementation *odel 4iew

n this the structural and behavioral as parts of the system are

represented as they are to be built.


26/64

2nvironmental *odel 4iew

n this the structural and behavioral aspects of the environment in which the

system is to be implemented are represented.

>*L is specifically constructed through two different domains they are

>*L 'nalysis modeling, which focuses on the user model and

structural model views of the system.

>*L design modeling, which focuses on the behavioral modeling,

implementation modeling and environmental model views.

>se case )iagrams represent the functionality of the system from a user+s point of

view. >se cases are used during re5uirements elicitation and analysis to represent the

functionality of the system. >se cases focus on the behavior of the system from eternal

point of view.

'ctors are eternal entities that interact with the system. 2amples of actors

include users li!e administrator, ban! customer Getc., or another system li!e central

database.


27/64

Use Case 'ia4ra5 A'5i)$ e6ee Lo-a(t- a)' Rewar's

Admin

Login

Password

Configure

Search

Add/View

Reports


28/64

Use Case Dia4ra5 User $ e6ee Lo-a(t- a)' Rewar's

User

Registration

Login

Forgot Password

Update Profile

View Details

Get Rooms

Log ut


29/64

Se7+e)ce Dia4ra5 / e6ee Lo-a(t- a)' Rewar's 8A'5i) Lo4i)9

Administrator Login Home Data Base

1 : Login()

2 : Invalid Data()

3 : Request to DB()

4 : Response rom DB()

! : "et Home()


30/64


31/64

>ser 'ctivities

#ser $as%ord Data Base&ie% 'odi

1 : *ange()

2 : &ie% o%n Details()

3 : 'odi( )

4 : +ave()

! : +ave()

, : +ave()


32/64


33/64

networ! access to data but the comparison dens thereM The file server simply provides a remote

dis! drive that can be accessed by L'3 applications on a fileEbyEfile basis. The client server

offers full relational database services such as ALE'ccess, "ecord modifying, nsert, )elete

with full relational integrity bac!up/ restore performance for high volume of transactions, etc. the

client server middleware provides a fleible interface between client and server, who does what,

when and to whom.

0hy #lient erver

#lient server has evolved to solve a problem that has been around since the earliest

days of computing$ how best to distribute your computing, data generation and data storage

resources in order to obtain efficient, cost effective departmental an enterprise wide data

processing. )uring mainframe era choices were 5uite limited. ' central machine housed both the

#P> and )'T' %cards, tapes, drums and later dis!s&. 'ccess to these resources was initially

confined to batched runs that produced departmental reports at the appropriate intervals. ' strong

central information service department ruled the corporation. The role of the rest of the

corporation limited to re5uesting new or more fre5uent reports and to provide hand written forms

from which the central data ban!s were created and updated. The earliest client server solutions

therefore could best be characterized as ?L'42E*'T2"@.

TimeEsharing changed the picture. "emote terminal could view and even change the

central data, subject to access permissions. 'nd, as the central data ban!s evolved in to

sophisticated relational database with nonEprogrammer 5uery languages, online users could

formulate adhoc 5ueries and produce local reports with out adding to the * applications

software bac!log. However remote access was through dumb terminals, and the client server

remained subordinate to the laveN*aster.

(ront end or >ser nterface )esign

The entire user interface is planned to be developed in browser specific

environment with a touch of ntranetE1ased 'rchitecture for achieving the )istributed #oncept.


34/64

The browser specific components are designed by using the HT*L standards, and the dynamism

of the designed by concentrating on the constructs of the ava erver Pages.

#ommunication or )atabase #onnectivity Tier

The #ommunication architecture is designed by concentrating on the tandards of

ervlets and 2nterprise ava 1eans. The database connectivity is established by using the ava

)ata 1ase #onnectivity.

The standards of threeEtire architecture are given major concentration to !eep the

standards of higher cohesion and limited coupling for effectiveness of the operations.

(eatures of The Language >sed


35/64


36/64


37/64


38/64


39/64

REPORTS


40/64


41/64


42/64


43/64


44/64


45/64


46/64


47/64


48/64


49/64


50/64


51/64

SYSTEM TESTING

Testi)4


52/64

Testing is the process of detecting errors. Testing performs a very critical role for

5uality assurance and for ensuring the reliability of software. The results of testing are used later

on during maintenance also.

Ps-c:o(o4- of Testi)4

The aim of testing is often to demonstrate that a program wor!s by showing that it

has no errors. The basic purpose of testing phase is to detect the errors that may be present in the

program. Hence one should not start testing with the intent of showing that a program wor!s, but

the intent should be to show that a program doesn+t wor!. Testing is the process of eecuting a

program with the intent of finding errors.

Testi)4 Obectives

The main objective of testing is to uncover a host of errors, systematically and

with minimum effort and time. tating formally, we can say,

Testing is a process of eecuting a program with the intent of finding an error.

' successful test is one that uncovers an as yet undiscovered error.

' good test case is one that has a high probability of finding error, if it eists.

The tests are inade5uate to detect possibly present errors.

The software more or less confirms to the 5uality and reliable standards.

Leve(s of Testi)4


53/64

n order to uncover the errors present in different phases we have the concept of

levels of testing. The basic levels of testing are as shown belowG

#lient 3eeds

"e5uirements

)esign

#ode

S-ste5 Testi)4

The philosophy behind testing is to find errors. Test cases are devised with this in

mind. ' strategy employed for system testing is code testing.

Co'e Testi)4$

This strategy eamines the logic of the program. To follow this method we

developed some test data that resulted in eecuting every instruction in the program and module

i.e. every path is tested. ystems are not designed as entire nor are they tested as single systems.

To ensure that the coding is perfect two types of testing is performed or for that matter is

performed or that matter is performed or for that matter is performed on all systems.

T-;es Of Testi)4

'cceptance

Testing

+(stem -esting

Integration -esting

#nit -esting


54/64


55/64

n this project integrating all the modules forms the main system. 0hen integrating

all the modules have chec!ed whether the integration effects wor!ing of any of the services by

giving different combinations of inputs with which the two services run perfectly before

ntegration.

S-ste5 Testi)4

Here the entire software system is tested. The reference document for this process

is the re5uirements document, and the goal is to see if software meets its re5uirements.

Here entire D'T*+ has been tested against re5uirements of project and it is

chec!ed whether all re5uirements of project have been satisfied or not.

Acce;ta)ce Testi)4

'cceptance Test is performed with realistic data of the client to demonstrate that

the software is wor!ing satisfactorily. Testing here is focused on eternal behavior of the system

the internal logic of program is not emphasized.

n this project D3etwor! *anagement Of )atabase ystem+ have collected some

data and tested whether project is wor!ing correctly or not.

Test cases should be selected so that the largest number of attributes of an

e5uivalence class is eercised at once. The testing phase is an important part of software

development. t is the process of finding errors and missing operations and also a complete

verification to determine whether the objectives are met and the user re5uirements are satisfied.

#:ite o< Testi)4

This is a unit testing method where a unit will be ta!en at a time and tested

thoroughly at a statement level to find the maimum possible errors. tested step wise every

piece of code, ta!ing care that every statement in the code is eecuted at least once. The white

bo testing is also called -lass 1o Testing.

have generated a list of test cases, sample data, which is used to chec! all possible

combinations of eecution paths through the code at every module level.


56/64

(ac, o< Testi)4

This testing method considers a module as a single unit and chec!s the unit at

interface and communication with other modules rather getting into details at statement level.Here the module will be treated as a bloc! bo that will ta!e some input and generate output.

Output for a given set of input combinations are forwarded to other modules.

Criteria Satisfie' b- Test Cases

Test cases that reduced by a count that is greater than one, the number of

additional test cases that much be designed to achieve reasonable testing.

Test cases that tell us something about the presence or absence of classes of errors,

rather than an error associated only with the specific test at hand.


57/64

SO%T#ARE TOOLS

Met:o'o(o4-


58/64

The method being used in developing the system is the system )evelopment Life

#ycle %)L#& The )L# process includes project identification and selection, project initiation

and planning, analysis, design, implementation and maintenance.

.

(igure


59/64


60/64

TECHNICAL NOTES

#i)'ows =P O;erati)4 S-ste5


61/64

Microsoft "is+a( St+'io/300> 3.0 %ra5ewor,

Microsoft MYS*L/?.0.?2b/wi)@3

I)ter)et Moi((a %ire%o

hotel-management-system - copy.doc

Documents