Report SRS

CHAKA Hotel Management System Software Requirements Specifications

REQUIREMENTS ENGINEERING DUY TAN UNIVERSITY

TABLE OF CONTENTS I. INTRODUCTION ............................................................................................... 4

1. PURPOSE ............................................................................................................ 4

II. SOFTWARE REQUIREMENTS SPECIFICATIONS ....................................... 4

1. VISION AND SCOPE ............................................................................................ 4

1.1. Short description ........................................................................................ 4

1.2. Context diagram ......................................................................................... 5

1.3. Vision .......................................................................................................... 5

1.4. Scope .......................................................................................................... 5

1.5. Budget ......................................................................................................... 6

1.6. Resource ..................................................................................................... 6

2. ELICITATION ...................................................................................................... 6

2.1. Interview ..................................................................................................... 6

2.1.1. Purpose .................................................................................................... 6

2.1.2. Stakeholder .............................................................................................. 7

2.1.3. Interviewee .............................................................................................. 7

2.1.4. Interview ................................................................................................. 7

2.1.5. Templates ................................................................................................ 9

3. ANALYSIS ........................................................................................................17

3.1. Business Flow Diagram ...........................................................................17

3.2. Functional ................................................................................................17

3.2.1. Functional Requirement ........................................................................18

3.2.1.1. Operational Scenarios ........................................................................18

3.2.1.2. Operational Process ...........................................................................20

3.3. None Functional .......................................................................................21

3.3.1. Performance Requirements ...................................................................21

3.3.2. Safety Requirements .............................................................................22

3.3.3. Security Requirements ..........................................................................22

3.3.4. Business Rules ......................................................................................22

3.4. Quality Attribute .......................................................................................22

4. SPECIFICATION.................................................................................................23

4.1. Context diagram .......................................................................................23

4.2. List of actors .............................................................................................24

4.3. List of Use Case ........................................................................................25



4.4. Use Case Diagram ...................................................................................40

4.4.1. Receptionist ...........................................................................................40

4.4.2. Manager .................................................................................................41

4.4.3. Owner ....................................................................................................42

4.5. Prototype ..................................................................................................43



Revision History

Name Date Reason for Change Version

New Document 2014-09-30 None 1.0



I. Introduction

The following subsections of the Software Requirements Specifications

(SRS) document provide an overview of the entire SRS.

1. Purpose

The Software Requirements Specification (SRS) will provide a detailed

description of the requirements for the Chaka Hotel Management System (CHMS).

This SRS will allow for a complete understanding of what is to be expected from the

newly introduced system which is to be constructed. The clear understanding of the

system 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 Chaka Hotel

Management System can be designed, constructed, and finally tested.

This SRS will be used by the system development team which is constructing

the CHMS and the hotel end users. The Project team will use the SRS to fully

understand the expectations of this CHMS to construct the appropriate software.

The hotel end users will be able to use this SRS as a “test” to see if the constructing

team will be constructing the system to their expectations. If it is not to their

expectations the end users can specify how it is not to their liking and the team will

change the SRS to fit the end users’ needs.

II. Software Requirements Specifications

1. Vision and Scope

1.1. Short description

The Chaka 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 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.



1.2. Context diagram

1.3. Vision

For Thanh Lam Trang Hotel who need the Chaka Hotel Management

System is a manage software that help the customer manages Service of Hotel and

Employees unlike customer can change a name and logo of customer in product

and print it to bill and training for employee of customer, our product or service

help a customer manage hotel so quickly and easily.

1.4. Scope

The introducing software, Chaka Hotel Management System which is going

to be implemented for Hotel Thanh Lam Trang will automate the major operations

of the hotel. The Reservation System is to keep track in room and hall reservation

and check availability. The Room Management System is for manage all room types

room services. The Inventory Control System will keep track in all inventories of

the hotel and guest details will handled by guest management. Administration

department will monitor the all. There is three End Users for CHMS. The End Users

are Owner, Manager and Receptionist. Owner can access to all system

functionalities without any restrictions. Manager can access to all system

functionalities with limited restrictions. Receptionist can only access to the

Figure 1. Context Diagram

RECEPTION

OWNER

MANAGER

CHAKA HOTEL

MANAGEMENT

SYSTEM



Reservation management section. To keep restrictions for each End User levels

CHMS can create different Login functions.

The objectives of the automated Chaka Hotel Management System is to

simplify the day to day processes of the hotel. The system will be able to handle

many services to take care of all customers in a quick manner. As a solution to the

large amount of file handling happening at the hotel, this software will be used to

overcome those drawbacks. Safety, easiness of using and most importantly the

efficiency of information retrieval are some benefits the development team going to

present with this system. The system should be user appropriate, easy to use, provide

easy recovery of errors and have an overall end user high subjective satisfaction.

1.5. Budget

Personal Computer:

o Amout: 2.

o Price: 250 USD/PC.

Server:

o Amount: 1.

o Price: 1000 USD.

Printer:

o Amount: 1 (minimal).

o Price: 70 USD/device.

License Chaka Hotel Management System

o Price: 400 USD/year/customer.

1.6. Resources

Programmer: 6 employees

Tester: 3 employees

Requirement engineer: 2 employees

Designer: 2 employees

Computer: 15 computers

Server: 1 server

2. Elicitation

2.1. Interview

2.1.1. Purpose

Purpose of the document is to update requirements which are changed by

customer. The document will be base to clearly analyze and specify customer’s

requirement.



2.1.2. Stakeholder

- The manager of Thanh Lam Trang Hotel

- Project team

2.1.3. Interviewee

- Manager of Thanh Lam Trang Hotel

2.1.4. Interview

a. Setup schedule

We will make appointment with the manager of operation at 14:00,

09/09/2014 in the Thanh Lam Trang Hotel and end interview at 15:30 on

same day.

b. Interview - An, Le Ngoc: Hi, I’m An, Le Ngoc. I come from CHAKA TEAM and I have a meet

with Ms Huyen.

- An, Le Ngoc: I was scheduled with you on today to get the software requirements

that company has requested, and this is my Visit Card.

- This is the document that I sent to you via email. On company’s request, the

software managed hotels must implement the following functions: booking room

management, management of supplies, services, staff, and revenue and

expenditure statistics.

- Based on the experience of the project manager, the hotel manager process

booking room follows: Customers demand at the hotel can call or direct booking.

Staff will use the program to record booking information on the registration form,

and when customers check in, you can add the necessary information such as ID /

PASSPORT, check-in time. When customers check out, reception will be based on

register to calculate fees (room charge, service charge, VAT tax) and then export

the coupon payment.

- Ms Huyen: In terms of the process is correct but Thanh Lam Trang Hotel wanted

to add one website to promote hotels and online booking functionality.

- An, Le Ngoc: How is the process of booking room?

- Ms Huyen: To book room, the customers must enter information about them, the

number of rooms, type of room, and time of check in-check out. After that

customer will trans money to Thanh Lam Trang Hotel’s bank account

- An, Le Ngoc: Here I found some companies have billing functions via online

bank accounts very well as Paypal, Ngan Luong, Bao Kim and using credit cards

and debit cards such as Visa, MasterCard.

- Ms Huyen: That good, Chaka TEAM should add this request to the list required

by the Thanh Lam Trang Hotel for products.

- An, Le Ngoc: Would you like to add any requirements?



- Ms Huyen: In addition, Lam Thanh Trang Hotel not only want products with

logo of Thanh Lam Trang Hotel but also wanted after the invoice has both logo

and information on the hotel page Thanh Lam.

- An, Le Ngoc: I'll add to the list of functions is required.

- An, Le Ngoc: Would you like to add any requirements?

- Ms Huyen: No, thanks.

- An, Le Ngoc: This is the record of required changes today, please read it.

- An, Le Ngoc: Do you want to change anything? If you do not, please certify their

fears about the required change.

- An, Le Ngoc: Thank you for cooperation. Wishing you happy and successful.



2.1.5. Templates



3. Analysis

3.1. Business Flow Diagram

Figure 2. Business Flow Diagram

3.2. Functional

Below is a list of all functions that can be found in the system with a description of

the function and its priority. The priorities range from 1 to 3, with 1 being the

highest priority and 3 being the lowest.

Priority Detail

1 Must have

2 Should have

3 Nice to have Table 1. Function’s priorities range

Function

ID

Name of Main

Function

Description Priority

FU01 Make

Reservations

Add a new reservation 1

FU02 Search Rooms Search ID or Name of room in list 2

Hotel Management System

Receptionist

Search room

Issue Bill

Add Payment

Manage Guest

Manage Reservaion

Manager

Manage Room

Manage Staff

Manage Inventory

Report

Owner

Set Room rate

View Report

Delete Staff member

Take Backup



FU03 Add Payment Add a payment to System 1

FU04 Issue Bills Manage Issue Bills 1

FU05 Manage Guest

(Add, Update

Guest)

Add, Update information of Guest 1

FU06 Manage Room

Details (Add,

Update, Delete)

Manage Room of Hotel 1

FU07 Manage Staff

(Add, Update,

Delete, View)

Manage Staff of Hotel 1

FU08 Manage Inventory

(Add, Edit,

Delete)

Manage Inventory of Hotel 1

FU09 Set Rates Set rate for rooms 2

FU10 Retrieve Reports

(Staff payment,

Income)

Report Viewer 1

FU11 Manage Users

(Add, Update,

Delete)

Manager User to use a system 1

FU12 Taking Backups Backup and Restore database 2

FU13 E-mail

notifications

Send email to customer or employee 2

Table 2.Functions list

3.2.1. Functional Requirement

3.2.1.1. Operational Scenarios

Reception

- When customer order?

Check list of rooms available in the record. Record customer information

and the number of rooms rented in the book. Unavailable this room in list.

- While customer stay?

Record the client services and materials used in the record.

- When customers check out?



Calculations based on data in record. Receive customer payments. Fill in

record.

- When guests want to book a room (guest have to come to the hotel)?

Check the list of rooms available. Record customer information and date

will come. Get the payment. Fill in record.

Manager

- How do you manage room?

Check the list of rooms available and room had guest.

- How do you manage staff?

Manage employee information (name, date of birth, address, date start,

salary). Daily attendance is recorded in the timekeeping. Record the productivity

of employees.

- How do you manage inventory?

Check all inventory everyday and fill in record.

- How do you general report?

Statement of collecting monthly, quarterly, annually for directors based on

the data in the records.

Owner

- What do you do when set room rate?

Catelogy types of room, set price of room.

- What do you do when view report?

View report from manager. Appreciating condition of Hotel.



3.2.1.2. Operational Process

FU01 Make Reservations

Input Code, Number of children, Number of adults, check-in

date, check out date, status, Number of nights

Output Database Record, Database successfully updated

message

Processing Validate the given details and record the information in

to the database.

FU02 Add Guest

Input Member code, Phone number, Company, Name, E-mail,

Gender, Address


message


to the database.

FU03 Add staff member

Input Code, Employee Name, Employee Address, NIC, Salary,

Name Age, Occupation, E-mail


message


to the database.

FU04 Search Rooms

Input Period, Check-in, Check-out, Guest

Output Display a message with available room details

Processing Validate the given details and check for the available

rooms in a given time period and return it’s availability.

FU05 Add Payments

Input Total, pay time, Credit card details


message


to the database.



FU06 Issue Bill

Input Billing no, Quantity, Price, Taxes, Date, Services, Unit

Output Printed version of the bill

Processing Validate the given details and total cost is calculated

according to the

Services gain by the customer.

FU07 Set Rates

Input Check-in, Check-out, Day, No.of guests, First night

price, Extension price


message


to the database.

FU08 Taking Backups

Input Location to save the backup file

Output Display a message showing backup successfully created

Processing Validate the user given location to save the backup file.

Save the backup file to the user specified location

3.3. None Functional

3.3.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.



3.3.2. Safety Requirements

There are several user levels in Chaka 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.

3.3.3. Security Requirements

Customer Service Representatives and Managers and owner will be able to

log in to the Chaka Hotel Management System . Customer Service Representatives

will have access to the Reservation/Booking and subsystems. Managers will have

access to the Management subsystem as well as the Reservation/Booking

subsystems. Owner has the maximum privilege to all subsystems. Access to the

various subsystems will be protected by a user log in screen that requires a user name

and password.

3.3.4. Business Rules

Chaka Hotel Management System will perform under three users which are

Owner, Manager and Receptionist. The system is designed in a way where

responsibility and privileges are decreased in the order of owner, manager and

receptionist. The role of manager is elected in the aim of making the owner’s hands

free from regular interfering with the system. So, most of the privileges that owner

has are given to manager, except the ones are critical and important. Some features

like that are, taking backup, restoring of the system and handling financial details,

hotel income reports of the system. Receptionist is given with the most frequently

used features of the system which has less responsibility than the other two users.

Deleting of any information in the system is only allowed for the owner of the hotel.

3.4. Quality Attribute

Availability: - The system shall be available during normal hotel operating

hours

Integrity: - How the system would insecure the information in the system

and how it avoids the data losses. Referential integrity in database tables

and interfaces

Maintainability: - How easy is to keep the system as it is and correct

defects with making changes.

Portability: - The Chaka Hotel Management System shall run in any

Microsoft Windows environment



Reliability: - Specify the factors required to establish the required

reliability of the software system at time of delivery. Mean time between

failures and mean time to recovery

Reusability: - What is the ability to use the available components of the

system in other systems as well.

Usability: - How easily a person can be taken the benefits of the system

and the user friendliness.

Robustness: – Strength of the system to handle system functions

accurately and maintain the database without facing to unexpected failures

4. Specification

4.1. Context diagram

Figure 3. Context Diagram

RECEPTION

OWNER

MANAGER

CHAKA HOTEL

MANAGEMENT

SYSTEM



4.2. List of actors

Manager

View

Insert

Update

Delete

Add

Update

Delete

Add

Update

Reports

Department Details

Department

Details

Department Details

Room/Staff/InventoryDetails



GuestDetails

GuestDetails

Delete GuestDetails

Search Rooms

Make Reservations

Owner

Receptionist

Issue Bill

Figure 4. High Level Architecture



4.3. List of Use Case

Use Case

ID

Primary Actor Use Cases

UC-01 Receptionist Make Reservation

UC-02 Receptionist Check Availability

UC-03 Receptionist Add Guest

UC-04 Manager Add Room

UC-05 Owner, Manager Delete room

UC-06 Owner, Manager Edit room properties

UC-07 Manager Guest search

UC-08 Owner, Manager Create system restore point

UC-09 Manager Set room rate

UC-10 Manager Add Property

UC-11 Owner View financial reports

UC-12 Receptionist Delete Guest

UC-13 Receptionist Change Guest information

UC-14 Owner Take Backup

Table 3. List of Use Cases



Use Case ID: UC-01

Use Case

Name:

Make Reservation

Created By: Chuong Nguyen Tran

Viet

Last Updated

By:

Chuong Nguyen Tran

Viet

Date

Created:

2014-09-06 Last Revision

Date:

2014-09-06

Actors: Receptionist

Description: Add a new reservation

Trigger:

Preconditions: Guest shouldn’t already be exist

Postconditions: Hotel Guest Details updated to include current Guest

Normal Flow: 1. Receptionist enter guest details

2. System searches for room details

3. System presents room types and tariffs

4. Customer selects room and confirms tariff

5. System records customer’s name and address

6. receptionist confirms booking on system

7. System generates confirmation receipt

Alternative Flows: Not have

Exceptions: Not have

Includes: Not have

Frequency of Use: Usually

Special

Requirements:

Not have

Assumptions: Not have

Notes and Issues: Not have



Use Case ID: UC-02

Use Case

Name:

Check Availability


Viet

Last Updated

By:

Chuong Nguyen Tran

Viet

Date

Created:


Date:

2014-09-06


Description: To check whether a room available or not

Trigger:

Preconditions: Login to the system.

Postconditions: Not have

Normal Flow: 1. Display User interface

2. Select Availability Tab

3. Enter room type, duration, number of adults and children

4. System check room availability relevant to each

requirements

5. Display available room details


Exceptions: No room available for entered details and display “No Room

Available”

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-03

Use Case

Name:

Add Guest


Viet

Last Updated

By:

Chuong Nguyen Tran

Viet

Date

Created:


Date:

2014-09-06


Description: Add a new Guest

Trigger:

Preconditions: Log in to the system

Postconditions:

Normal Flow: 1. Receptionist selects “add guest” button.

2. System prompts to fill out guest details.

3. System validates details.

4. Update database.

5. Display “Successful message”.

6. Guest details are incorrect, Display the message

"Unsuccessful" and display Add guest option.


Exceptions: Guest details are incorrect, Display the message

"Unsuccessful" and display Add guest option.

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-04

Use Case

Name:

Add Room


Viet

Last Updated

By:

Chuong Nguyen Tran

Viet

Date

Created:


Date:

2014-09-08

Actors: Manager

Description: Add a new room to the system

Trigger:



Normal Flow: 1. Manager clicks “add room” button.

2. System prompts the manager to fill out room details.

3. System validates new room information.

4. System creates a new room.

5. Update database.

6. Display “successful ” message.


Exceptions: Room details are incorrect, Display the message

“Unsuccessful" and display room management option.

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-05

Use Case

Name:

Delete room

Created By: An Ngoc Le Last Updated

By:

An Ngoc Le

Date

Created:


Date:

2014-09-08

Actors: Owner, Manager

Description: Delete a room from the system

Trigger:



Normal Flow: 1. User select “delete room” option

2. Display delete room option

3. User select the room

4. System display confirm message

5. User select confirmation

6. Update database

7. Display “successful message’

Alternative Flows:

Exceptions: If user select “No” details are not remove from the database.

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-06

Use Case

Name:

Edit room properties


By:

An Ngoc Le

Date

Created:


Date:

2014-09-08

Actors: Owner, Manager

Description: Alter properties such as view or type of room

Trigger:



Normal Flow: 1. Manager selects “change room properties”

2. System prompts manager to select room

3. Manager select the room

4. System display room properties

5. Manager edit room properties

6. System alters room properties

7. Update database

8. Display “successful” message



Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-07

Use Case

Name:

Guest search


By:

An Ngoc Le

Date

Created:


Date:

2014-09-09

Actors: Manager

Description: Modify or delete guest information

Trigger:



Normal Flow: 1. User select search option

2. System displays search interface

3. User enters details

4. System validates user inputs

5. Display search results


Exceptions: User inputs are invalid and prompt Display unsuccessful

message

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-08

Use Case

Name:

Create system restore point

Created By: Khanh Nguyen Last Updated

By:

Khanh Nguyen

Date

Created:


Date:

2014-09-09

Actors: Manager

Description: Create a system restore point to the system

Trigger:



Normal Flow: 1. User Select security option

2. System display security option interface

3. User select system restore

4. User select system restore point

5. System validates details

6. Create system restore point

7. Update database

8. Display “successful message”


Exceptions: If system restores point invalid display “invalid selection”

user redirected to security option.

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-09

Use Case

Name:

Set room rate

Created By: Khanh Nguyen Last Updated

By:

Khanh Nguyen

Date

Created:


Date:

2014-09-10

Actors: Manager

Description: Set room rate to hotel room in system

Trigger:



Normal Flow: 1. User select room properties

2. Display room management window

3. User selects set room rates

4. Display enter room rate

5. User enter room rates

6. Validate details

7. Update database

8. Display “successful” message


Exceptions: If room rates set previously clear them and redirect to set

room rates

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-10

Use Case

Name:

Add Property

Created By: Hau Phan Ngoc Last Updated

By:

Hau Phan Ngoc

Date

Created:


Date:

2014-09-10

Actors: Manager

Description: Add a new property to the system inventory

Trigger:



Normal Flow: 1. User Select inventory section

2. System displays inventory handling section

3. User Select add property

4. User enter product details

5. Validate product details

6. Update database

7. Display successful message


Exceptions: If data invalid display “Invalid selections” redirect to

inventory section window

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-11

Use Case

Name:

View financial reports

Created By: Hau Phan Ngoc Last Updated

By:

Hau Phan Ngoc

Date

Created:


Date:

2014-09-10

Actors: Owner

Description: View a financial report for specific time

Trigger:



Normal Flow: 1. System prompts the owner to select two dates

2. Enter dates

3. System will display the revenue for that specific time


Exceptions: If invalid details entered Display “unsuccessful” message

and reenter interface.

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-12

Use Case

Name:

Delete Guest

Created By: An Le Huu Last Updated

By:

An Le Huu

Date

Created:


Date:

2014-09-10


Description: Delete a Guest

Trigger:


Postconditions: A new guest is added to the system

Normal Flow: 1. User interface displayed

2. Select “delete Guest” option

3. Enter guest details

4. Valid guest details

5. System display guest details

6. System confirms deletion of selected guest

7. Update database


Exceptions: If invalid details entered Display “not found” message and

redirect to main interface

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-13

Use Case

Name:

Change Guest information


By:

An Le Huu

Date

Created:


Date:

2014-09-11


Description: Alter properties such as telephone number or email of guest


Postconditions: Guest details edited

Normal Flow: 1. User interface displayed

2. Select “Edit Guest” option

3. Enter guest details

4. Valid guest details

5. System displays guest properties

6. System alters the guest properties

7. Update database

8. Display “Successful” message

9. Database updated


Exceptions: If invalid details entered Display “unsuccessful” message

and redirect to main interface

Includes: Not have


Special

Requirements:

Not have





Use Case ID: UC-14

Use Case

Name:

Take Backup


By:

An Le Huu

Date

Created:


Date:

2014-09-11

Actors: Owner

Description: Not have

Trigger:



Normal Flow: 1. Display user interface

2. Select backup option

3. Display backup interface

4. Select create backup option

5. Create backup

6. Creating backup process is not successful, display

“Unsuccessful” message.



Includes: Not have


Special

Requirements:

Not have





4.4. Use Case Diagram

4.4.1. Receptionist

Figure 5. Receptionist Use Case Diagram



4.4.2. Manager

Figure 6. Manager Use Case Diagram



4.4.3. Owner

Figure 7. Owner Use Case Diagram



4.5. Prototype

Figure 8. Main User Graphic Interface



Figure 9. Customer Information User Graphic Interface



Figure 10. Invoice & Bill User Graphic Interface



Figure 11. Room Manage User Graphic Interface



Figure 12. Statistics User Graphic Interface

Report SRS

Documents

Transcript of Report SRS