SRS HMS

SRS-2009-04-V3 FSKKP

SRS-2009-04-V3 i

SOFTWARE REQUIREMENT SPECIFICATION (SRS)Hotel Management System (HMS)

2008

Tenebrous Sdn BhdTo be submitted to the Software Planning & Requirement Workshop

Bachelor of Computer Science (Software Engineering)

Ong Kah Siang CB07053

Dayang Zaimah Binti Mawi CB07037

Norizan Binti Syahann CB07010

Nur ‘Aqilah Bte Ramli CB07043

Mohd. Syafiq Bin Bachok CB08013

SOFTWARE REQUIREMENT SPECIFICATION (SRS) FSKKP

DOCUMENT APPROVAL

Name Date

Verified by:

_______________________

Project Leader

Ong Kah Siang

Authenticated by:

_______________________

Project Managers

Mdm Fauziah binti Zainuddin

Approved by:

_______________________

Client

LA Hotel

Software : Microsoft Word Version 2003

Archiving Place : HMS\Management\SDP\HMS_SRS.doc

Copies Available : CD-ROM

SRS-2009-04-V3 ii


TABLE OF CONTENTSDOCUMENT APPROVAL..................................................................................................................ii

TABLE OF CONTENTS.....................................................................................................................iii

LIST OF FIGURES............................................................................................................................iv

LIST OF TABLES...............................................................................................................................v

LIST OF APPENDIXES......................................................................................................................vi

1. INTRODUCTION......................................................................................................................1

1.1 PURPOSE 1

1.2 PROBLEM STATEMENT.........................................................................................................1

1.3 REFERENCES.........................................................................................................................2

1.4 DOCUMENT OVERVIEW........................................................................................................2

2. OVERALL DESCRIPTION...........................................................................................................4

2.1.1 PRODUCT PERSPECTIVE.........................................................................................................4

2.1.2 SYSTEM INTERFACES...........................................................................................................6

2.1.3 USER INTERFACES................................................................................................................8

2.1.4 SOFTWARE INTERFACES........................................................................................................8

2.2 PRODUCT FUNCTIONS..........................................................................................................9

2.3 USER CHARACTERISTICS.....................................................................................................10

2.4 CONSTRAINTS.....................................................................................................................10

2.5 ASSUMPTIONS AND DEPENDENCIES..................................................................................11

3. SPECIFIC REQUIREMENTS......................................................................................................12

3.1 EXTERNAL INTERFACE REQUIREMENTS..............................................................................12

3.1.1 USER INTERFACES................................................................................................................12

3.2 SOFTWARE PRODUCT FEATURES........................................................................................15

3.2.1 USE CASE 1.........................................................................................................................24

3.3 PERFORMANCE REQUIREMENTS........................................................................................29

3.4 REQUIREMENT TRACEABILITY ............................................................................................ 30

4. DEFINITIONS, ACRONYMS AND ABBREVIATION ..................................................................... 33

SRS-2009-04-V3 iii


LIST OF FIGURES

Figure 2.1: Sequence Diagram for Hotel Management System........................................................5

Figure 2.2: Function that Available in HMS.....................................................................................9

SRS-2009-04-V3 iv


LIST OF TABLES

Table 3.1: Software Interface........................................................................................................14

Table 3.2: Requirement Traceability.............................................................................................30

SRS-2009-04-V3 v


LIST OF APPENDIXES

Appendix A: Sequence Diagram....................................................................................................35

Appendix B: Graphical User Interface...........................................................................................45

SRS-2009-04-V3 vi

SRS-2009-04-V3 FSKKP

1. INTRODUCTION

1.1 PURPOSE

The purpose of this project is to specify function and requirement for “Hotel management

System” (HMS). It will details the description and features of the system, the interfaces of

the system, what the system will do, the constraints under which it must operate and how

the system will react to external stimuli. This document is intended for both the

stakeholders and the developers and will provide a common point of reference for system

expectations. During completion, the document will act as a binding contract between

developer and users which will provide a common point of reference for system expectation.

1.2 PROBLEM STATEMENT

The need for the system arises as the result of this set of problems faced by users in the

current manual way of performing the related task associated with users such as:

i. User need to reserve by manual and this system is not systematic

ii. User cannot check their reservation status

iii. The manual system services is not efficient in reservation room

iv. User do not know the information about the room by the hotel so they cannot make

the reserve based on their choice

1.3 REFERENCES This section lists any references used in producing this document.

i. Addison Wesley, “Software Engineering” eight edition, Ian Sommerville, England 2001.

ii. IEEE STD 830-1998, “IEEE Recommended Practice for Software Requirement Specification”,

1998 edition, IEEE, 1998.

iii. Description about how to write Software Requirement Specification (SRS).

iv. http://microtoolsinc.com/Howsrs.php, Date of retrieve 20 September 2007

v. http://sparc.airtime.co.uk/users/wysywig/srsdid.htm . Date of retrieve 20 September 2007

vi. http://home.gna.org/gp2xmb/srs.html Date of retrieve 22 September, 2007

vii. http://www.care2x.org/billing_generic/srscare.html Date of retrieve 06 October , 2007

SRS-2009-04-V3 1

http://home.gna.org/gp2xmb/srs.html

http://sparc.airtime.co.uk/users/wysywig/srsdid.htm

http://microtoolsinc.com/Howsrs.php,%20%20Date


1.4 DOCUMENT OVERVIEW

This document outline is based on the IEEE Standard 830-1998 for Software Requirement Specification (SRS).The explanations of the SRS are divided into 4 chapters:-

Chapter 1 Introduction

This Section is described about the purpose of this document. Generally, in

this chapter was state the problems that occur in the current manual way

performing the related task associated with Hotel Management System.

Also indicates in this chapter are the references for this document and

document overview for SRS.

Chapter 2 Overall Descriptions

This chapter is related with overall description of product functions, user

characteristic. This chapter also states the constraints requirement and the

assumption and dependencies of the system.

Chapter 3 Specific Requirements

Chapter Specific Requirement is addition from the Chapter 2. In this chapter

the requirement of the system will be state clearly and more details. Each

module description was accompanied with the sequence diagram. In this

chapter describe the external interface requirements, software product

features, performance requirements and requirements traceability.

Chapter 4 Definitions and Acronyms

In this chapter, the definition and acronyms are listed. This chapter can help

user to know the definitions and acronyms which are used in developing

HMS.

SRS-2009-04-V3 2


2. Overall Description

2.1 Overall Description

This section of the SRS should describe the general factors that affect the product and its

requirements. This section does not state specific requirements. Instead, it provides a

background for those requirements, which are defined in detail in Section 3 of the SRS, and

makes them easier to understand.

2.1.1 Product Perspective

HMS is a web based system which can hold the information of the hotel computerized data

storage which can be quick review and referred by user. The system will interact with

database through Microsoft SQL Server 2005.

There are 2 kinds of users, which are the employee and manager. All of them enter the

system through the stand alone. The application should allow those two kinds of users to

register new employee, apply for room reservation, apply check in/out and arrange

customer payment. But certain function cannot use by employee such as generate report.

Just manager can use generate report function.

SRS-2009-04-V3 3


: Employee : Manager :Hotel Management System

1. Registration New Employee

2. Room Reservation

3. Check In/Out Customer

4.Generate Report

Figure 2.1 Sequence Diagram for Hotel Management System

SRS-2009-04-V3 4


2.1.2 System Interfaces

Receptionist to Register

1. A newly hired employee should register to have his/her own username and Password to Login in order to execute application and this must be done by employee supervisor.

2. Employee supervisor firstly need to Login by entering ID and Password to start execute application.

3. Users fulfills register form.

4. Create new usename and Password.

Receptionist to Reservation

1. Firstly, user insert ID and Password to Login in order to execute application.

2. Enter Customer Identification Number and click Search button. This button functions to look in database either this Customer data already in server and will display the data of this customer reservation. If not, user needs to enter Customer name for new record.

3. Enter the reservation date which is the currently date, arrival date, select room type, number of rooms and day of ends for reservation.

4. If there were any available room, user may proceed and make confirmation. If not, user can either cancel to reserve or change date, time or type of room.

5. User can reset to re-enter new data.

Receptionist to view Room Availability (Room Information)1. Firstly, user insert ID and Password to Login in order to execute application.

If in beginning user already Login no need to insert ID and Password.

2. User will search for room’s availability from Room Information menu.

3. User can select type of room, season and date which are available.

4. Once user click on Submit button, system will display the room’s rate and number of that room available.

Receptionist to Check In (Stay Information)

1. Firstly, user insert ID and Password to Login in order to execute application. If in beginning user already Login no need to insert ID and Password.

2. Insert ID of hotel’s customer to check whether he/she made any reservation.

3. If not, user fulfills check in forms then select room available

SRS-2009-04-V3 5


Receptionist to Check Out (Payment)

1. Firstly, user insert ID and Password to Login in order to execute application. If in beginning user already Login no need to insert ID and Password.

2. Choose Payment menu.

3. Then insert Customer Identification Number and click OK.

4. Ensure all data display correct.

5. For customer’s cash payment, user need to insert the amount and click Calculate to confirm the change due and total of payment.

6. Lastly print out the form as customer’s receipt.

Manager to Generate Report

1. Firstly, user inserts ID and Password to Login in order to execute application.

2. Choose to Generate Report.

3. User insert the date start and date end for any duration he/she want and click View to view the report result base on these duration.

4. Lastly, system will display the report based on date duration inserted by user previously and print out as hardcopy record.

2.1.3 User Interfaces

This should specify the following:

1. The different group of user will get different sets of interface since each of the users has different level of usage and ability to the system.

2.1.4 Software Interfaces

This sub-section will be explained detailed in sub-section 3.1.3

SRS-2009-04-V3 6


2.2 PRODUCT FUNCTION

Figure 2.2 Function that Available in HMS

The process of HMS started by a new receptionist to have own account ID and Password as they need to login into the system in order to proceed execute applications. To have their own account, the supervisors who are responsible to register these new employees into the system and all the information allocate into database. By doing that, a newly receptionist has their own account to log in according to their shift.

The system allows the hotel’s customer to reserve room/s before their arrival date under reservation service.This will be done by receptionist on shift to key in any informations needed into the system for the reservation. Before confirming these reservation ,the receptionist need to check for the room availability from time to time at Room Information by retrieving the information of the room availability which provided by system service.

Besides, the receptionist used HMS for check-in and check-out customer according to the preference of the customer and the system able to stay informations of customer. Then, this is no doubt that the system also included the calculation system to handle all the payment whenever receptionist handling customer payment.

For manager, he/ she can easily get report for the hotel operations through the system and print out as hardcopy record.

SRS-2009-04-V3 7


2.3 USER CHARACTERISTICS

The skill needed to use this application is minimal.

Users of this system must be fairly IT literate.

Have a basic knowledge of using GUI.

Proficient with the use of a keyboard and mouse in order to interact with the GUI.

Familiar with internet browser.

Trained on how to work with this system.

2.4 CONSTRAINTS

This subsection of the SRS provides a general description of any other items that will limit

the developer’s options. The sub-section below will explain briefly the constraints that need

to consider when the development of HMS is done.

2.4.1 Manager Constraints

1. Only manager can register new employee

2. Report can only generated at reservation counter

3. Reports that provide by the system only display the statistic of customer and type of room preferable according to season.

2.4.2 Receptionist constraints

1. New employee only can be registered by manager or supervisor

2. Only employee on duty that can take reservation from customer

3. Employee only can login to HMS during their shift time because once he or she login during their shift, it could be as record for attendance at their workplace

SRS-2009-04-V3 8


2.5 ASSUMPTIONS AND DEPENDENCIES

The systems will be run on web based HMS. HMS runs on local database. For the user it is assumed that all the users are familiar with computer.

During the running time, the performance of the application shall be better if no other application is running at the same time. So, it depends on the memory of ram for the performance of the application.

SRS-2009-04-V3 9


3. SPECIFIC REQUIREMENTS

3.1 EXTERNAL INTERFACE REQUIREMENTS

3.1.1 User Interfaces

This section will show and explain about the interface which will be used by the User (Hotel’s Manager and Receptionist) of the system. The interface consists of Log In interface, Reservation interface, Stay Information (Check in) interface, Payment (Check Out) interface and Report Generation interface.

3.1.1.1 Receptionist’s interface

The interfaces that available for receptionist are log in interface, reservation, stay information, room information and payment. The receptionist is required to log in before proceed to other interface as mentioned above. Receptionist shall able to search, edit, update and delete certain information like reservation information of customer and edit the staying information of a particular customer.

3.1.1.2 Manager’s interface

For manager interface, the manager able to access to all interface which available in the application. Those interfaces are login interface, reservation interface, stay information interface, payment interface and report generation interface. Only manager able to access in report generation interface because the account and statistic of hotel’s business is considered as private and confidential to the hotel. So, receptionist is not allowed to access the report generation interface.

3.1.2 Hardware Interface

Not Applicable.

SRS-2009-04-V3 10


3.1.3 Software Interface

Table 3.1 Software Interface

Product Function

Windows XP Professional, version 2000, Service Pack 2

Operating system that use throughout the process of developing system as well as the preparation of document and presentation

Microsoft SQL Server 2005 Design and develop database which work as database platform

3.2 SOFTWARE PRODUCT FEATURES

3.2.1 Use Case Login and Registration [SRS-REQ-V01-01]

3.2.1.1 Purpose

This Registration use case is initiated by the receptionist. It provides the capability to register newly hired receptionist and record the information of the receptionist into database before they can login into the system.

3.2.1.2 Role

Event is driven by the receptionist.

3.2.1.3 Pre-Condition (s)

1. The application is running.

3.2.1.4 Base Scenario

1. This use case begins when new receptionist make a new account on Registration form button and insert all information needed in registration form together by creating new Username and

SRS-2009-04-V3 11


PASSWORD .( R-1: Registration Only for Employee) [SRS-REQ-V01-01-01]

2. Starts to proceed to Main Menu, employee need to login first by entering Username and Password on Login column to open Main Menu which under his or her account.( A-1: Login Directly ) [SRS-REQ-V01-01-02] ( E-1: Invalid Username and Password) [SRS-REQ-V01-01-03]

3. HMS displays the Main Menu.

4. The use case ends.

3.2.1.5 Alternative Scenario

A-1: Login Directly

1. The employee inserts Username and Password on Login form. 2. Click ‘OK’ button.3. Main menu will be displayed.

3.2.1.6 Exception Scenario

E-1: Invalid ID number and Password

1. The system will prompt a message which stated that “Invalid Username or Password. Re-enter Username and Password.”

2. The system will wait for a valid Username and Password.3. The use case continues.

3.2.1.7 Post Condition (s)

Main menu under employee’s username shall be displayed

3.2.1.8 Rules (s)

R-1: Registration Only for newly hired receptionist

Registration to get a new account for newly hired receptionist.

3.2.1.9 Constraint (s)

C-1: Login during Shift

SRS-2009-04-V3 12


Employee login to HMS during their shift time because once he or she login during their shift, it could be as record for attendance at their workplace.

C-2: Login to Use Own Account

Receptionist able to access into the system using their own account.

3.2.1.10 Sequence Diagram

Please refer to Appendix AA1, A2 and A3

3.2.1.11 GUI

Please Refer Appendix BB1 and B2

3.2.2 Use Case Customer Reservation [SRS-REQ-V01-02]

3.2.2.1 Purpose

This is use case initiate by receptionist. It provides capability to make a reservation for a customer and check reservation that has been made by the customer.

3.2.2.2 Role

Event is driven by the receptionist.


Receptionist has log in into the system and the system is running.


1. The use case begin when receptionist click “Reservation” button

SRS-2009-04-V3 13


2. The system display reservation menu and IC number of the customer who made the reservation and receptionist click on “ Search ” button [SRS-REQ-V01-02-01]C-1: Enter IC number less/more than 12 digit) (E-1: Invalid IC Number) (E-2: Data Not Found)

3. The able to do following function:

1. Edit the customer’s information (A-1: Edit Customer’s Information)[SRS-REQ-V01-02-02]

4. The system gets the information.5. The system displays the reservation information. [SRS-REQ-V01-02-03]6. The use case end.


A-1: Edit Customer’s Information

1. At the same form receptionist enter IC number of the customer who made the reservation.

2. The system display the reservation information and receptionist can edit the information

3. The employee click “Submit” button.

4. The system update database.

5. The system continues.


E-1: Invalid IC Number

1. The system displays the “Invalid IC Number” message

2. The system waits for correct value.

3. The use case continues.

E-2: Data Not Found

1. The system display “Reservation Information is not found” message

SRS-2009-04-V3 14


2. The system clear the display

3. The use case is continues


1. Reservation information that has been made by customer shall be displayed.

3.2.2.8 Rules (s)

R-1: Restricted for receptionist

To check reservation and edit reservation information is restricted only for the receptionist those on duties.


C-1: Enter IC number less/more than 12 digit

The employee needs to enter exactly 12 digit for IC number



3.2.2.11 GUI


3.2.3 Use Case Stay Information [SRS-REQ-V01-03]

Employee Stay Information

3.2.3.1 Purpose

This use case is initiated by hotel’s receptionist. It has the capability of check room information which room type and room rate according to

SRS-2009-04-V3 15


the season. Also, this is a module to conduct the process of check in and check out of a customer whereby the room is whether being reserved.

3.2.3.2 Role

Event driven by the hotel’s receptionist


Employee has log in into the system and the system is running.


1. This use case begin when the employee log in into the system.2. The employee shall key in his/her given identification account as

employee [SRS-REQ-V01-01-02]3. Password of the employee’s identification required to log in into the

system.4. If the identification and password is valid, the employee able to

proceed into the main menu of the system else invalid identification and password will return to the log in form [SRS-REQ-V01-01-03].

5. Employee shall choose the check In [SRS-REQ-V01-03-01] or Check Out [SRS-REQ-V01-03-02] for the room option.

6. The employee is able to do following action:i. Cancel from check In /Out (A-1: cancel check In/Out

process) [SRS-REQ-V01-03-03]7. Check room availability[R-1: Check Room Availability] for check

In/Out process according to the season [SRS-REQ-V01-03-04].8. The information will be retrieved from the system’s database.


A-1: Cancel check In/out process

1. The hotel’s employee click on “Cancel” button.2. The system will return to the main menu of the system.3. The use case continues.


E-1: Invalid information

1. The hotel’s employee invalid inserts the room number for check available.

2. The system display “Invalid information”.3. Corrective action will takes place (clear the invalid information) and

waits for valid information.4. The use case continues.

SRS-2009-04-V3 16



1. Check In/out consists of the room availability; eg: Check In if room available and check out for room not available.

3.2.3.8 Rules (s)

Check to the room availability to proceed to the check in process



3.2.3.10 GUI

Please Refer Appendix BB5

3.2.4 Use Case Payment [SRS-REQ-V01-04]

Employee Payment

3.2.4.1 Purpose

This use case is initiated by the receptionist. It provides the capability to calculate the total bill of a customer had stayed at the hotel according to the duration of staying until the current day (day check out) and room rate at the present time.

3.2.4.2 Role

Event driven by the hotel’s receptionist


SRS-2009-04-V3 17


Receptionist has log in into the system and the system is running.


1. This use case begins when the receptionist clicks on the “ Payment” button and enters the customer ID.(C-1: Enter a Wrong ID)[SRS-REQ-V01-04-01]

2. The HMS display customer info (include name, dates and days of staying, type of room, room number and season)

3. The employee clicks on the “Calculate” button. [SRS-REQ-V01-04-01]

4. The HMS calculate the total price by season (R-1: Calculate Total Price for Payment) [SRS-REQ-V01-04-01]

5. The HMS displays the total price [SRS-REQ-V01-04-03]Receptionist clicks on ‘Print’ to print out the receipt for customer. [A-1: Print the Payment]

6. The use case ends.


A-1: Print the Payment

1. The receptionist clicks on the “Print” button.2. The HMS print out receipt according to payment record.3. The HMS will return to main menu.4. The use case continues.


E-1: Invalid Customer ID Number

1. The HMS displays the “Invalid ID Number” message.2. The HMS waits for a valid Customer ID number.3. The use case continues.


The number of name, day/s of staying, type of room and season, total payment, date of staying and time of check out display on the receipt.

3.2.4.8 Rules (s)

R-1: Calculate Total Price for Payment

Off Peak:

Peak Season:

Total Price for Peak Season = D * PPS

SRS-2009-04-V3 18

Total Price for Off Peak Season

= D * POP


where

D = Days stayed in the hotel

POP = Price on Off Peak season

PPS = Price on Peak season


C-1: Enter a Valid Customer ID Number

Receptionist must enter a valid customer ID number.



3.2.4.11 GUI


SRS-2009-04-V3 19


3.2.5 Use Case Report Generation [SRS-REQ-V01-05]

Generate ReportManager

3.2.5.1 Purpose

This use case is initiated by the hotel’s manager. It provides the option to print a report that displays the statistic of customer and type of room preferable according to season (peak and off peak) for selected duration.

3.2.5.2 Role

Event driven by the hotel’s manager.


Manager is log in into the system and the system is running.


1. This use case begin when the manager log in into the system. [SRS-REQ-V01-01-01]

2. The manager shall key in his/her given identification account as manager.

3. Password of the manager’s identification required to log in into the system.

4. If the identification and password is valid, the manager able to proceed into the main menu of the system else invalid identification and password will return to the log in form Manager shall choose the report generation option [SRS-REQ-V01-05-01]

5. Report of the hotel’s information will be printed which consists of average number of customer [R-1: Calculate the average number of customer] and statistic of preferable room type [R-2: Statistic of

SRS-2009-04-V3 20


preferable room type] according to the season [SRS-REQ-V01-05-03].

6. The manager key in invalid informationi. Wrong information being key [E-1: Invalid date]

7. The information will be retrieved from the system’s database.


Not Applicable.


E-1: Invalid Date

1. The hotel’s manager insert date start or date end which is not relevant.

2. The system display “Invalid date”.3. Corrective action will takes place (clear the invalid date) and waits

for valid information.4. The use case continues.


1. Report generated consists of the selected option; eg: statistic of preferable room type, average number of customer and wages of employee

3.2.5.8 Rules (s)

R-1: Calculate the average number of customer

Average number of customer = _____X_______

D

Where,

X = total number of customer(s)

D = total duration (day(s))

R-2: The statistic of preferable room type

Statistic of preferable room type: key in the number of customer according to the room type throughout duration.


C-1: Enter a right format of date (dd/mm/yyyy)

The hotel’s manager shall insert the date according to the right format.

SRS-2009-04-V3 21


C-2: Enter a valid information

The hotel’s manager shall insert the date as following 31st August 2008 which valid unlike 32nd of August 2008 which is invalid.



3.2.5.11 GUI

Please Refer Appendix BB8

SRS-2009-04-V3 22


3.3 PERFORMANCE REQUIREMENT

The result of calculation in payment shall be display within 3 seconds as the requirement for response time.

The query of Microsoft SQL server 2005 shall be executed in order.

SRS-2009-04-V3 23


3.4 REQUIREMENT TRACEABILITY

Table 3.2 Requirement Traceability

Requirement Number Descriptions Source

SRS-REQ-V01-01

SRS-REQ-V01-01-01

SRS-REQ-V01-01-02

SRS-REQ-V01-01-03

Login and Registration

Registration for a newly hired employee

User log into the system where required username and password

Error recovery which detect incorrect username and password

SRS-REQ-V01-02

SRS-REQ-V01-02-01

SRS-REQ-V01-02-02

Customer Reservation

Provide reservation function to perform reservation action towards postdated customer

Edit customer’s reservation information for any changes

Display the reservation information of

SRS-2009-04-V3 24


SRS-REQ-V01-02-03 the customer

Table 3.2 Requirement Traceability (cont)


SRS-REQ-V01-03

SRS-REQ-V01-03-01

SRS-REQ-V01-03-02

SRS-REQ-V01-03-03

SRS-REQ-V01-03-04

Stay Information (Check in)

Perform check in process for a customer to check in into room

Perform check out process for a customer to check out from room

Cancel check in/out process and return to main menu

Check room availability according to room type and season

SRS-REQ-V01-04

SRS-REQ-V01-04-01

Payment (Check Out)

Perform payment function by calculating according to the duration of staying, room type and season.

SRS-2009-04-V3 25


Table 3.2 Requirement Traceability (cont)


SRS-REQ-V01-04-02

SRS-REQ-V01-04-03

Cancel the payment action and return to the main menu of the system

Print function which allows to print a receipt which contains the information of paying such as duration of staying, room type, season and total payment

SRS-REQ-V01-05

SRS-REQ-V01-05-01

SRS-REQ-V01-05-02

SRS-REQ-V01-05-03

Report Generation

Report Generation option required for the application

Report Generation option being cancelled and return to the main menu

Calculation of average number of customer according to a certain duration and show the statistic of preferable room from time to time

SRS-2009-04-V3 26


4. DEFINITION, ACRONYMS AND ABBREVIATION

4.1 DEFINITIONS

HMS HMS is a stand alone system which can hold the information of the hotel computerized data storage which can be quick review and referred by user. In this system are comprises of modules for registration and login, reservation, check in/out, payment and report. These modules are created based on requirements needed by users besides to close up the relations among both target users.

Microsoft Relational database management system (RDBMS) which

SQL SERVER has more than 11 million installations. The program runs as a server providing multi-user access to a number of databases.

Employee The person who use HMS. Responsible to take reservation from customer, apply for check in and arrange payment from the customer.

Manager Hotel manager is the one who is able to access the report generation form to avoid receptionist knowing the statistic of the hotel’s business which is considered as private and confidential. The hotel manager is able to find out the average number of customer according to the duration and also, the type of preferable room from time to time

Internet

Browser

Software application which enables a user to display and interact with text, images, videos, music, games and other information typically located on a Web page at a website on the World Wide Web or a local area network.

Graphical User Interface

A program interface that takes advantage of the computer’s graphics capabilities to make the program easier to use. Well-designed graphical user interfaces can free the user from learning complex command languages. On

SRS-2009-04-V3 27


other hands, many users find that they work more effectively with a command-driven interface. Especially if they already know the command language.

Microsoft Visual Basic

It is an event driven programming language and associated development environment created by Microsoft. In business programming, it has one of the largest user bases. It is derived heavily from BASIC. Visual Basic enables Rapid Application Development (RAD) of graphical user (GUI) applications, access to database and creation of ActiveX controls. A programmer can put together an application using the component provided with Visual Basic itself

4.2 ACRONYMS

D - Days stayed in the hotel

GUI - Graphical User Interface

HMS - Hotel Management System

IC - Identification Card

ID - Identification Number

IEEE - Institute of Electrical and Electronics Engineers

NRIC - National Registration Identity Card

POP - Price on Off Peak season

PPS - Price on Peak season

REQ - Requirement

SQL - Structured Query Language

SRS - Software Requirement Specification

UML - Unified Modeling Language

SRS-2009-04-V3 28


Appendix A

Sequence Diagram

SRS-2009-04-V3 29

: Employee

:Login

: HMS controller

:Main Menu:Registration System Database

6.loginForm()

1.getNewEmployeeInfo()

4.getData()

2.getNewID()

3.getNewPassword()

5.updated

7.getPassword()

8.checkValidation()

6.getID()

9.invalid

10.re-typeIDPassword()

11.attendanceUpdate

13.enter()

:Login :Main Menu:Registration System Database

: HMS controller : Employee

1.loginForm()2.getID

4.checkValidation

3.getPassword

5.enter()


A1-Basic Flow (SRS-REQ-V01-01) (Log in and Registration)

A2 -A1 Alternative Flow (SRS-REQ-V01-02) (Login Directly)

SRS-2009-04-V3 30


A3- E1Exception Flow (SRS-REQ-V01-03) (Invalid Username and Password)

A4-Basic Flow (SRS-REQ-V01-02) (Reservation)

SRS-2009-04-V3 31


A5-A1- Alternative Flow (SRS-REQ-V01-02-02) (Edit customer’s information)

A6- E1 Exception Flow (SRS-REQ-V01-02-03) (Invalid NRIC)

SRS-2009-04-V3 32

Staff : Employee login : loginForm : HMS controller : mainMenu : checkIn/OutForm : CheckIn : CheckOut : RoomAvailability : HMS database

1:LoginForm

2:getID()

3:getPassword()

4:Invalid

5:Proceed To Main Menu

6:View CheckIn/OutForm

7:Check In Room

8:Check Room Availablility

9:getRoomStatus

10:Check Out Room

12:getRoomStatus

11:CheckRoom

Staff : Employee login : loginForm : HMS controller : mainMenu : checkIn/OutForm : CheckIn : CheckOut : RoomAvailability : HMS database

1:LoginForm

2:getID()

3:getPassword()



4:Invalid

7:Cancel


A7- Basic Flow (SRS-REQ-V01-03) (Stay Information)

A8-A1 Alternative Flow (SRS-REQ-V01-03-03) (Cancel Stay information)

SRS-2009-04-V3 33


: HMS controllerStaff : Employee login : loginForm : mainMenu : checkIn/OutForm : CheckIn : CheckOut : RoomAvailability : HMS database

1:LoginForm

2:getID()

3:getPassword()



8:Check In Room

12:Check Out Room

9:Check Room Availablility

13:CheckRoom

10:getRoomStatus

14:getRoomStatus

4:Invalid

7:Cancel

11:Invalid

15:Invalid

A9-E1 Exception Flow (SRS-REQ-V01-03-04) (Invalid information)

: Employee Login : LogInForm

: HMS controller : mainMenu Accounting : payment

: system database

1: logInForm()

2: getID()

3: getPassword()

4: Invalid

5: proceed main menu

6: getCustomerInfo()

7: Cancel()

A10-Basic Flow (SRS-REQ-V01-04) (Payment)

SRS-2009-04-V3 34




: system database

1: logInForm()

2: getID()

3: getPassword()

4: Invalid



7: Cancel()

A11-A1Alternative Flow (SRS-REQ-V01-04-02) (Cancel Payment)



: system database

1: logInForm()

2: getID()

3: getPassword()

4: Invalid



7: InvalidInfo

A12-E1 Exception Flow (SRS-REQ-V01-04-03) (Invalid Room Information)

SRS-2009-04-V3 35

Manager : Employee

login : login : LogInForm : HMS controller : :mainMenu : :generateReport system database : system database

reportOption : reportOption

1: logInForm()

2: getID()

3: getPassword()


6: printReport()

4: invalid

7: cancel


Manager : Employee



1: logInForm()

2: getID()

3: getPassword()

4: Invalid


6: printReport()

7: option()

8: getReportData

A13-Basic Flow (SRS-REQ-V01-05) (Report Generation)

A14-A1 Alternative Flow (SRS-REQ-V01-05-02) (Cancel Report Generation)

SRS-2009-04-V3 36

Manager : Employee



1: logInForm()

2: getID()

3: getPassword()


6: printReport()

4: invalid

7: cancel


A14-A1 Alternative Flow (SRS-REQ-V01-05-02) (Cancel Report Generation)

Manager : Employee



1: logInForm()

2: getID()

3: getPassword()


6: printReport()

7: option()

8: getReportData

4: invalid

9: invalid

A15-E1 Exception Flow (SRS-REQ-V01-05-03) (Invalid Information)

SRS-2009-04-V3 37


Appendix B

Graphical User Interface

SRS-2009-04-V3 38


B1-Log in form

B2-Registration Form

SRS-2009-04-V3 39


B3 – Check Reservation

B4 – Display Reservation Information

SRS-2009-04-V3 40


B5 – Check in/out form and room availability form

SRS-2009-04-V3 41


B6 – Payment form

B7- Printed Receipt (example)

SRS-2009-04-V3 42


B8- Report Generation Form

SRS-2009-04-V3 43

SRS HMS

Documents

software requirement

e1 exception

a1 alternative

report generation

report generation

report generation

cancel report

hotel management