Software Requirement Specification (SRS)

Hotel Management System

Version: SRS 1.0

Printing Date: 01/12/2008

Team Number: # 03

Location of electronic version of file

http://student.atilim.edu.tr/~sproject0803/index.php?id=docs

University: ATILIM UNIVERSITY

Department: Computer Engineering

Supervisor: Assoc. Prof. Dr. Mohammad Rehan

1
Revision Page

Overview:
SRS document is a description of the expected software features, constraints,

interfaces and other attributes. Aim of this document is to document the agreed

requirements with the project supervisor; to provide the basis for design; to provide

the basis for system test.

Informatin:
Target Audience: Hotels and Property Managers

Supervisor: Assoc. Prof. Dr. Mohammad Rehan

Team Member:

Student Number Surname Name E-Mail

030302007 AKYILDIZ Mehmet Olcay mehmetolcay@hotmail.com

030302020 KARAGÖZ Abdullah Tarık atk_999@hotmail.com

Version Control History:

Version Author Description of Version Date

v1.0 Mehmet Olcay AKYILDIZ 1st draft 1.12.2008

2
Contents

Revision Page........................................................................................................................................... 2
Overview: ............................................................................................................................................ 2
Informatin:........................................................................................................................................... 2
Target Audience: ............................................................................................................................. 2
Supervisor:....................................................................................................................................... 2
Team Member: ................................................................................................................................ 2
Version Control History: .................................................................................................................. 2
Contents .................................................................................................................................................. 3
1. INTRODUCTION ........................................................................................................................... 5
1.1 Purpose .................................................................................................................................... 5
1.2 Scope ....................................................................................................................................... 5
1.3 Product Overview .................................................................................................................... 6
1.4 Acronyms ................................................................................................................................ 7
2. Overall Description ............................................................................................................................. 8
2.1 Product Perspective ....................................................................................................................... 8
2.1.1 System Interfaces ................................................................................................................... 8
2.1.2 User Interfaces ........................................................................................................................ 8
2.1.3 Hardware Interfaces ............................................................................................................... 8
2.1.4 Software Interfaces ................................................................................................................. 8
2.1.5 Communication Interfaces...................................................................................................... 9
2.1.6 Store System ........................................................................................................................... 9
2.1.7 Operations .............................................................................................................................. 9
2.2 Product Functions .......................................................................................................................... 9
2.2.1 User Authentication ................................................................................................................ 9
2.2.2 Search Functions .................................................................................................................... 9
2.2.3 Administrator Authorization ................................................................................................ 10
2.2.4 Online Reservation Function ................................................................................................ 10
2.2.5 Add Functions ...................................................................................................................... 10
2.3 User Characteristics..................................................................................................................... 10
2.3.1 Customers ............................................................................................................................. 10

3
 2.3.2 Administrators ...................................................................................................................... 10
2.3.3 Staff ...................................................................................................................................... 11
2.4 Assumptions and Dependencies .................................................................................................. 11
2.4.1 Network ................................................................................................................................ 11
2.4.2 Storage system...................................................................................................................... 11
3. SPECIFIC REQUIREMENTS .......................................................................................................... 12
3.1 EXTERNAL INTERFACE REQUIREMENT ....................................................................... 12
3.1.1 User Interface Requirements ................................................................................................ 12
3.1.2 Hardware Interface Requirements ........................................................................................ 13
3.1.3 Software Interface Requirements ......................................................................................... 13
3.1.4 Communication Protocol Requirements............................................................................... 14
3.2 Software Product Features........................................................................................................... 15
3.2.1 Functional Requirements ...................................................................................................... 15
3.2.2 Non-Functional Requirements.............................................................................................. 15
3.3 Software System Attributes ......................................................................................................... 16
3.3.1 Reliability: ............................................................................................................................ 16
3.3.2 Availability: .......................................................................................................................... 16
3.3.3 Security:................................................................................................................................ 16
3.3.4 Maintainability: .................................................................................................................... 17
3.3.5 Performance: ........................................................................................................................ 17
3.3.6 Reparability: ......................................................................................................................... 17
3.4 Database Requirements ............................................................................................................... 18
4. ADDITIONAL MATERIAL ............................................................................................................ 19
4.1 REFERENCES ............................................................................................................................ 19
4.1.1 Websites: .............................................................................................................................. 19
4.2.1 Documents: ........................................................................................................................... 19
5. Appendix............................................................................................................................................ 20
5.1 Appendix-1 (Network Schema) ................................................................................................... 20
5.2 Appandex 2 (Database) ............................................................................................................... 20

4
1. INTRODUCTION

1.1 Purpose

The purpose of this Software Requirement Specification (SRS) is to help the our

project. It is provided with some requirements which is used in Hotel Management

System. All parts; design, coding and testing will be prepared with helping of SRS.

This document will be checked by group member’s supervisor and it will corrected by

members if supervisor orders.

1.2 Scope

The scope of this project is to develop a Hotel Management System is following the

costumer’s online reservation, meal cost and their other spending which is based on

online web system. Customers can reserve rooms, conference hall, meeting salon by

using the Hotel Management System and they can pay their cost by using credit card

at same time.

The scope of Software Requirements Specification is to present all requirements about

Hotel management system. But there is no detailed information about which

methodology is chosen.

Hotel Management System (HMS) will be ensured some benefits:

 Online Reservations

 Following the customers spending

 Collecting data about customer deportments and staff.

 Online paying technology.

 Announcements about hotel can be followed by our system

 Hotel personnel can connect each other by using online messaging system

5
1.3 Product Overview

Our project is the hotel management system. In this project, our aim is to serve

customers with an automated system. One of the ways is that customers choose their

preferred choices and rooms etc. to their own needs. So they can get the discount they

are looking for without additional work.

In the final part of the project, steps of product are finished by us. Product is made up

of associated documentation and computer programs. SPMP, SRS, SDD and STD are

the steps of the associated documentation. In these steps, we introduce characteristics

of project like defining requirements, making prototype for customers and scheduling

a project. Secondly, our software is a web application. Internet programming is mostly

used in our project. Customers must use internet for reaching our system. When we

look at computer programs, they include databases, collection of programs which are

related to finding optimal paths with algorithms, graphical user interface for visual

projection. There are more than five databases. It stores some information about

customers, staff, room, department, log, process and we have more databases which

are related to storing other information.

Finally, we explain our product characteristics. Our software product is a web-based

application. Internet programming, database and algorithm are used in the product.

6
1.4 Acronyms

JSP: Java Server Pages

HMS: Hotel Management System

DBMS: Data Base Management System

HW: Hardware

ID: Identification

IEEE: Institute of Electrical and Electronics Engineers

SRS: Software Requirements Specification

SW: Software

OS: Operating System

SWE: Software Engineering

7
2. Overall Description
2.1 Product Perspective
2.1.1 System Interfaces
Hotel Management System (HMS) is an web based application so it is not depend on

system interface. It is depends on the browser and its works all OS like Linux,

Microsoft Windows, MacOS, Mobil Device ets.

2.1.2 User Interfaces

We have web users interfaces.

Web users will be categorized as;

Administrator Interfaces

Staff Interfaces

Customers Interfaces

2.1.2.1 Web Users Interfaces:

2.1.2.1.1 Interfaces for Administrator

List of views are listed as bellow

2.1.2.1.1.1 Account View

In this view use will add, remove new staff in the system. In administrator view,

administrator will confirm newly added department. Administrator will be able to

access all information about hotel staff, customers and managed them.

2.1.3 Hardware Interfaces

Our hardware is desing by networking. Therefore database server, application server

and more than one client is included.(check appendix networking)

2.1.4 Software Interfaces

Software requirements are an idea for developments part of Java Server Page(jsp) and

8
Servlet. We need Apache-TomCat Server and My-SQL. In next part, detailed

explanation can be seen in the next SRS report

2.1.5 Communication Interfaces

Communication is via internet and local area network(LAN) and wireless local area

network(W-LAN).

2.1.6 Store System

 We need big server to hold more than thousands of peoples, information and

process data.

 We need little space for application server

2.1.7 Operations
Buck-up operation month by month

2.2 Product Functions

2.2.1 User Authentication
 Registration

 Approval

 Login

 Change Password

 Determine Authorization Level

 Change User Information

2.2.2 Search Functions

 Search customer

 Search staff

 Search phone number in hotel rooms

9
2.2.3 Administrator Authorization
Creating Administrator and staff account

Login

Remove account

2.2.4 Online Reservation Function

 Make a reservation

 Pay reservation cost

2.2.5 Add Functions

Add customer

Add staff

Add new rooms(standard, king, suit conference hall, etc )

Add new department (security, vale, etc.)

Add new service (barber, café, disco etc. )

2.3 User Characteristics

2.3.1 Customers
Customers can make reservation by using internet page. And it can be done without

account needed

2.3.2 Administrators

Administrators can manage all the system and they have all the opportunities about the

system. They can add new staff department and new user about hotel.

10
2.3.3 Staff

Staff add new customers and knowledge about the customers.

2.4 Assumptions and Dependencies

2.4.1 Network

2.4.2 Storage system

11
3. SPECIFIC REQUIREMENTS
3.1 EXTERNAL INTERFACE REQUIREMENT

3.1.1 User Interface Requirements

User interface is used to provide communication between users and database system.

Our product should be the communication between them. Because, Hotel Management

System is a web-based system and it should get input from users for processing.

Firstly the system should ask to users about which room they want to book or when

they want to check in .Users will enter their desired place, date period. The system

gets these inputs by using user interface. After that, the system will give appropriate

output for users via user interface. Finally users will see the information about their

choices at their screen according to their selected option for a final approval.

User interface elements should be easy to understand. Part of user interface should be

well-organized on screen and the parts should be concatenated right. When users look

at the interface, they understand which pane is used for which purpose. Each task of an

interface should be specified clearly and users should use them correctly. For example,

when users press to any button on interface, they should know which operations are

done by pressing this button.

The interface actions and elements should be consistent. When users press any button,

required actions should be done by the system.

The screen layout and color of the user interface should be appealing. When users look

at the screen, it will have a nice vision. Colors will be selected clearly, so it won’t

cause tired eyes.

12
3.1.2 Hardware Interface Requirements

Hotel management System is a web-based project. So any personal computer, which

has an web browser, local area network and internet connection, is enough to use this

system.

3.1.3 Software Interface Requirements

In Hotel Management System, users will use application program via the internet user

interface program. When database management system access is required, the system

establishes a connection to the database management system, once the connection is

created; the client program can communicate with the database management system. A

standard called Open Database Connectivity (ODBC) provides an application

programming interface (API), which allows client-side programs to call database

management system, as long as PC has the necessary software installed. Most database

management system vendors provide ODBC drivers for their systems. A user can

actually connect to several database management system and send query and

transaction requests using the Open Database Connectivity (ODBC) API, which are

then processed at the server site. Any query results are sent back to user, which can

process or display the result as needed.

MY-SQL

Eclipse IDE ( jsp )

Notepad++

TomCat

13
3.1.4 Communication Protocol Requirements

Hypertext Transfer Protocol (HTTP) shall be used to provide a communication

between system and users. Because, Hotel Management System is a web-based system

which should be reached on World Wide Web by users. Hypertext Transfer Protocol

(HTTP) is a communications protocol which is used to transfer or convey information

on intranets and the World Wide Web.

Its original purpose was to provide a way to publish and retrieve hypertext pages.

Development of HTTP was coordinated by the W3C (World Wide Web Consortium)

and the IETF (Internet Engineering Task Force), culminating in the publication of a

series of RFCs, most notably RFC 2616 (June 1999), which defines HTTP/1.1, the

version of HTTP in common use. HTTP is a request/response protocol between a

client and a server. The client making an HTTP request, such as a web browser, is

referred to as the user agent.

The responding server, which stores or creates resources such as HTML files and

images, is called the origin server. In between the user agent and origin server may be

several intermediaries, such as proxies, gateways, and tunnels. HTTP is not

constrained to using TCP/IP and its supporting layers, although this is its most popular

application on the Internet. Indeed HTTP can be implemented on top of any other

protocol on the Internet, or on other networks. HTTP only presumes a reliable

transport; any protocol that provides such guarantees can be used. Typically, an HTTP

client initiates a request by establishing a Transmission Control Protocol (TCP)

connection to a particular port on a host (port 80 by default; see List of TCP and UDP

14
port numbers). An HTTP server listening on that port waits for the client to send a

request message.

TCP/IP

HTTP protocol ( port no: 8080)

3.2 Software Product Features

3.2.1 Functional Requirements

• the system shall be enabling for users, when they want to enter the system.

• The system shall provide a registration system.

• When users take an action on the system, they choose room and check-in date.

• The system shall ask users to which time interval is suitable.

• After all operations are finished, system communicates with database to ask if

the rooms and dates are available.

• The system shall communicate with banking systems. Because of final process,

users need banking system to pay for pre-booking.

3.2.2 Non-Functional Requirements

The system should be web-based system. Users should use the system via internet.

Thus, when they want to book for a room, they only need to have the internet.

15
Each user should have a user account. The system should ask the username and

password to users. It doesn’t permit to unregistered access for reservation.

3.3 Software System Attributes

3.3.1 Reliability:

When user wants to call the system over a given period of time, the system should

correctly deliver services as expected by the user. The reliability of the system shall be

good if it delivers services as specified. Otherwise, reliability is bad and it shall

produce unexpected output. So, program should be changed according to right

situation.

3.3.2 Availability:
When the system has any request at any given time, system should be available, it

should be up and running and able to deliver useful service at this time. The

availability of the system shall be good if it delivers services when it is requested.

Otherwise, if requests are not responded at any given time then it implies bad

availability.

3.3.3 Security:
The system should resist accidental or deliberate intrusions, when users operate on the

system. If the system should not resist accidental or deliberate intrusions, then

important data – such as credit card number, id number, username, etc. – which

belongs to user, shall be stolen by hacker. Thus, security of the system shall be low

and trust of users shall be ruined. So, security of the system is very important for

users.

16
3.3.4 Maintainability:
When the system is used, new requirements may emerge. When these requirements are

emerged, the system should be changeable to accommodate these requirements for

maintaining the usefulness of the system. If the system is not maintainable, then the

system cannot be modified for new requirements. In this situation, a new system

should be developed for provide new requirements. The maintainability is important

for avoiding from cost.

3.3.5 Performance:
The system should use the minimum part of memory. The processes of the system

should use the processor most efficiently. User should finish operation in the least time

interval.

3.3.6 Reparability:
When the system is used, system failures are inevitable. The disruption caused by

failure can be minimized if the system can be repaired quickly. So, the system should

be possible to find the problem, access the component that has failed and make

changes to fix that component. When the system has a repair, the source code should

be modified.

17
3.4 Database Requirements

In our project, there are more than five databases. One of them keeps staff

information. Information is user name, surname, country, city, password, e-mail

address, address and etc... It is necessary to keeping users information in the database.

Another type keeps company’s information. Information is company name, how many

customers are checked in, what is their information, much owned to the agencies etc…

Finally, we have to create databases. If they are invalid, system can’t work properly.

We can only store information in the databases.

18
4. ADDITIONAL MATERIAL

4.1 REFERENCES
4.1.1 Websites:

http://www.wikipedia.org/

http://www.ieee.com/

http://www.atilim.edu.tr/~fcserce/compe491/resources/IEEE-830.pdf

4.2.1 Documents:
Software Engineering Seventh Edition Ian Summerville

19
5. Appendix

5.1 Appendix-1 (Network Schema)

5.2 Appandex-2 (Database)

20