Srs Template

Software Requirements Specification
for
Hotel Management System
Version 1.0 approved
Prepared by:
No.
Name
Registration No.
01
Mirza Mussawer Baig
SP14-BSE-017
02
Saad Anjum
SP14-BSE-034
COMSATS Institute of Science and Technology, CS Department
Date Created: Monday, November 21, 2016

Copyright1999byKarlE.Wiegers.Permissionisgrantedtouse,modify,anddistributethisdocument.
SoftwareRequirementsSpecificationfor<Project>
Pageii
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..................................................................................................................2
2.5 DesignandImplementationConstraints.........................................................................................2
2.6 UserDocumentation.......................................................................................................................2
2.7 AssumptionsandDependencies.....................................................................................................3
3. ExternalInterfaceRequirements................................................................................................3
3.1 UserInterfaces................................................................................................................................3
3.2 HardwareInterfaces........................................................................................................................3
3.3 SoftwareInterfaces.........................................................................................................................3
3.4 CommunicationsInterfaces............................................................................................................3
4. SystemFeatures.........................................................................................................................4
4.1 SystemFeature1............................................................................................................................4
4.2 SystemFeature2(andsoon)..........................................................................................................4
5. OtherNonfunctionalRequirements...........................................................................................4
5.1 PerformanceRequirements.............................................................................................................4
5.2 SafetyRequirements.......................................................................................................................5
5.3 SecurityRequirements....................................................................................................................5
Pageiii
5.4 SoftwareQualityAttributes............................................................................................................5
5.5 BusinessRules................................................................................................................................5
6. OtherRequirements...................................................................................................................5
AppendixA:Glossary......................................................................................................................5
AppendixB:AnalysisModels.........................................................................................................5
AppendixC:ToBeDeterminedList...............................................................................................6
RevisionHistory
Name
Date
ReasonForChanges
Version
1.
Page1
Introduction
1.1 Purpose
This (SRS) will provide a detailed description of the requirements for the Hotel Management
System (HMS). 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 be used by the software engineers constructing the HMS and the hotel end users. The
software engineers will use the SRS to fully understand the expectations of this HMS to construct
the appropriate software. The hotel end users will be able to use this SRS as a test to see if the
software engineers will be constructing the system to their expectations.
1.2 Intended Audience and Reading Suggestions

The intended audience of this document would be owner and specific employees like Manager and
Receptionist of Hotel Gayana, and project team with the objective to refer and analyze the
information. The SRS document can be used in any case regarding the requirements of the project
and the solutions that have been taken. The document would final provide a clear idea about the
system that is building.
1.3 Product Scope

There are three types of the end users for this Hotel Management System. The first ones are the
customer who uses the system for the reservation purposes. The other end users are the admin user
and the management users who are given separate authentication to the Hotel Management System.
The first subsystem is the Home Page from which the entire site can be viewed. Recent sales, price
cuts and bonuses will be streamed here along with the news. The second subsystem is the Explore
Page2
system from which Hotel reservations, availability of rooms among other information can be
checked. The third subsystem is the Gallery from which images related to behind-the-scenes and
rooms can viewed. The fourth subsystem is Contact Us which supplies information to potential
clients who are looking to hire Hotel services. The Booking subsystem allows future booking of
rooms.
The Hotel Management Systems objectives is to provide a system to manage a hotel that has
increased in size to a total of 100 rooms. Without automation the management of the hotel has
become an unwieldy task. The end users day-to-day jobs of managing a hotel will be simplified by a
considerable amount through the automated system. The system will be able to handle many services
to take care of all customers in a quick manner. The system should be user appropriate, easy to use,
provide easy recovery of errors and have an overall end user high subjective satisfaction.
1.4 References
http://www.scribd.com/doc/27927992/HotelManagementCaseStudy
http://www.highlevelsoftware.com/features/
http://hillside.net/plop/plop99/proceedings/Fernandez2/reservanalysisPattern3.PDf
http://www.itu.dk/~slauesen/Papers/IEEEtasks.pdf
http://www.liacs.nl/assets/Bachelorscripties/200608JanneLouw.pdf
http://coverlettersandresume.com/receptionist/resumesampleofhotelreceptionist/
http://www.buzzle.com/articles/hotelreceptionistduties.html
2.
Overall Description
2.1 Product Perspective

The Hotel Management System is a new self-contained software product which will be produced by
the project team in order to overcome the problems that have occurred due to the current manual
system. The newly introduced system will provide an easy access to the system and it will contain
user friendly functions with attractive interfaces. The system will give better options for the problem
of handling large scale of physical file system, for the errors occurring in calculations and all the other
Page3
required tasks that has been specified by the client. The final outcome of this project will increase the
efficiency of almost all the tasks done at the Hotel in a much convenient manner.
2.2 Product Functions
Make Reservations
Search Rooms
Add Payment
Issue Bills
Manage Guest (Add, Update Guest)
Manage Room Details (Add, Update, Delete)
Manage Staff (Add, Update, Delete, View)
Manage Inventory (Add, Edit, Delete)
Set Rates
Retrieve Reports (Staff payment, Income)
Manage Users (Add, Update, Delete)
Taking Backups
E-mail notifications
Bulletin board
Slideshow
2.3 User Classes and Characteristics

Owner:
Hotel owner has the privilege of Monitoring and authorization of all the tasks handle by the system.
He can access every function performed by the system. Owner of the company as well as the system
can access to the administration panel which is consider the core of the system. As the main
authorized person of the company owner gets the ability to manage the other users including their
user levels and privileges. Taking backups of the system and restoring system can also be done by the
Owner. Meanwhile he will be able to take all the kinds of reports available in the system. As the
owner of the system and the company he has the power to set room rates as well. Hotel owner has
the sole right of deleting a staff member from the system database.
Manager:
Page4
Manager is responsible for managing resources available in hotel management system. Manager also
has most of the privileges mentioned above except the things regarding the payment handling. The
reason for using a Manager is to reduce the work load done by the owner that cannot be assigned to
the receptionist, as those tasks seem much responsible. The user level, Manager has the authority to
take all the reports available in the system but here also except the reports related to financial stuff,
hotel income. Manager has other abilities that receptionist, user level has. Such as, adding new staff
member to the system, Modifying them or removing them, Adding new guests to the system,
Modifying them and removing them from the system, Adding new inventory to the system,
Modifying them and removing them. Adding new room types to the system, modifying them and
removing them
Client:
Clientcanaccessthesystemonalimited,viewonlybasis.Theycannotcausechangeswithinthe
databaseandhavenoauthoritytochangedata.TheycanrequestdatasuchasContactUs
information,billingandhotelbooking.
2.4 Operating Environment

Hardware and software requirements:
Hardware:
1. Operating System Supports all known operating systems, such as Windows, Linux
2. Computer 512MB+ RAM, monitor with minimum resolution of 1024x768, keyboard, and
mouse
3. Hard Drive should be in NTFS file-system formatted with minimum 10 GB of free space
4. A Laser printer will need to be used to print these reports and notes
Software:
1. Software is designed to run on any platform above Microsoft Windows 7 (32bit).
2. Microsoft .NET Frameworks 4.0 or above.
3. Microsoft SQL Server Management Studio Express 2010.
Page5
2.5 Design and Implementation Constraints

Software development crew provides their best effort in developing the system. In order to maintain
the reliability and durability of system, some design and implementation constraints are applied.
Availability of an android app for hotel management system could make the system portable but due
to time constraint it is not possible. System will need a minimum memory of 512MB. But it is
recommended to have a memory of 1GB. When designing interfaces of system, we had the capability
of work with new tools such as Dev Express. Considering the clients budget we decided to create
those interfaces in a simple realistic manner using affordable technology.
2.6 Assumptions and Dependencies

Assumptions:
Some software used in implementing the system is with high cost and the client has agreed to afford
the amount of money needed to purchase them. Its assumed that client wont change that decision
on the next phases of the software development. Although we assume that client is using windows 7
or windows 8. Otherwise if client use an open source operating system, there is a need of changing
the SRS accordingly.
Dependencies:
The project should be completed within specified time period including Planning,
Designing, Development, Testing and Deployment.

The project should be completed within specified budget.
The Requirement Traceability Matrix (RTM) should be correlated and completed.
All the Entry and Exit criteria of all the stages should be met.
The product should be user-friendly, reliable and should maintain the industry
standards without compromising the quality.

The system architecture and design should be open and in a standard way such that
additional functionalities can be added later without much effort.

The Creative IT Solutions will provide only the software; it is the responsibility of the
client company to set up hardware for running the application.

The consultation with the Casino Group of Hotels regarding project development
comes at no cost to the project
3.
External Interface Requirements
3.1 User Interfaces
Page6
Page7
Page8
Page9
Page10
3.2 Communications Interfaces

When a specific reservation reserved at the same time an e-mail notification will be sent to both
relevant staff members e-mail account and guests account. Guest will be notified in the check-out
date. To achieve that functionality, it requires having a stable internet connection. Mostly a
broadband connection with the clients computer will provide the efficient service.
4.
System Features
1. Reservation/Booking
1.1. The system shall record reservations.
1.2. The system shall record the customers first name.
1.3. The system shall record the customers last name.
1.4. The system shall record the number of occupants.
1.5. The system shall record the room number.
1.6. The system shall display the default room rate.
1.7. The system shall record the customers phone number.
1.8. The system shall display whether or not the room is guaranteed.
1.9. The system shall generate a unique confirmation number for each reservation.
1.10. The system shall record the expected check-in date and time.
1.11. The system shall record the expected checkout date and time.
1.12. The system shall check-in customers.
1.13. The system shall allow reservations to be modified without having to reenter all the
customer information.
1.14. The system shall display the hotel occupancy for a specified period of time (days;
including past, present, and future dates).
1.15. The system shall display projected occupancy for a period of time (days).
1.16. The system shall display room revenue for a specified period of time (days).
1.17. The system shall display an exception report, showing where default room and
prices have been overridden.
1.18. The system shall allow for the addition of information, regarding rooms, rates, menu
items, prices, and user profiles.
1.19. The system shall allow for the deletion of information, regarding rooms, rates, menu
items, prices, and user profiles before final submission
1.20. The system shall allow for the modification of information, regarding rooms, rates,
items, prices, and user profiles.
1.21. The system shall allow managers to override any information that the user has
entered.
2. Main Page
2.1.1. The system shall display the main activities and modules provided
2.1.2. The system shall allow access to modules
2.1.3. The main page shall display all the necessary information regarding the hotel
2.1.4. The system will display news, recent broadcasts and any other changes that
the hotel is being subject to.
2.1.5. The system will record customer feedback.
3. Explore
3.1. The system shall permit exploration of the features being provided by Hotel
3.2. The system will supply information and images regarding the hotel
3.3. The system will provide the user with any information they may like to request about
the Hotel
Page11
Page12
4. Room
4.1. The system will allow users to check the images of various rooms.
4.2. The system will allow the user to check the prices and related information regarding
the rooms.
4.3. The user will be able to browse through the selection of rooms as represented by the
module.
4.4. The user will be able to use a slider to view these images and select from them to
attain further information about them.
5. Contact Us
5.1. The system will allow the user to enter their queries and send them to the admin.
5.2. The system will prompt user to enter information such as name, room, experience.
5.3. The system will generate an auto response regarding the sending of query, whether it
has been accepted or rejected.
5.4. The system will provide all the necessary information that the user requires to fill
their queries or contact the Hotel Management.
5.
Other Nonfunctional Requirements
5.1 Performance Requirements

Performance requirements define acceptable response times for system functionality. Although the
system is developed suiting for the least system performances, the performance of the system will
highly depend on the performance of the hardware and software components of the installing
computer. When consider about the timing relationships of the system the load time for user interface
screens shall take no longer than two seconds. It makes fast access to system functions. The log in
information shall be verified within five seconds causes efficiency of the system. Returning query
results within five seconds makes search function more accurate.
Performance requirements define acceptable response times for system functionality which includes:
The load time for user interface screens shall take no longer than two seconds.
The log in information shall be verified within five seconds.
Page13
Queries shall return results within five seconds.
5.2 Safety Requirements

There are several user levels in hotel management system, Access to the various subsystems will be
protected by a user log in screen that requires a user name and password. This gives different views
and accessible functions of user levels through the system. Maintaining backups ensure the system
database security. System can be restoring in any case of emergency.
5.3 Security Requirements

Admins will be able to log in to the Hotel Management System. The other users will have access to
to the other subsystems but only from viewing perspective or will be able to enter requests such as
booking. They will have to be verified or checked by admin before being accepted by system.
Managers will have access to the Management subsystem as well as the Reservation/Booking
subsystems. Access to the various subsystems will be protected by a user log in screen that requires a
user name and password.
6.
Other Requirements
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, its required that a member from the development team should
spend sometime in the system 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 should have a valid e-mail account in order to receive reservation e-mail notifications.
Appendix A: Glossary
None.
Page14
Use Cases
1)
Use case Name
Make Reservation
Goal
Primary Actors
Secondary Actors
Add a new reservation

Receptionist
None
Precondition
Post condition
Guest shouldnt already be exist

Hotel Guest Details updated to include current
Guest
Triggers
Main flow
Step
Action
Receptionist enter guest details
System searches for room details
System presents room types and
tariffs
Customer selects room and
confirms tariff
System records customers name
and address
receptionist confirms booking on
system
System generates confirmation
receipt
Extensions
2)
Page15
Use case Name
Check Availability
Goal
Primary Actors
Secondary Actors
To check whether a room available or not

Receptionist
None
Precondition
Post condition
Triggers
Login to the system.
Main flow
Step
Action
Display User interface
Select Availability Tab
Enter room type, duration, number

of adults and children
Extensions
System check room availability
5
4.1
relevant to each requirements

Display available room details
No room available for entered
details and display No Room
Available
Page16
3)
Use case Name
Add Guest
Goal
Primary Actors
Secondary Actors
Add a new Guest

Receptionist
None
Precondition
Post condition
Triggers
Log in to the system
Main flow
Step
Action
Receptionist selects add guest
button
System prompts to fill out guest
3
4
5
details
System validates details
Update database
Display Successful message
Extensions
Guest details are incorrect, Display
3.1
the message "Unsuccessful" and

display Add guest option.
Page17
4)
Use case Name
Add Room
Goal
Primary Actors
Secondary Actors
Add a new room to the system

Manager
None
Precondition
Post condition
Triggers
Main flow
Step
Action
Manager clicks add room button
System prompts the manager to fill
out room details

System validates new room
4
5
6
information
System creates a new room
Update database
Display successful message
Extensions
Room details are incorrect, Display
3.1
the message "Unsuccessful" and

display room management option.
5)
Page18
Use case Name
Delete room
Goal
Primary Actors
Secondary Actors
Delete a room from the system

Owner
Manager
Precondition
Post condition
Triggers
Main flow
Step
Action
User select delete room option
Display delete room option
3
4
5
6
7
User select the room

System display confirm message
User select confirmation
Update database
Extensions
If user select Yes details are
4.1
remove from the database. Else

cancel the process
6)
Use case Name
Edit room properties
Goal
Primary Actors
Secondary Actors
Alter properties such as view or type of room

Manager
Owner
Precondition
Post condition
Triggers
Main flow
Step
Action
Manager selects change room
properties
System prompts manager to select
3
4
room
Manager select the room
System display room properties
Page19
5
6
7
8
Manager edit room properties

System alters room properties
Update database
Extensions
7)
Use case Name
Guest search
Goal
Primary Actors
Secondary Actors
Modify or delete guest information

Manager
Precondition
Post condition
Triggers
Main flow
Receptionist searches for customer

Step
Action
User select search option
System displays search interface
3
4
5
User enters details

System validates user inputs
Display search results
Extensions
User inputs are invalid and prompt
4.1
Display unsuccessful message
8)
Use case Name
Create system restore point
Goal
Primary Actors
Secondary Actors
Create a system restore point to the system

Manager
None
Precondition
Post condition
Page20
Triggers
Main flow
Step
Action
User Select security option
System display security option
3
4
5
6
7
8
interface
User select system restore
User select system restore point
System validates details
Update database
Extensions
If system restores point invalid
4.1
display invalid selection user

redirected to security option.
Page21
9)
Use case Name
Set rom rate
Goal
Primary Actors
Secondary Actors
Set room rate to hotel room in system

Manager
None
Precondition
Post condition
Triggers
Main flow
Step
Action
User select room properties
Display room management window
3
4
5
6
7
8
User selects set room rates

Display enter room rate
User enter room rates
Validate details
Update database
Extensions
If room rates set previously clear
4.1
them and redirect to set room rates
Page22
10)
Use case Name
Add Property
Goal
Primary Actors
Secondary Actors
Add a new property to the system inventory

Manager
None
Precondition
Post condition
Triggers
Main flow
Step
Action
User Select inventory section
System displays inventory handling
3
4
5
6
7
section
User Select add property
User enter product details
Validate product details
Update database
Extensions
If data invalid display Invalid
4.1
selections redirect to inventory

section window
Page23
11)
Use case Name
View financial reports
Goal
Primary Actors
Secondary Actors
View a financial report for specific time

owner
None
Precondition
Post condition
Triggers
Main flow
owner clicks button view reports

Step
Action
System prompts the owner to select
two dates
Enter dates
System will display the revenue for

that specific time
Extensions
2.1
If invalid details entered Display

unsuccessful message and reenter
interface.
Page24
12)
Use case Name
Delete Guest
Goal
Primary Actors
Secondary Actors
Delete a Guest
Receptionist
None
Precondition
Post condition
Triggers

A new guest is added to the system
Receptionist clicks button Delete guest
Main flow
Step
Action
User interface displayed
Select delete Guest option
3
4
5
6
Enter guest details

Valid guest details
System display guest details
System confirms deletion of
selected guest
Update database
Extensions
4.1

not found message and redirect
5.1
to main interface
Database is not updated, Display
the message "Unsuccessful"
Page25
13)
Use case Name
Change Guest information
Goal
Alter properties such as telephone number or
Primary Actors
Secondary Actors
email of guest
Receptionist
None
Precondition
Post condition
Triggers

Guest details edited
Receptionist clicks button Edit guest
Main flow
Step
Action
User interface displayed
Select Edit Guest option
3
4
5
6
7
8
9
Enter guest details

Valid guest details
System displays guest properties
System alters the guest properties
Update database
Display Successful message
Database updated
Extensions
4.1

unsuccessful message and
5.1
redirect to main interface

Database is not updated, Display
the message "Unsuccessful"
Page26
14)
Use Case
Take Backup
Goal
Take a backup of the system
Primary Actor
Owner
Secondary Actor
Name
Pre-condition
User should login to the system
Main Flow
Step
Action
Display user interface
Select backup option
Display backup interface
Select create backup option
Create backup
Creating backup process is not

successful, display
Unsuccessful message.
Add new Hotel Room
Page27
Edit
Hotel
Room
Make
Reservation
Page28
Take Backup
Page29
Search
Page30
Delete a user
Page31
Add Payment
Page32
Add Guest
Page33
Add Staff
Page34
Add property
Page35
Delete user
Page36
Page37
Set room rate
Page38

Srs Template

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Srs Template

Diunggah oleh

Hak Cipta:

Format Tersedia

Software Requirements Specification

Mirza Mussawer Baig

COMSATS Institute of Science and Technology, CS Department

Date Created: Monday, November 21, 2016

1.2 Intended Audience and Reading Suggestions

1.3 Product Scope

2.1 Product Perspective

2.2 Product Functions

2.3 User Classes and Characteristics

2.4 Operating Environment

2.5 Design and Implementation Constraints

2.6 Assumptions and Dependencies

Designing, Development, Testing and Deployment.

standards without compromising the quality.

additional functionalities can be added later without much effort.

client company to set up hardware for running the application.

External Interface Requirements

3.1 User Interfaces

3.2 Communications Interfaces

Other Nonfunctional Requirements

5.1 Performance Requirements

The log in information shall be verified within five seconds.

Queries shall return results within five seconds.

5.2 Safety Requirements

5.3 Security Requirements

Add a new reservation

Guest shouldnt already be exist

Receptionist enter guest details

System searches for room details

System presents room types and

Use case Name

To check whether a room available or not

Login to the system.

Display User interface

Select Availability Tab

Enter room type, duration, number

System check room availability

relevant to each requirements

Add a new Guest

Log in to the system

Receptionist selects add guest

the message "Unsuccessful" and

Add a new room to the system

Log in to the system

Manager clicks add room button

System prompts the manager to fill

out room details

the message "Unsuccessful" and

Use case Name

Delete a room from the system

Log in to the system

User select delete room option

Display delete room option

User select the room

remove from the database. Else

Edit room properties

Alter properties such as view or type of room

Log in to the system

Manager selects change room

Manager edit room properties

Modify or delete guest information

Log in to the system

Receptionist searches for customer

User select search option