Anda di halaman 1dari 17

Software Requirements

Specification
For

Hotel Management System


Version 1.0 approved

Prepared by:

Archana Pandita
Varun Panicker
Tejas Parab,
Ashish Pathak
Thadomal Shahani Engineering College

20th February, 2015

SoftwareRequirementsSpecificationforHotelManagementSystem
Page2

TableofContents
TableofContents...........................................................................................................................ii
RevisionHistory.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 DocumentConventions...................................................................................................................1
1.3 IntendedAudienceandReadingSuggestions.................................................................................1
1.4 ProductScope.................................................................................................................................1
1.5 References......................................................................................................................................1

2. OverallDescription..................................................................................................................2
2.1 ProductPerspective.........................................................................................................................2
2.2 ProductFunctions...........................................................................................................................2
2.3 UserClassesandCharacteristics.....................................................................................................2
2.4 OperatingEnvironment...................................................................................................................3
2.5 DesignandImplementationConstraints.........................................................................................3
2.6 UserDocumentation.......................................................................................................................3
2.7 AssumptionsandDependencies......................................................................................................4

3. ExternalInterfaceRequirements...........................................................................................5
3.1 UserInterfaces................................................................................................................................5
3.2 HardwareInterfaces........................................................................................................................5
3.3 SoftwareInterfaces.........................................................................................................................5
3.4 CommunicationsInterfaces.............................................................................................................5

4. SystemFeatures.......................................................................................................................6
4.1 SystemFeature1.............................................................................................................................6
4.2 SystemFeature2(andsoon)..........................................................................................................7

5. OtherNonfunctionalRequirements.......................................................................................8
5.1 PerformanceRequirements.............................................................................................................8
5.2 SafetyRequirements.......................................................................................................................8
5.3 SecurityRequirements....................................................................................................................9

SoftwareRequirementsSpecificationforHotelManagementSystem
Page3

5.4 SoftwareQualityAttributes............................................................................................................9
5.5 BusinessRules................................................................................................................................9

6. OtherRequirements..............................................................................................................10
AppendixA:Glossary..................................................................................................................10
AppendixB:AnalysisModels.....................................................................................................10
AppendixC:ToBeDeterminedList..........................................................................................10

RevisionHistory
Name

Date

ReasonForChanges

Version

SoftwareRequirementsSpecificationforHotelManagementSystem

Page1

1 Introduction
ThefollowingsubsectionsoftheSoftwareRequirementsSpecifications(SRS)documentprovidean
overviewoftheentireSRS.

1.1 Purpose
The Software Requirements Specification (SRS) will provide a detailed description of the
requirements for the Hotel Management System (HMS). This SRS will allow for a complete
understanding of what is to be expected of the HMS to be constructed. The clear
understanding of the HMS and its functionality will allow for the correct software to be
developed for the end user and will be used for the development of the future stages of the
project. This SRS will provide the foundation for the project. From this SRS, the HMS can
be designed, constructed, and finally tested.

ThisSRSwillbeusedbythesoftwareengineersconstructingtheHMSandthehotelendusers.The
softwareengineerswillusetheSRStofullyunderstandtheexpectationsofthisHMStoconstruct
theappropriatesoftware.ThehotelenduserswillbeabletousethisSRSasatesttoseeifthe
software engineers will be constructing the system to their expectations. If it is not to their
expectationstheenduserscanspecifyhowitisnottotheirlikingandthesoftwareengineerswill
changetheSRStofittheendusersneeds.

1.2 Scope
ThesoftwareproducttobeproducedisaHotelManagementSystemwhichwill

SoftwareRequirementsSpecificationforHotelManagementSystem

Page2

automatethemajorhoteloperations.ThefirstsubsystemisaReservationandBookingSystemto
keeptrackofreservationsandroomavailability.ThesecondsubsystemistheTrackingandSelling
Food System that charges the current room. The third subsystem is a General Management
ServicesandAutomatedTasksSystemwhichgeneratesreportstoauditallhoteloperationsand
allows modification of subsystem information. These three subsystems functionality will be
describedindetailinsection2OverallDescription.
There are two en users for the HMS. The end users are the hotel staff (customer service
representative) and hotel managers. Both user types can access the Reservation and Booking
SystemandtheFoodTrackingandSellingSystem. TheGeneralManagementSystemwillbe
restrictedtomanagementusers.
TheHotelManagementSystemsobjectivesistoprovideasystemtomanageahotelthathas
increasedinsizetoatotalof100rooms. Withoutautomationthemanagementofthehotelhas
becomeanunwieldytask.Theendusersdaytodayjobsofmanagingahotelwillbesimplifiedby
aconsiderableamountthroughtheautomatedsystem. Thesystemwillbeabletohandlemany
servicestotakecareofallcustomersinaquickmanner.Thesystemshouldbeuserappropriate,
easy to use, provide easy recovery of errors and have an overall end user high subjective
satisfaction.

1.3 Definitions,Acronyms,andAbbreviations.
SRS Software Requirements Specification
HMS Hotel Management System
Subjective satisfaction The overall satisfaction of the system
EndusersThepeoplewhowillbeactuallyusingthesystem

1.4 Overview
The SRS is organized into two main sections. The first is The Overall Description

SoftwareRequirementsSpecificationforHotelManagementSystem

Page3

and the second is the Specific Requirements. The Overall Description will describe the
requirementsoftheHMSfromageneralhighlevelperspective.TheSpecificRequirementssection
willdescribeindetailtherequirementsofthesystem.

2 TheOverallDescription
Describesthegeneralfactorsthataffecttheproductanditsrequirements. Thissectiondoesnot
statespecificrequirements. Insteaditprovidesabackgroundforthoserequirements,whichare
definedinsection3,andmakesthemeasiertounderstand.

2.1 ProductPerspective
TheHMSisanindependentstandalonesystem.Itistotallyselfcontained.

2.1.1HardwareInterfaces
TheHMSwillbeplacedonPCsthroughoutthehotel.

SoftwareInterfaces

AlldatabasesfortheHMSwillbeconfiguredusingOracle8i.Thesedatabasesincludehotelrooms
andcustomersinformation. Thesecanbemodifiedbytheendusers. Theroomdatabasewill
includetheroomnumbersandiftheyarevacantoroccupied.Thecustomersinformationdatabase
willcontainalltheinformationofthecustomersuchasfirstname,lastname,numberofoccupants,
assignedroom,defaultroomrate(maybechanged),phonenumber,whetherornottheroomis
guaranteed,creditcardnumber,confirmationnumber,automaticcancellationdate,expectedcheck
indateandtime,actualcheckindateandtime,expectedcheckoutdateandtime,amountowedby
customer,andabbreviatedcustomerfeedback.

SoftwareRequirementsSpecificationforHotelManagementSystem

2.2 ProductFunctions
Reservation and Booking System
Allowsfortypingincustomerinformation
Hasadefaultroomratethatisadjustable
Includesadescriptionfieldforthechangedrate
Whenacustomerchecksin,theroomnumberwillbechangedtooccupiedinthe
database
Abilitytomodifyareservation
Whennoroomsareavailableandacustomerwouldliketoextendtheirreservation
theirinformationwillbeplacedinadatabaseandwhenthereareroomsavailablethe
firstcustomeronthelistwillhavetheroom
Whenacustomerchecksouttheamountowedisdisplayed
Iftheinternalclockstatesthatisacustomerstimetohavecheckedoutandcustomer
hasnotcheckedout,addsanextranighttoamountowedandprovidesareport
Recordsthatroomisvacant
Recordspayment
Allowsforspacetowritecustomersfeedback
TrackingandSellingFoodSystem
Tracksallmealspurchased
Chargesthecurrentroomasnecessary
GeneralManagementServicesandAutomatedTasksSystem
Reports generatedtoaudithoteloccupancy,futureoccupancy,roomrevenue,and
foodrevenue
Exceptionreportslistingexceptionstothenormalcost
Allowsaddition,deletionandmodificationofinformationonroomsandrates,menu
itemsandprices,userprofiles

Page4

SoftwareRequirementsSpecificationforHotelManagementSystem

Creationofusersandassigningpasswords

2.3 UserCharacteristics
Educational level of HMS computer software Low
Experience of HMS software None
Technical Expertise Little

2.4 ApportioningofRequirements
Theaudioandvisualalertswillbedeferredbecauseoflowimportanceatthistime.

2.5 AssumptionsandDependencies
- The system is not required to save generated reports.
Creditcardpaymentsarenotincluded

Page5

SoftwareRequirementsSpecificationforHotelManagementSystem

Page6

3 SpecificRequirements
Thissectioncontainsallthesoftwarerequirementsatalevelofdetail,thatwhencombinedwiththe
systemcontextdiagram,usecases,andusecasedescriptions,issufficienttoenabledesignersto
designasystemtosatisfythoserequirements,andtesterstotestthatthesystemsatisfiesthose
requirements.

3.1 ExternalInterfaces
TheHotelManagementSystemwillusethestandardinput/outputdevicesforapersonalcomputer.
Thisincludesthefollowing:

Keyboard

Mouse

Monitor

Printer

3.1.1

UserInterfaces

TheUserInterfaceScreensaredescribedintable1.
Table 1: Hotel Management User Interface Screens

ScreenName
Login
Reservation

Description
LogintothesystemasaCSRorManager
Retrieve button, update/save reservation, cancel reservation,
modifyreservation,changereservation,adjustroomrate,accept

Checkin

paymenttype/creditcard
Modifyroomstay(e.g.,newcreditcard),checkincustomer(with
or without a reservation), adjust room rate, special requests,

Checkout
HotelPayment
RoomService/Restaurant

acceptpaymenttype/creditcard
Checkoutcustomer,generatebill
Acceptpaymentforroomandfood
Create order, modify order, view order, cancel order, generate

SoftwareRequirementsSpecificationforHotelManagementSystem

ScreenName
CustomerRecord
AdministerRooms
AdministerUser
AdministerMeals
Reports
3.1.2

Page7

Description
mealbill
Addorupdatecustomerrecords
Availabilityandrates
Create,modify,anddeleteusers;changepassword
Create,modify,anddeletemealitemsandprices
Select,view,save,anddeletereports

SoftwareInterfaces

ThesystemshallinterfacewithanOracleorAccessdatabase.

3.1.3

HardwareInterfaces

ThesystemshallrunonaMicrosoftWindowsbasedsystem.
3.1.4

CommunicationInterfaces

Thesystemshallbeastandaloneproductthatdoesnotrequireanycommunicationinterfaces.

3.2 FunctionalRequirements
Functional requirements define the fundamental actions that system must perform.
The functional requirements for the system are divided into three main categories,
Reservation/Booking,Food,andManagement.Forfurtherdetails,refertotheusecases.
1. Reservation/Booking
1.1. Thesystemshallrecordreservations.
1.2. Thesystemshallrecordthecustomersfirstname.
1.3. Thesystemshallrecordthecustomerslastname.
1.4. Thesystemshallrecordthenumberofoccupants.
1.5. Thesystemshallrecordtheroomnumber.
1.6. Thesystemshalldisplaythedefaultroomrate.
1.6.1. Thesystemshallallowthedefaultroomratetobechanged.

SoftwareRequirementsSpecificationforHotelManagementSystem

1.6.2.

Page8

The system shall require a

commenttobeentered,describingthereasonforchangingthedefaultroom
rate.
1.7. Thesystemshallrecordthecustomersphonenumber.
1.8. Thesystemshalldisplaywhetherornottheroomisguaranteed.
1.9. Thesystemshallgenerateauniqueconfirmationnumberforeachreservation.
1.10.

The system shall automatically

cancelnonguaranteedreservationsifthecustomerhasnotprovidedtheircredit
cardnumberby6:00pmonthecheckindate.
1.11. Thesystemshallrecordtheexpectedcheckindateandtime.
1.12. Thesystemshallrecordtheexpectedcheckoutdateandtime.
1.13. Thesystemshallcheckincustomers.
1.14. Thesystemshallallowreservationstobemodifiedwithouthavingtoreenterallthe
customerinforamtion.
1.15. Thesystemshallcheckoutcustomers.
1.15.1. Thesystemshalldisplaytheamountowedbythecustomer.
1.15.2. Toretrievecustomerinformationthelastnameorroomnumbershallbeused
1.15.3. Thesystemshallrecordthattheroomisempty.
1.15.4. Thesystemshallrecordthepayment.
1.15.5. Thesystemshallrecordthepaymenttype.
1.16.

The system shall charge the

customerforanextranightiftheycheckoutafter11:00a.m.
1.17.

The system shall mark

guaranteedroomsasmustpayafter6:00pmonthecheckindate.
1.18.

The system shall record

customerfeedback.
2. Food
2.1. The system shall track all meals purchased in the hotel (restaurant and room
service).
2.2. Thesystemshallrecordpaymentandpaymenttypeformeals.

SoftwareRequirementsSpecificationforHotelManagementSystem

2.3. Thesystemshallbillthecurrentroomifpaymentisnotmadeattimeofservice.
2.4. Thesystemshallacceptreservationsfortherestaurantandroomservice.
3. Management
3.1. Thesystemshalldisplaythehoteloccupancyforaspecifiedperiodoftime(days;
includingpast,present,andfuturedates).
3.2. Thesystemshalldisplayprojectedoccupancyforaperiodoftime(days).
3.3. Thesystemshalldisplayroomrevenueforaspecifiedperiodoftime(days).
3.4. Thesystemshalldisplayfoodrevenueforaspecifiedperiodoftime(days).
3.5. Thesystemshalldisplayanexceptionreport,showingwheredefaultroomandfood
priceshavebeenoverridden.
3.6. Thesystemshallallowfortheadditionofinformation,regardingrooms,rates,menu
items,prices,anduserprofiles.
3.7. Thesystemshallallowforthedeletionofinformation,regardingrooms,rates,menu
items,prices,anduserprofiles.
3.8. Thesystemshallallowforthemodificationofinformation,regardingrooms,rates,
menuitems,prices,anduserprofiles.
3.9. Thesystemshallallowmanagerstoassignuserpasswords.

Page9

SoftwareRequirementsSpecificationforHotelManagementSystem

Page10

3.3 NonfunctionalRequirements
Functionalrequirementsdefinetheneedsintermsofperformance,logicaldatabaserequirements,
design constraints, standards compliance, reliability, availability, security, maintainability, and
portability.

3.3.1

PerformanceRequirements

Performancerequirementsdefineacceptableresponsetimesforsystemfunctionality.

Theloadtimeforuserinterfacescreensshalltakenolongerthantwoseconds.

Thelogininformationshallbeverifiedwithinfiveseconds.

Queriesshallreturnresultswithinfiveseconds.

3.3.2

LogicalDatabaseRequirements

Thelogicaldatabaserequirementsincludetheretentionofthefollowingdataelements.Thislistis
notacompletelistandisdesignedasastartingpointfordevelopment.
Booking/ReservationSystem

Customerfirstname

Customerlastname

Customeraddress

Customerphonenumber

Numberofoccupants

Assignedroom

Defaultroomrate

Ratedescription

Guaranteedroom(yes/no)

Creditcardnumber

SoftwareRequirementsSpecificationforHotelManagementSystem

Confirmationnumber

Automaticcancellationdate

Expectedcheckindate

Expectedcheckintime

Actualcheckindate

Actualcheckintime

Expectedcheckoutdate

Expectedcheckouttime

Actualcheckoutdate

Actualcheckouttime

Customerfeedback

Paymentreceived(yes/no)

Paymenttype

TotalBill

Page11

FoodServices

Meal

Mealtype

Mealitem

Mealorder

Mealpayment(Billtoroom/Credit/Check/Cash)

3.3.3

DesignConstraints

TheHotelManagementSystemshallbeastandalonesystemrunninginaWindowsenvironment.
ThesystemshallbedevelopedusingJavaandanAccessorOracledatabase.

SoftwareRequirementsSpecificationforHotelManagementSystem

3.3.4

Page12

StandardsCompliance

There shall be consistency in variable names within the system. The graphical user interface
shall have a consistent look and feel.

3.3.5

Reliability

Specifythefactorsrequiredtoestablishtherequiredreliabilityofthesoftwaresystemattimeof
delivery.

3.3.6

Availability

Thesystemshallbeavailableduringnormalhoteloperatinghours.
3.3.7

Security

CustomerServiceRepresentativesandManagerswillbeabletologintotheHotelManagement
System.CustomerServiceRepresentativeswillhaveaccesstotheReservation/BookingandFood
subsystems. Managers will have access to the Management subsystem as well as the
Reservation/BookingandFoodsubsystems.Accesstothevarioussubsystemswillbeprotectedbya
userloginscreenthatrequiresausernameandpassword.

3.3.8

Maintainability

TheHotelManagementSystemisbeingdevelopedinJava.Javaisanobjectorientedprogramming
languageandshallbeeasytomaintain.

3.3.9

Portability

TheHotelManagementSystemshallruninanyMicrosoftWindowsenvironmentthatcontainsJava
RuntimeandtheMicrosoftAccessdatabase.

SoftwareRequirementsSpecificationforHotelManagementSystem

Page13

4 ChangeManagementProcess
Changestothisdocumentmaybemadeafterapprovalfromtheprojectmanagerandtheclient
approvalofficer.

5 DocumentApproval
On occasion of on-going transaction, if any hacker uses any sort of SQL-Injection attack, then data
may be altered. Also there can be cases of any sort of spoofing. For these reasons, appropriate
measures have to be used.
Thissoftwareisintendedtocommunicateovertheinternet;thereforesecurityisofmajorconcern.
Theuserwillhavetoentertheusernameandpasswordsotheprogramcanconnecttothedatabase
server.Theusernameandpasswordwillbestoredandforthisareliableencryptionalgorithmwill
beused.

6 OtherRequirements
Asystemcontextdiagramaswellasusecasesandusecasedescriptionshavebeendevelopedin
separatedocuments.

Appendix A: Glossary
SQL- Structured query languages
SRS- Software Requirement Specification
HTTPS- Hypertext Transfer Protocol Secure

Appendix B: Analysis Models


The different diagrams relating the project during the analysis phase are:

SoftwareRequirementsSpecificationforHotelManagementSystem

1. Use case Diagram


2. Class Diagram
3. Sequence Diagram
4. Activity Diagram
5. Data Flow Diagram

Page14

Anda mungkin juga menyukai