Hotel Mana gemen t S)-ste m

1 INT RO DU CT ION
rooms of Hotel through onJinc by the
Jbe HOleJ Mana gemen t System is a tool for booking the
access to the custom er information-
cussomer. It provides the prope r management tools and easy

I.I Pur pos e

Specification (SRS) main objec tive is to
This Hotel Mana gemen t System Software Requirement

pr0\'ide a base for the foundation of the project

_ It gives a comprehensive view ofbow the system

is supposed to work and what is to be expected by

the end users. CLiem·s expec tation and

iguous functional and non-f unctio nal

r?qUirements are analyzed to produce specific unamb
ciear un~erstanding to build a system
requirements, so they can be used by development team with

as per end user needs.

This SRS for HMS can also be used for future as basis
for detailed understanding on how projec t

"as started. It provid es a blueprint to upcoming new

developers and maintenance teams to assist

eability.
in maintaining and modif }ing this project as per required chang

I IP :i.g:e
J.2 Scope of the Project
ne ff.\t5 is ir.!mdt:d fr~ t:.1t me1'~-m fOJ" mom that can be made through ooline. It will

be af)k tD the ,-mew {.~ of Li..e Hmet Our Ho<el Management S ~ will have

aid users: Cwu.~. ~i1m3 , and Hntel Manager. Hotel Management System will

cawsis of Booking M~2 ~ Sy.t:..~ mMs Sen-a, and Report Generator. Customers will

be ,bk to ~k for rofJffl•i a\"'ili!abiiny, , e ~ (1-~ rooms, and pay for the room. .Receptionist will

11,\-e ~ess to u;xiale or modify oocJiing ~.ai~ Manager '-'ill able to view the fm.anciaJ report

a,d abk 10 u,dU room mfurw..ati!,'1) .G ro;a an.I category.

The awn goa.J of this imroo~ HMS software is to simplify every day process of

b:'.tl Day to da) Hot.ds are ir,~,mg .-a-,d tr.e,. reed to automate to provide customer ease of

,:::;ns, Jt ~ill be ..bk to take car~ of ~m to ClS5t1>mer in a quick manner. This automation will

x ~le to rep'...au frie drav-bacb of !a,-~ cu:m,rrf'::J information ph)'sical files "Ahich were difficult
1c, ~,d~. S,,;,-.:ure 1 ram.a::tKJfl,. quid r ~ I vf infm:-.atioo, ease of use, quick recovery of errors,

!aJt aoJer-.uY.:e are io<JfTie of t}-;e btr.-efits tt:ai devekF.a :t ream •-ill t:e ,.orkmg on to achieve end

2 P a2e
1•3
Definitions, Acronym
s and abbreviations
So ftw ar e Re qu ire m en

-
SRS t Sp ec ifi ca tio ns

HMS Hotel M an ag em en t Sy -
ste m
-
DBMS Da tab as e M an ag em en
t Sy ste m
-
Blueprint A design tec hn ica l pl
an

React Js Re ac t J av as cr ip t

HTIP/HTTPS Hy pe r Te xt Tr an sfe r
Pr ot oc ol /S ec ur e

API Ap pl ica tio n in ter fa ce

OS
Op er ati ng Sy ste m

JSP
Ja va Se rv er Pa ge s

,
RTM
Re qu ire me nt Tr ac ea bi
lit y Matrix

FR
Functional Re qu ire me
- nt

NFR
No n Functional Re qu
ire me nt
J.4 References
, Ian SommervilJe
[1] Software Engineering cf11 Edition

nt B. Navathe
6 Edition, Ramez EJmasri, Shamka
th
tem~
[1] Fundamentals ofD atab ase S_ys

ram representation.htm
w.tutorialspoint.com/dbms/er diag
[3J ER Diagram Tutorial: hnps: /ww

7/ch02.htm I
: '/morse.inf.unideb.hu/valseg/!!vbitt/0
[4J Requirement Engineering: hnp

s:'/www.scribd.com/doc/638 24633/Hotel-Management-
Pl Hotel ~1anagement System: http
Svsrem

.com/doc~7927992/Hotel -Management-Case-Study
[6] Case Study: hnps: www.scribd
1

.tripod.com·cs457/dfd.htm
[l Data Flo " Diagram: http: 'mvYee

engineering
.wikipedia.onv\,\,iki/Requirements
Requirement Engineering; hnps: ·/en

4' •
J.5 Overview
describes the overall descriptions which includes
The remaining sections of this documentations
of users. It also consists of Assumptions, and
product perspective and functions, characteristics
on 2. Section 3 includes Specific Requirements
Constraints. Overall description is listed in secti
l requirements, External Interface Requirements,
which consists of Functional and Non-functiona
irements, Capacity Requirements, Availability
Software System Attributes, Performance Requ
irement Traceability Matrix.
Requirements, Safety Requirements and Requ
 HotelManagementSystem

2 OVERALL DESCRIPTION
2.1 Product Perspective

Application Server

I
i !:
i~
; 11 -~DBC_
l/1 Mong<:Db
I
I

' I t
i
\'-___)
F,gurt! 2. I Product Per.vpecllve

61P ag~
-
2.2 Product Fun ction s
HotelManagementSystem

Our Product General functions are:

• Customer Registration

• Check for Availability Of Rooms

• Display the Rate

• Confinnation Of Booking

• Email Notification

• Payment

• Set Room Details

• Manage Booking Details

• Generate Report

• Custo mer Service

7jP .lft..'
-
,·u~o mrr

. \' ' '

I M,111.,11:., I
L ______ .-1

2.3 Use,· Chnracteristics

There arc 3 ust-r L~, ds in '-'ur I h.\td ~fan~ ~""l\h. 'tll
~<-m:

A. lfotd Man~g.cr

B. Reccpt i\,nist
 - c. customers
HotelManagementSystem

.\13JUlget' hit'1e e,~ access ta the hotel system. Manager is solely responsible for managing hotel

resvurc.es and smth. Man{lgcr can view any report such as financial report, customer information,

l)oOking infom1 ation. and mom information. analyze them and take the decision accordingly.

,f!lllger is required t-..) ha, e C.'{perienee on managing hotel previously, and have base knowledge of

,t\t~base and spplication sen er.

RN'f'l)tioaisl

H,ll~J Receptionist S\.Jle purpo~--e is to provide the quality customer service. She have least access

ch:ln manu,ger. She can m:mnge the OC"iQking details. She can search for availability of rooms, add

the ('.U-~J.~mc:-.r. ~tim1 th(' booking, and update the booking details. Manager of hotel would

prohahl) \\&nt th<" ~e--pti0nisr ,,ho have good communication skills and command over English

bngu..,gt:, Sh~ sh,')t.tld h;n e basic IT Knov, ledge..

Customttr

l u,t'"m~ rt)"(" , nal part of rhe- s) s.t~1 Customer havl! access to view the vacant room information

and prce range The) ~\i.")uld be nhle 11.,1 contim1 the hooking and cancel it if necessary. Customers

'ia, c «,,~sh."\ ~i'1-..')0\ef ~f\ ,ce desk port.JI ll'l forward th~ir inquiry. Customer should at least be

.::.lpJole 10 u,~ the '-' ch l I mrc:rfau

9j, J_~

b
-
., 4 comtnints

om:n iCS- l."J tS ~ ~ t : : . Sihl ( ic

,r\. IIJ-•1•~~•>:a:n-n-11-• C •es.. -ie- -~~Jxr ix be hasod an Ja\·a on~--

2..S ...\s....qimption and Depen de-nci cs

•-u..,..s C."S... a:Jii - ~ S.:0-::r- • r l ",~:i 00 lf imase of any ditoculties .. SRS

- HotelManagementSystem

3 SP~CIFIC REQUIREMENTS
3.1 External Interface Requirements

J.1.1 User Interfaces

~:reen Name Description

Login Log into the system as a CSR or Manager

Reservation Retrieve button, update/save reservation, cancel reservation, modify

reservation, change reservation, adjust room rate, accept payment
type/credit card

Check-in Modify room stay (e.g., new credit card), check-in customer {with or
without a reservation), adjust room rate, special requests, accept
payment type/credit card

Checkout Checkout customer, generate bill

Hotel Payment Accept payment for room and food

Room Service/Restaurant Create order, modify order, view order, cancel order, generate meal
bill

-: •::::- r\a me Description

-
Customer Record

Administer Rooms
Add or update customer records

Availability and rates

r--.....--------i----------------------i
Ad,r.-•ruster
• User create, modify, and delete users; change password

1 IJP :•ge
 HotelManagementSystem

Create, modify, and delete meal items and prices

Select, view, save, and delete reports

oata Requ ireme nts

1l!e logical database requirem ents include the retention of the following data element s.
This list is not
acornplete list and is designed as a starting point for developm ent.

1. Booking /Reserva tion System

2. Custome r first name

3. custome r last name

4. custome r address

s. Custome r phone number

6. Number of occupan ts

7. Assigned room

8. Default room rate

9. Rate descript ion

10. Guarant eed room (yes/no)

11. Credit card number

u. Confirm ation number

13. Automa tic cancella tion date

14. Expected check-in date

15. Expected check-in time

16. Actual check-in date

 4
W ;;: h tee• ltd ltat::Z

HotelManagementSystem

11. Actual check-in time

18. Expected check-out date

19. Expected check-out time

20. Actual check-out date

21. Actual check-out time

22. Customer feedback

23. Payment received (yes/no)

24. Payment type

25. Total Bill

11.l Software Interfaces

WebSeryer

• Apache Tomcat Server, OS (Windows)

• Mongo DB, OS (Windows)

Do-c!ovrncot Eod

• React J~ Css, Bootstrap, React Libraries, HTML, XML, JavaScript, OS(Windows)

13 II' :lg~
 HotelManagementSystem

-
J.1.3 Hardware Interfac es

- Server Side
....

Monitor Processor RAM Disk Space

.- -

Resolution: Intel or AMO 2GHZ 4GB 10GB

1024x768 .

141P a~1.·
 1 {;(iteO ., , .

HotelManagementSystem

TECHNOLOGIES USED
Technology Description

IDE

VS Code

Languages HTML, JavaScript ,CSS ,React

API Fakestoreapi.com/products

Reco1nmended Google Chrome,

Browser
Microsoft Edge

Operating Systen1 Windows 10,8,7,XP

151P ag~
 I

HotelManagementSystem

unication Interfa ces

3-t.4 C0 0110
'Jbesystem shall be using HTfP/H ITPS for communication over Internet and for intranet
nications, it shall use TCP/IP protocol.
c:()IPIDU

3.8 Software Syste m Attrib utes

. Correctness: This system should satisfy the normal regular Hotel Management operatio
ns
precisely to fulfill the end user objectives

• Availability: The system shall be available during normal hotel operating hours

• Reusability: Specify the factors required to use the available components of the availabl e
components of the system in other system as well.

• Efficiency: Enough resource s to be implemented to achieve the particular task efficient

ly without
any hassle._

• Flexibility: System should be flexible enough_ to provide space to add new features
and to handle
them conveniently

• Integrity: System should focus on securing the customer information and avoid
data losses as
much as possible

• Portability: The system should run in any Microsoft windows environment.

• Vsability: The system should provide user manual to every level of users.

161P nu~
 HotelMana ementS stem
testability: The system should be able to be tested to confinn the performance and clients

specifications.

• ~iotainability : The system should be maintainable.

J.9 Requirem ent Traceabil ity Matrix

Tbe Requirement Traceability Matrix (RTM) reflects the correlation between Non Functional

Requirements (NFR) and Functional Requirements (FR). The RTM is a documentation that associates the

requirements entirely throughout the validation process. Traceability is regarded to be one of the most

inportant c~nsiderations for tracing the requirements.

lo the table below we will be tracing the relation between Functional Requirements and Non Functional

Requirements.

Other Requirem ents

When the system is completely developed and submitted to the client, few sessions will be required to make
the users of the system understand about the functionality of it and some time to adapt to the system.

After those sessions, iCs required that a member from the development team should spend some time in
the 5Ystem background for an agreed time period. That time period will be used in identifying new bugs
that could not be reached in the earlier phases of the development process.
Client shou Id have a valid e-mail account in order to receive
• reservation
• e-ma1•111011'fi1cat1ons.
•

171P agl!
 HotclManagementSystcm

AfPENDIXES
DATA FLOW DIAGRAM

r---------1=-,.,--,- - - - - -
I ----~~;.i_ ------m ·,
Pavment
~Oeldll$
/,./ --.......__
,,/ "-.._
,,,,,,.-/ •~Email ·"----.....__
,.----..___ Room /-· , ._
RDoom / .,._,_~ \ ID,Pnce/ .,.
a ~ \. Select I I Book ( )
I• Available ,I Room
I
Room
Pav BIii
\ Room ,
"'----- / '~-_/ ~~.,. ' , --- .
A ,._~">~:, II Soc,kin
Data 9
Payment / ' - J P t i v . Id

I I
Ava•lab!e
Room Req.sest
,§>~ ,'
•l /
'?-~ /
,
~ldtu, c.-,,d_name
Card no
CV',/

1
I

J J#'- f ~,.. .....,,..._.,._ Amt paid

~_;QPttaci.l
" (ei--r~~~~
! ~-,., -~ooom
··,, ata
LI2.
fF o,
CD
g
-.....__~
Booking

-...___ ,
t1,::i.~~iiiJ

-...___
Payment
Data
'
''--. IO -;;;;-- ~-.. ._
._ ( Generate

~,
'-, Report

::·::~ ' -,,,,>:~p , .., __

l'J,
( Bookin\) \ :: ) Report
~I
I
\ Oeta::,;ils
'--
l
,,__
Room In o ' Room Data
·,....._
~,,
Inquiry
_ ___j_Bookmg Info_ _ _ _ _ _ _ _ _ _ __
 HotclManagernentSystem

r :RELATIONSHIP DIAGRAM
~Jff

G:!?i>
GJj .~~<2> @ 0 (3)
',r.rm~~- -
~-!~'i '• . i,,• I

0 -
1 .
UNI
0(
---

191P ag~
 HocelManagancntSystem

/ ' "JNYVT AND OUPU T SCREENSHOTS

HOTEL

-:,
az-.r; Jr . -_,...... c.:=~ ~~~ ......
• • I·& ·,iu:v1', ;:;, s It ,

HOME PAGE

,,,,,,
--
0 ---·

\\'dcome to I:S:Fl'-rl 1• 11< HEL

I:.,,)
)l(l(J

CHECK AVAILABILITY

20JP;1_,
 HotelManagementSystem
ROOMS & S ~

.... ___...........__ __, ...,.,....,..

...............,..,_
....... _
......,. : ...•!::1:".4-
~._.._
.......__._....... ......
--
•tW· : . . _ ~
~:....--. .._........ -....,
.....
- - . - . - - - - - - ·~ ~ - - - - - - 1 : a -
-•--..-....,._3 ,,__., _ __._..,_......,_

1a•s-m ~CC I
ROOM_ BOOKI NG

---<Our Service s----

Food & Resraurant Sports & Gaming

...
~-
---------~---~~
._..,_.._
~-::; .
-·-·...,....,... --"'--.__.... ,..._____ _....
':l...-.-.-...--..~r-:----iau-
----·.---.-·----- . , . _ . ~.........-·- -
,;-t ..
: a , - -.... - ~ - . . - - ~ - - - ' - -

H±ii :·5
SERVICES SECTION
 f IOf.elManagemcntSyllem

-REGISTER
-
-
- REGIST ER_SEC TION

" • • INFINITE HOTEL If; ; ' )

Login

a C:onn.-c1 "·i1h L's

\bout v• Conl3cl lJs
u.
.......... I..W.xlllllll&k kalCWat"t(trl P&. ..

-
r,i1'\af,t !"J•
.-.-.-,-,,r,1,.•: ;,\--W.,....fflO IDitl•:J.J&H ~.11~1n.-"l-16
~'d.~·SCC:.'41: 1

LOGIN_SECTION
 P.atcNmagrrnc n:S~"'ifal
1--~
---~
--
..-

-
- ROO,-f BOOKL~G _RESERVA TIO~SECT ION

.
-
- ---,--;.~n Our FJOTil---

...,. __ c::,
..__
. 9-~
Q 9

0 -
I

Q
a-
0 +

.MAP_SECTION

INPUT CODES
 Hot eI Ma nas cm cnt Svs tcm
. , t { con tain er, Row Login page
, Col , But ton , Fol'WI} fro
t { use Sta te} fro a "re act "; a •re act -bo ots tra p·;
i11p0rt { use Nav iga te} fNl
~., -ou ter -do a" : iap ort ll
axi os fro a ·ax ios "; fun ctio
nav = use Na vig ate (); n Log in() {
con st (ea ail , setE11ail] a
~su teC ' • ); . con st (pass'lfOrd, setPassw
sub 9itl og1 n • asy nc () => orct] = use 5ta te( • • );
1et { let par aas . {
,_,_.
il
.
. E!llilil• pass'lfOrd: passwoNI
}
,:do S·p ost ("lo gin ", par aas try { let res • aw ait
).ca tch (er r •> ale rt(e rr)
,on sol e.lo g(r es.d ata ); )
let { suc ces s,
da ta} =
~.d ata if (su cce ss) {
,ier t(.e ssa ge) con sol e.lo g(d ata );
tru e);
rJ'i( "/") els e {
}
1
:ert(aessage) }
} cat ch (er ror ) {
ilt!"t-(er ror )
}
stt ~il ("" )
ytPas s..ord C-· )
l
~JM I (
<>
<Co nta ine r>
<ROW>
<Col>
<hl>Login</hl>
<fonn>
<Fora.Group
,,-. Lat el> E11 ail< /Fo nn. lab con trol id= "fo nnB asic Em ail"
el> >
<Fenn.Control type=·e11ail"
,al11t={ra.iil} req uir ed name•·email" pla ceh old er=
onChange={(d) => setE ma il(d "En ter em ail"
.tar get .va lue )} />
</fora.Group>
<Form.Group className="mb
-3" controlid="formBasicpas
<fonn.Label>Password</Fonn sword">
.Label>
<form.Control type•"passw
ord" pla ceh old er= "En ter pas
~1. -.d onChange={(d) •>
setP ass wor d(d .tar get .va lue sw ord · val ue= {pa ssw ord
)
)} />
</Fon1.Group>
<Fora.Group
controlid="fonnBasicCheckbo
<fora.Check type="checkbo x">
x" label="Check me out • req
uir ed/ >
</Farra.Group>
<Button variant="primary"
onClick={submitlogin}>
Su t.it
 1-futeL\hnm!emmS,'Slcm

</Fore
</Col>
t/Ro,o
</~tainer>

) }
ex;rort :i!!-hu.lt ~ r ;

Register Page
,-:rr-. { ~ . '°'• W. ~.i:::::m., !'-or., Cir:l. ~ . N.iv} froa ·ruct-bootstrap";
1 us6'3","t, t-.;mC.C!l; ll.~ } fr:.
0
M!«t"; i-.,.:,rt { useN.ivigate } frot11 "react-
,u:-.,:r-c-.--; .utW"t a , ~ .:..:,. "ui_--s"; f.r.ctlcn ~pt~() {
Olf'St t~a. ~<-:ncz-..] • ~:.-:~{
~ : •• ·, arie:::t:.ror~:
:to'!'-"~- ••
j);
C?nl>t fwli • u-r.gr.tj') LCl!St [•-He,

,r.,.tllt) • \l!.t'S:.d" e("); CV.st (EUil,

~f~i!J • ~!.l"S-t~t:(''); c~t (:,.ss.,.....ro,
• ~'.:~-"-f("); L~t (h.nber,

;,·~,_,., • ...,A">t,•.cl'"); let sut,,,itrtglste r

C~t t,,,.,.d;iu • ,w,.

ltt c,u • J¼W.~trirglf y(Ol,Jtct, frc,o,[ntrles(fo rll!data));cons ole. log(data);

J<. F¥- • { ustrndlllf: t1•mie,

~Nil: e,a:J,
~~s,.,yd: pilSS•~<"d,)
,.v,y;a.l~e/p aril~); try

ltt rn • •••It ulos.rost("re glSter·, •> alert(trr)l

l<'Wlt. Jce(ru ,diU);
Id ( su<i•n, wssage } • ros.d,ra
lf 1,uruu) { ;;le, t(11essage)
• l"/L~&ln")) Els• (

) r•!Ch (rrrur)
ron,oh.1.1,(" trror ..·, error);
''" t (rr rOf')

••'i•,ll("")
t1l•»• tJ( .. )
' ,.,., ( •• l