Hotelreservationchapter3 2

Chapter 3
Chapter 3
3.1 Software Requirement Specification
3.1.1 Introduction
To develop the Online Hotel Reservation, the work is started by gather

information about the topic. The technology such as software and hardware needed
to develop the study are decided. To gather requirements of this study, discussion is
held within supervisor and hotel staffs.
After studying and analyzing the flow of the current system of hotel, the
proponents would like to recommend the following: the system proves to be fast
accurate convenient, efficient and reliable for the process of reservation. The
proponent developed an online reservation system suitable for the hotel; the system
could save time, effort in filling and monitoring.
Hotel reservation system plays a great role and has a potential effect on day to
day performance measures, this type of system have highly evolved from decades
due to high demand for their use, effective and efficiency in any given institutions.
Due to the rapid change of technology the use of such system has become a
necessity to any given high learning institution for better performance and be used
with quite a large number of users at the same time but it can save time, resources
and creates awareness of the evolving technology.
3.1.1.1 Goals and Objectives
3.1.1.1.2 Goals
The goal of the current system is to develop a Hotel

reservation system to replace the computerized Hotel reservation. The
purpose of the document is to describe requirements for the Online
Hotel Reservations Software that will serve as a foundation for the final
product. It is important that an agreement of these requirements be
reached so that everyones expectations will be met. This document
Online Hotel Reservation System Page 1

Chapter 3
uses written descriptions as well as various types of modeling diagrams

to illustrate the high level structure of the application. Although some of
these diagrams may seem to convey similar information they typically
do so from an alternate perspective. This gives different stakeholders a
view of the requirements that is better suited to their area responsibility.
A web based solution will be delivered so that users the system

with their favorite browser. By designing around a standardized
language like JAVA the application will run on the most popular
computer platforms connected to the internet will allow employees to
more easily share information.
The Hotel Reservation System Software is intended to provide a

computer based system that will assist in managing in a guest. Many
typical functions involved in operating a hotel will be automated through
software to improve the operational workflow within a facility, for
instance maintaining a guest rooms to be check in. in addition, tasks
like processing invoices and printing guests reports will be available
within the program to minimize the time that administrative staff must
spend creating these documents. This requirements Specification will
describe these as well as many other features of the software in greater
detail.
3.1.1.2 Statement of Scope
The initial stage of project development is to find of

system requirements and define project scope. Scope or boundary
of project is important to anticipate the time of completion. By a
clearly defines scope, specified time will be assigning to develop
each module in the application. From here can conclude that,
virtual tour on hotel room needing more using digital video camera.
Other module my need less time for completion. By well-organized
tasks and duration, the application will develop on time, within
scope and fulfill all the system requirements.
Chapter 3
After defining the project scope, the matters that will

considered in doing the research are time, resources, technology
and skills. The unavailability of the time during the project
development, such as several tasks that need to be handle in one
time need to be consider when building the schedule. The
resources availability, such as expertise, reference books or
internet online also needs to be considered. The lack of technology
and skills in the developer will also affect the schedule planning.
3.1.1.3 Software Context
There are many key component of hotel reservation. But the

ability of their hotel reservation to remain in the business will be dictated
in their ability to manage, development projects would be severe risk of
missing deadlines, escalating budgets and a low-quality system. As a
conduct a project study, our system provides the structure, method,
controls and checklist needed to ensure successful development.
In this project, the application developed is called online hotel

reservation, which is web-based application. This onlined reservation
application is accessible through internet and local area network. The
programming languages and software involved in this project are
identified.
For the project facilities, laser printer is required to print the

project documentation. Scanner is using to scan pictures that are needed
to place in this document.
3.1.1.4 Major Constraints
The hotel Reservation System will use Microsoft

ASP.net which requires a web server supporting this technology.
3.1.2 Usage Scenario

Chapter 3
3.1.2.1 User Profiles
The following definitions describe the actors in the system.
Admin An admin has the responsibility for registering a new customer

and also he can access the system including the viewing and
changing password.
Staff The staff can only view the system if client/customer got check in
and check out and also the information of the guests.
System The system refers to the computer hardware and software that
controls all application. Its accepts user input ,display user output,
and web server thru internet.
3.1.2.2 Use Case
The following is how the guest reserves to the hotel:
1. Log onto system
2. Display available rooms
3. Reserve for the room Available

Chapter 3
3.1.2.2.1 Use-Case Diagram
3.1.2.2.1 Reception of user-case diagram
Check in
Date
Room
Check Out
Reserved
Date
Room
Category
Update
Customer
Modify
Customer
Modify
Reservation
Figure 1.Reception of User-caser Diagram
Figure 1.Reception of User-caser Diagram. This figure represents the transaction between
the admin and the costumer

Chapter 3
3.1.2.2.2 Use-Case Description
Use-Case Search available room

Goal:
Reception search for available room
Actors: Reception System
Preconditions The reception must insert the check in and checkout

: date
The reception clicks the button "Search
Triggers:
Basic 1. The reception specify the check in and checkout

Scenario: date.
2. The reception adds room type.
3. Reception clicks on the button "Search".
4. The system will show the available rooms with

their type on the determined dates.
5. The reception chooses the rooms the customer

prefers depends on the floor and the view and clicks
the button "Booking".
6. System will take the reception to the booking

details page.
Post The reception searched for the available rooms.

Conditions:
Use-Case Booking Details

Chapter 3
Goal:
Insert the booking details.
Actors:
Reception System
Preconditions:
The reception must be done with the
room search.
Triggers:
Reception click the button "Save"
Basic Scenario: 1. Check in date, check out date.
2. The reception fill the Guest Details

"First and Last Name, Address, Email,
Telephone Number and finally the guest
identification number".
3. Then the reception must fill the guest

credit card information "Credit card
number, credit card holder name and the
credit card expire date".
4. Then the reception clicks on "Save" to

save all the information on the database.
5. The system will check the information

before saving it in case the receptions
forget to insert any of the important
information.
Post Conditions:
The receptions have completed the

Chapter 3
booking details.
Use-Case Remainder Email

Goal:
Send a remainder email to the guest to
date before the check in date.
Preconditions: Reception must be able to access the

system via a web browser; booking
details must be in the database.
Triggers:
Reception clicks button "Remainder

Email".
Basic Scenario: 1. The reception clicks to view a list with

the entire guest who will check in after
two days.
2. The reception clicks "Send" to send a

remainder email to each guest.

Chapter 3
Use-Case
Change Guest Information
Goal:
Alter properties such as telephone
number or email of the guest.
Actors:
Reception System
Preconditions:
Reception must be able to access the
system via web browser.
Triggers:
The reception clicks the button "Change
Guest Properties".
Basic Scenario:
Basic Scenario: 1. Reception clicks the
button to initiate change guest properties
process. 2. System prompts the
administrator to a guest by searching
using the guest identification or viewing
a list of guest. 3. System displays the
guest properties. 4. System alters the
guest properties. 5. System displays the
home page.
Post Conditions:
A room has been altered with the
system.

Chapter 3
Use-case
Customer Search
Goal:
Modify a customer information.
Preconditions:
The customer information should be on the
database.
Triggers:
The reception searches for customer by
his ID or view all the customer list.
Basic Scenario:
1. After the reception search's for a
customer his information will upper on the
page "First and Last name, address,
telephone number, and his email".
2. Modify the customer information.
Post Conditions: The customer details will be modified.
3.1.2.3 Special Usage Considerations

Chapter 3
Billing fees cannot be change.
3.1.2.4 Activity Diagrams
The following activity diagrams show the actions that occur during particular use-
case.
Figure 2. Activity Diagram for Online Hotel Reservation System.

Chapter 3
3.1.3. Data Model Description
3.1.3.1 Data Objects
Guest Data Object

CostumerID A unique identifier assigned to the costumer.
Form displays of a units/rooms occupancy status presentation that gives
the ability to select a free unit and make a reservation by one click
Name The costumers name.
Birthdate The childs birth date.
Special Needs Any special needs such as housekeeping food and
others.
Status indicates if the customer is check in or in waiting list.
Comments a customer comment about the hotel.
Employee Data Object

UserID A unique number assigned to the employee.
Password The employees Password used to log on to the computer
system.
FirstName The employee first name.
LastName The employees last name.
Hotel Room Data Object

HotelRoomID A unique number for the hotel room.
Hotel RoomNO. The hotel room number.
Phonenumber The phone number of the hotel room.
Check In Data Object

GuestID the identifier number of the guest.
RegisteredDate The date that the guest registered
Check INDate The date that the guest check in.
Check Out Data Object

GuestID The identifier number of the guest.
RegisteredDate The date that the guest registered
Check OutDate The date that the guest check out.
Confirmation Data Object

ConfirmationID A unique identifier for the confirmation.
GuestID The identifier number of the guest.
EmailAdd Sends the confirmation check into the hotel.

Chapter 3
3.1.3.2 Relationships
In order for a guest have an account with the hotel they must
have been check in to the hotel. Since a guest can have a multiple
guest a one too many relationship exists. It is also true that a guest
cannot exist alone in the hotel system. In the general all guest must
have registered for the hotel.
A guest will receive a confirmation for the GuestId. A guest will

pay in advanced bill using their credit cards. However after their check
in they should pay their bill the two data object cannot exist alone.
The Hotel Room can hold up depend to their reservation. They

cannot be reserved it if they has a guest at that day. A one to one
relationship exists because a hotel room will have at most waiting list
and each list can only be used for a single Hotel Room.
An employee may add multiple events to their daily reminder list

so one-to-many relationship exists. Since the employee may not need
to be reminded of anything it is possible for an employee to exist
without a daily reminder, but a daily reminder must be assigned to a
specific employee.
Each time an employee edits a record it will be recorded in the

change data object. Most employees will make multiple changes so
there is a one-to-many relationship between employee and the change
data objects. An employee may not any change and can therefore exist
alone. However, a change object must be associated with an employee
and therefore cannot exist alone
3.1.3.3 Complete Data Model

Chapter 3
The relationships between the data objects
Figure 3. Relationship diagram for the Hotel Reservation system.
3.1.4 Functional Model Description

Chapter 3
3.1.4.1 Class Diagram
figure4. Online Hotel Reservation class diagram
3.1.4.2 Software Interface Description

Chapter 3
3.1.4.2.1 External Machine Interfaces
The software will be capable of printing invoices and

reports on a local or network printers
3.1.4.2.2 External System Interfaces
The Online HR system will communicate with a web

server on the internet through a high speed network connection
such as DSL, cable, or T1 line
3.1.4.2.3 Human Interface
Web pages shall permit complete navigation using the

keyboard alone, in addition to using mouse and keyboard
combinations
3.1.4.3 Reports
Inventory of Reports
Layout of Reports
Data Dictionary of Reports
3.1.5 Behavioral Model Description
3.1.5.1.1 Description for Software Behavior
3.1.5.1.1 Events
Guest Class Events

Guests reservation room
Guest check in
Guest check out
Guest bill
Administration Class Events

Administration is hired
Administration logs onto the system
Administration logs off of the system
Administration gets promoted
Administration is no longer employed
3.1.5.1.2 States

Chapter 3
Guest States Description
Reserved The guest has been sign in to a hotel request.
Check In The guest has arrived in the hotel.
Check Out The guest left the hotel.
Administration Description
On Line The employee has logged on to the system.

Off Line The employee has logged off the system.
3.1.5.2 State chart Diagram

RROOMoom Statechart
Vacant
Rm No entered when customer checks in
Five hrs. past check in

Rm. no. entered
Customer check out
Occupied Reserved
Room number entered when customer check in
Figure 3. Room State Chart

Chapter 3
Scheduler Statechart
Retrieve Time
System Started
Time is 1:00 p.m.

Scheduler Running Billing Additional Day
Billing Complete
System Stopped
Time is 6:30 p.m.
Billing Complete
Reservations Canceled
Time is 6:00 p.m. Billing Guaranteed Reservations
Cancelling Non-guaranteed Reservations
Figure 4. Scheduler State chart
3.1.6 Restrictions, Limitation, and Constraints
The system shall integrate within the existing LAN structure and with the existing
system, such as the database management system.
All JAVA codes shall conform to the Java standard.
All server side code shall be written in java Eclipse.
3.1.7 Validation Criteria
Software validation will ensure that the system responds according to the
users expectations; therefore it is important that the end users be involved in some
phases of the test procedure. All tests will traced back to the requirements.
3.1.7.1 Classes of Tests
Unit testing will be conducted on all of software subsystem

including:
1. Daily reminders
2. Viewing and editing information
3. Viewing and printing reports
4. Logging on to the system
5. Reserve for the room hotel
6. Viewing and printing invoices

Chapter 3
Acceptance testing will be conducted at the Guests Site.
3.1.7.2 Expected Software Response
The software should display an appropriate error message when a

value outside the accepted limits is entered.
The software should not be capable of deleting a guest record
even if they withdraw from the hotel.
3.1.7.3 Performance Bounds
The system shall support up to infinite simultaneous users against

the website/web server at any given time
The system will provide access to the database management
system with a latency of no more than 20 seconds.

Hotelreservationchapter3 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hotelreservationchapter3 2

Uploaded by

Copyright:

Available Formats

Chapter 3

3.1 Software Requirement Specification

To develop the Online Hotel Reservation, the work is started by gather

3.1.1.1 Goals and Objectives

The goal of the current system is to develop a Hotel

Online Hotel Reservation System Page 1

uses written descriptions as well as various types of modeling diagrams

A web based solution will be delivered so that users the system

The Hotel Reservation System Software is intended to provide a

3.1.1.2 Statement of Scope

The initial stage of project development is to find of

After defining the project scope, the matters that will

3.1.1.3 Software Context

There are many key component of hotel reservation. But the

In this project, the application developed is called online hotel

For the project facilities, laser printer is required to print the

3.1.1.4 Major Constraints

The hotel Reservation System will use Microsoft

3.1.2 Usage Scenario

3.1.2.1 User Profiles

The following definitions describe the actors in the system.

Admin An admin has the responsibility for registering a new customer

3.1.2.2 Use Case

The following is how the guest reserves to the hotel:

1. Log onto system

2. Display available rooms

3. Reserve for the room Available

Online Hotel Reservation System Page 4

3.1.2.2.1 Use-Case Diagram

3.1.2.2.1 Reception of user-case diagram

Figure 1.Reception of User-caser Diagram

Online Hotel Reservation System Page 5

3.1.2.2.2 Use-Case Description

Use-Case Search available room

Actors: Reception System

Preconditions The reception must insert the check in and checkout

Basic 1. The reception specify the check in and checkout

2. The reception adds room type.

3. Reception clicks on the button "Search".

4. The system will show the available rooms with

5. The reception chooses the rooms the customer

6. System will take the reception to the booking

Post The reception searched for the available rooms.

Use-Case Booking Details

Online Hotel Reservation System Page 6

Basic Scenario: 1. Check in date, check out date.

2. The reception fill the Guest Details

3. Then the reception must fill the guest

4. Then the reception clicks on "Save" to

5. The system will check the information

Online Hotel Reservation System Page 7

Use-Case Remainder Email

Preconditions: Reception must be able to access the

Reception clicks button "Remainder

Basic Scenario: 1. The reception clicks to view a list with

2. The reception clicks "Send" to send a

Online Hotel Reservation System Page 8

Online Hotel Reservation System Page 9

2. Modify the customer information.

Post Conditions: The customer details will be modified.

3.1.2.3 Special Usage Considerations

Online Hotel Reservation System Page 10

Billing fees cannot be change.