E-Booking

H otelM anagem ent System

By Majed Assafiri and Ali Taher

Th e org an ization al S tru ctu re

Add your first bullet point here
Add your second bullet point here
Add your third bullet point here

S ystem R eq u ests for th e E-B ookin g

Project Sponsor: Mike Stand, the CIO of the Las Vegas Hotel.

Business Need: E-bookings will increase the Hotel profit and will
increase its resources, and also will increase the efficiency of the
employees and minimize the possibility of errors.

B u sin ess req u irem en ts:

The IT department would be able to know the percentage of profit
and the problems and issues that may encounter in different
situations and circumstances, by that we can reduce problems by:
To make it easier to book for customers rooms with different options
Wider variability of different sizes and prices of rooms to choose
from.
Ability to share data between different departments to make the
work more valuable and better.
Using technology and advertisement so that customers can get
value of that the hotel services.

S p ecial Issu es
But there will always be some issues that can be caused by wrong
data entered to
the system which will be the cause of GIGO informations. And also
the system will
need maintenance every couple of months. And we have to finish this
system
within the next 3 months.

M ethodology U sed

Phased D evelopm ent M ethodology

B u sin ess P rocess

Because the e-booking will be new, so we will be following the BPR to
maximize the business value as much as we can, but this process is
definitely risky and costly but we need to follow the process that adds
value the most to the hotel which is the re-engineering process.

E-b ookin g system Featu res an d in form ation s

Feasib ility S tu d y
We are going to study two major components of the feasibility study;
the organizational and technical feasibility. To be able to reach a good
decision making, we should identify the risks in the technical
component

Tech n ical Feasib ility:

We should look if the analysts and web designers are familiar with
such a portion of the business, if not the risk would be high
Less familiarity with technology of such a system results in a high
risk of failure.
The system scope must fit the business need, if this doesnt occur,
high risk of letdown.
The online system should be compatible i.e. having the availability
to be integrated with our current booking system.

O rg an ization al Feasib ility:

The HMS should align the goals of the business purpose, i.e. Ebooking should be capable of facilitating the way the business
operate and providing information needed to keep updated with all
the operating system of the hotel and increase profit as well as
winning the loyalty of the customers

Econ om ic Feasib ility:

Tim e Estim ation

Complexity
Descri
Total
Low
Mediu
ption Numbe
m
r
Inputs 35
10*4
5*8
Outpu 10
3*3
4*7
ts
Querie 0
0*6
0
s
Files
11
5*6
5*14
Progra 3
0*4
0*9
m
interfa
ce
Total Unadjusted Function
Points

High

Total

5*5
1*4

105
41

0*11
2*8

100
16

262

Tim e Estim ation

Complexity due to Integration
Data Communications
Heavy use configuration
Transaction rate

5
2
0

End-user efficiency
Complex processing
Installation ease
Multiple sites
Performance
Distributed functions
Online data entry
Reusability
Operational ease

0
0
2
4
2

Extensibility

Total Processing Complexity (PC):

Adjusted Project Complexity = 0.65 +

(0.01*23) = 0.88
Total Adjusted Function Points= 0.88 *
374 = 329.12
Using VB as a language for programming

1
3
2
1

23

329.12*30= 9873
Efforts in person/month= 1.4 * 9.873=13.822
person month which means we need 14 persons per
month.
Schedule Time duration= 3*(13.822) ^ (1/3) =
3.461233 months approximately.

P roject S ch ed u lin g
Project Timeline:

P roject Tasks

P roject C alen d ar

R isk Id en tif i
cation an d P ossib le A ction s
RISK

PROBABILITY

EFFECT

ACTION

ORGANIZATIONAL
FINANCIAL PROBLEM
AFFECTING THE
BUDGETING.

NO SKILFUL AND
EXPERIENCED STAFF FOR
REQUIRED NEEDS.

KEY STAFF ARE ILL AT

CRITICAL TIMES OF THE
PROJECT
DIFFERENT MANAGEMENT
REQUIRES DIFFERENT
NEEDS

Low

Catastrophic

Complete the base functions of

the system and leave the other
options for later on.

High

Catastrophic

Assign experts to give training

sessions for our staff.

Moderate

Serious

Low

Serious

Moderate

Tolerable

Expand the time needed to

finish the program or oblige an
overtime work.

Convince the new

management with the current
project.

Overtime work or expanding of

time needed.

High

Serious

Train the system users.

Moderate

Low

Tolerable

Serious

Ask for more budgeting or do

only base functions of the
project.
Keeps old system working
while new system is available
until staffs is good at it.

UNDERESTIMATION OF TIME
REQUIRED FOR THE
PROJECT

SYSTEM USERS CANNOT

UNDERSTAND THE NEW
SYSTEM.

UNDERESTIMATION OF
PROJECT SIZE

REQUIRED TRAINING FOR

STAFF NOT AVAILABLE.

E-Booking analysis and design

we focused the most on the JAD Session, because it JAD decreases time and
costs associated with requirements elicitation process. During 2-4 weeks
information not only is collected, but requirements, agreed upon by various
system users, are identified. Moreover, more importantly is that Easy
integration of CASE tools into JAD workshops improves session productivity
and provides systems analysts with discussed and ready to use models. So
using the JAD we can gather the informations and the requirements with the
most effective way.

S ystem R eq u irem en ts
Flexibility
Control Efficiently
Managing Special offers
Efficiency improvement
Better Accuracy
Minimize room shortage and usage

Fu n ction al R eq u irem en ts
The system shall record reservations.
The system shall record the customers first name.
The system shall record the customers last name.
The system shall record the room number.
The system shall display the default room price.
The system shall check-in customers.
The system shall checkout customers.
The system shall record customer feedback.

N on fu n ction al R eq u irem en ts
Portability:
The Hotel Management System shall run in any Microsoft Windows
environment that contains Java Runtime and the Microsoft Access
database.
Maintainability:
The Hotel Management System is being developed in Java. Java is an
object oriented programming language and shall be easy to maintain.
Security:
Access to the various subsystems will be protected by a user log in
screen that requires a user name and password.
Availability:
The system shall be available during normal hotel operating hours.
Reliability:
Specify the factors required to establish the required reliability of the
software system at time of delivery.

U se C ase Id en tif i
cation an d d escrip tion
Use Case Name: Make
Reservation

ID: 1

Priority: High

Primary Actor: Client

Description: Client Reserve a room at the hotel
Trigger: Client Accesses online system or receptionist
Type: External
Relationships:
Association:
Include:
Extend:

Flow of Event:
1. Client enters a gateway for hotels.
2. Client selects hotel, arrival and departure dates, and room type.
3. System provides availability and price.
4. Client accepts and asks for a room.
5. Client provides name and post code.
6. Client provides his email address.
7. System makes a reservation and allocates a reservation number
8. System shows reservation number to client.
9. System creates and sends a confirmation to client by email.

Exceptions:
1. Required room type not available
2. Client declines offer
3. Client is registered and his info already on file

Use Case Name: Make

ID: 2
Priority: High
Reservation (Offline)
Primary Actor: Receptionist
Description: Receptionist Reserve a room For a client
Trigger: Receptionist clicks on the E-booking Icon
Type: External
Relationships:
Association:
Include:
Extend:

Flow of Event:
1. Receptionist Enters the system
2. Receptionist Check if Room Available
3. Receptionist Books Room
4. Receptionist Receive acceptance from Client
5. Receptionist Generate Bill/Invoice For Client
6. Receptionist Enters Client Informations (Phone No, Address)
7. Receptionist Exit Client Window.

Exceptions:
1. Client Cancels Reservation Order
2. Client Extend Reservation duration

Use Case Name: Check-Out

ID: 3

Priority: High

Primary Actor: Receptionist

Description: Receptionist Checks The Client Out
Trigger: Receptionist clicks on the E-bookings CHECK-OUT
Type: External
Relationships:
Association:
Include:
Extend:

Flow of Event:
1. Receptionist Get a request from the client to check-out
2. Receptionist Enters The check-out section in the system
3. Receptionist Search for the client name/ID
4. Receptionist records check-out date
5. Receptionist Update Client information
6. Receptionist Update Room number availability
7. Receptionist exit the client data section.

Exceptions:
N/A

U M L A n alysis (D iag ram s)

Sequence Diagram for online e-booking

U M L A n alysis (D iag ram s)

Sequence Diagram for offline Reservation E-booking

U M L A n alysis (D iag ram s)

State Chart for E-Booking

U M L A n alysis (D iag ram s)

Use Case Diagram For E-booking

A ctivity D iag ram For th e E-b ookin g S ystem

C lass D iag ram

The End!