Você está na página 1de 29

Resort Amenities

Management,
Billing and
Collection System
(RAMBCS)
Project Team Members:
Buco, Nhoriel John P.
Cruz, Eleiu Sam F.
Hornilla, Joel, S. A.
De Castro, Michael Lorenz C.
Tingal, Fritzie Yvonne E.
BSIT 3-2D

Page 1 of 29

Chapter 1 Abstract/Overview
1. Introduction
The resort offers reservation for cottages and amenities, it also offers
function halls for all occasions such as weddings, birthdays, baptismal,
anniversaries and debut. The existing reservation system is done through
phone calls and immediately records the data from the customer in a
simple logbook.
The resort experienced some problems in security, for the log book can
be accessed by anyone. And there is no centralized monitoring of cottages
and rooms which there can be a duplication of a certain reservation for a
specific amenity.
The Resort Amenities Management, Billing and Collection System will
provide solutions in the said problems.
2. Business case
2.1.

Project Goal
The developers aim to provide an automated and efficient system that will
manage information and company resources. The developers will create
an organized reservation system that will satisfy the customer needs and
improve the billing of services and collection of payment. The project will
promote the use of computer in processing and storing of information.

2.2.

Project Objective
Specific Objectives:

2.3.

To
To
To
To

create a database to facilitate storing of information


highly integrate data.
easily determine the available amenities in the said facility
create a back-up of files in every successful transaction.

Assumptions
The assumptions for this project are as follows:

2.4.

Unexpected risks will be managed accordingly.


Users can easily adopt with the system
The client will provide adequate resources for the system. Once
implemented.
Constraints
Page 2 of 29

Time Time will be consumed in addressing problems that are new to


the project team such as studying new techniques to develop the
system.
Limited Knowledge Due to confidentiality, the client refuses to
disclose any vital data.

3. Methods Used in the study


Iterative waterfall model
This model is said to be variant waterfall model. It attempts to
overcome the limitations of the original waterfall model by adding an
iterative loop to the end of the cycle. In order to keep up with changing
requirements, the analysis phase is revisited at the end of the cycle and
the process starts over again

We used the method stated above for when the system is finished and
there are some things that the client wants to add. It can be edited again by
doing the steps again in order to keep up with the clients changing
requirements. It will continue to loop until the client is satisfied with the
proposed system.

Page 3 of 29

Chapter 2 Functional Specification Reports


1. Data Requirements
1.1.
Forms
1.1.1.List and description of Forms
No.
1

Name of
Form
Reservation Slip

Voucher Reservation

Acknowledgement Receipt

Description
A form that includes all the
reservation details from the guests
A form that lets the customer know
the breakdown of his transaction
reservation, and the fee he needs
to pay in a limited time.
A form that was given to the
customer to testify that he already
paid the said amount indicated in
the voucher reservation form.

1.1.2.Layout of Forms
1.1.2.1
Reservation Slip

Page 4 of 29

1.1.2.2
Voucher Reservation

1.1.2.3
Acknowledgement Receipt

Page 5 of 29

1.2.
Reports
1.2.1.List and description of Reports
No.
1

Name of
Report
Official Receipt

Cash Book

Inventory
Report

Reservation
Report

Description

User

Frequency

A written acknowledgment that a


specified article or sum of money
has been received. The official
receipt records the purchase of
services being earned by the
customer.
A financial journal that contains all
cash receipts and payments in the
resort.
A report about the amenities that
has been used, returned and paid.
It also includes the remaining
quantity of the said amenity.
A summary report about the profits
made from reservations.

Customer

After the
event

Cashier

Monthly

Front Desk

Every Day

Front Desk

Monthly

1.2.2.Layout of Reports
1.2.2.1
Official Receipt

Page 6 of 29

1.2.2.2
Cash Book

1.2.2.3

Page 7 of 29

Inventory Report

1.2.2.4
Reservation Report

2. Policies and Procedures


2.1.
Procedures
2.1.1.Context Diagram
Page 8 of 29

2.1.2.Level 1 DFD

Page 9 of 29

2.1.3.Level 2 DFD

Page 10 of 29

2.2.

Policies
Page 11 of 29

2.2.1.Business Requirement

Business Requirement ID
BREQ1
BREQ2
BREQ3

BREQ4

Description
Cashiers must send summary reports
about the transactions made monthly.
Receptionist should give vouchers on
every reservation of each customer.
Receptionist should give reports on the
reservations that has been availed and
the reservations that has not been
availed.
Reservation fee is the 50% of the total
payment.

2.2.2.Business Rules
Business Rule ID
BRULE1
BRULE2

BRULE3

BRULE4

Description
The reservation fee must be paid 5
days before the arrival date.
In terms of cancellation, there is no
refund if youve already paid the
Reservation fee and cancelled by the
guest later on.
In terms of extension, the cottage and
amenities is billed per hour distinctly of
their kind.
The payment of billing is done after all
the services acquired of the customer is
finalized.

Page 12 of 29

3. Problem Analysis
3.1.
Fishbone Diagram

3.2.

Conclusion and Recommendation

After studying the business' processes, we have concluded several problems


such as slow processing of transaction especially in reservation where there is no
centralized monitoring of cottages and rooms in which it can really be hard to tell
the customer if their reservation is accepted or not. And the unorganized
information of the rooms, cottage and amenity status. With this information, we
concluded that a system might be a big help in this business. We recommend a
system that includes computerized process of resort management that will be
beneficial to the business. A system that will be more useful and efficient than
the manual process. Some information will be accurate and making it reliable.

Page 13 of 29

Chapter 3 Proposed System Definition


1. Functional Specification
1.1.
System Boundaries
1.1.1.Systems Use Case Diagram

1.1.2 Detailed Use Case Diagram


Page 14 of 29

1.1.2.1 Accept Reservation

1.1.2.2 Registration

1.1.2.3 Provide Amenities

1.1.2.4 Billing

Page 15 of 29

1.1.2.5 Accept Payment

1.1.2.6 Transfer

1.1.2.System Flow
1.1.1.3.1 Accept Reservation
Page 16 of 29

1.1.1.3.2 Registration

Page 17 of 29

1.1.1.3.3 Provide Amenities


Page 18 of 29

1.1.1.3.4 Billing

1.1.1.3.5 Accept Payment

Page 19 of 29

1.1.1.3.6 Transfer

Page 20 of 29

2. Technical Specification
2.1.
Domain Object Modeling
2.1.1.Data Dictionary of Classes
Page 21 of 29

Class
Guest

Description
All information about the
guest is specified here.

Reservation

Use to record all the


details about Reservation

Res_Details

Used to connect the


Reservation and
Accommodation table.

Accommodation

Used to record all the


details for the
Accommodation

Service_Received

Used to connect the


Reservation and Amenity
table.
Use to record all details
for Amenity

Amenity

Shift_Rate

Used to record details for


Shift

Discount

Use to record all details


for the Items

Payment

Use to record all the


details for payment

Accommod_Type

Used to record the details


for Accommodation Type

Attributes
GuestID
LastName
FirstName
MiddleName
Address
ContactNo
EmailAddress
ReservationID
EDA
ETA
EDD
ETD
GuestID
Res_ID
Acco_Id
NoOfChildren
NoOfAdult
AccoID
AccoName
ATypeID
Capacity
Date
Status
ReservationID
AmenityID
Quantity
AmenityID
AmenityName
ChildRate
AdultRate
ShiftID
TimeStart
TimeEnd
AdultRate
ChildRate
DiscountID
DiscountName
Discount
MiniTotal
PaymentID
TotalAmount
PaymentMode
ReferenceNo
ATypeID
Name

Page 22 of 29

2.1.2.

Final Class Diagram

Page 23 of 29

2.2.
Database Design
2.2.1.Database Schema

2.2.2.Data Dictionary
Table name: Guest
Table Description: Used to record all the information about the customer.
Related To: Reservation
ID
PK

Field
GuestID
GuestLastNam
e
GuestFirstNam
e
GuestMiddleNa
me
GuestAddress
GuestContactN
o
GuestEmail

Description
Unique ID for
each Guest
Last Name of
the Guest
First Name of
the Guest
Middle Name
of the Guest
Location of
the Guest
Contact
number of the
Guest
Email Address
of the Guest

Data Type
int

Length
5

Varchar

30

Varchar

30

Varchar

30

Varchar

30

Varchar

30

Varchar

30

Page 24 of 29

Table name: Reservation


Table Description: Use to record all the details about Reservation
Related To: Res_Details, Payment, Service_Received
ID
PK

Field
ReservationID

EstimatedDateArriv
al
EstimatedTimeArriv
al
EstimatedDateDepa
rture
EstimatedTimeDepa
rture
FK

GuestID

Description
Unique ID for
each
Reservation
Arrival Date
of the Guest
Arrival Time
of the Guest
Departure
Date of the
Guest
Departure
Time of the
Guest
Unique ID for
each Guest

Data Type
int

Length
5

date

10

date

10

date

10

date

10

int

Table name: Accommodation


Table Description: Used to record all the details for the Accommodation
Related To: Res_Details, Accommod_Type, OffMarketStatus
ID
PK

Field
AccoID

AccoName

AccoType

Capacity
Rate

Status

Description
Unique ID for
each
Accommodatio
n
Name of
Accommodatio
n
Type of
Accommodatio
n
Person
Capacity
Rate of
Accommodatio
n
Status of
Accommodatio

Data Type
int

Length
5

Varchar

30

Varchar

30

Int

10

Int

10

Varchar

30

Page 25 of 29

Table name: Res_Details


Table Description: Used to connect the Reservation and Accommodation table.
Related To: Reservation, Accommodation
ID

Field
ReservationID

AccoID

NoOfChildren
NoOfAdults

Description
References to
Reservation
table
References to
Accommodatio
n table
Children Count
Adult Count

Data Type
int

Length
5

Int

int
int

10
10

Table name: Service_Received


Table Description: Used to connect the Reservation and Amenity table.
Related To: Reservation, Amenity
ID

Field
ReservationID

AmenityID

Quantity

Description
References to
Reservation
table
References to
Accommodatio
n table
Quantity of
the said
Amenity

Data Type
int

Length
5

Int

int

10

Data Type
int

Length
5

Table name: Amenity


Table Description: Use to record all details for Amenity
Related To: Billing
ID
PK

Field
AmenityID

Description
Unique ID for

Page 26 of 29

AmenityName
ChildRate
AdultRate
With Detail?
Capacity

each Amenity
Name of the
Amenity
Rate for
Children
Rate for Adults
To check if its
Package or not
Capacity of
the said
Amenity

Varchar

30

Varchar

10

Varchar
boolean

10
5

int

10

Data Type
int

Length
5

Date/time

10

Date/time

10

Int

10

int

10

Table name: Shift_Rate


Table Description: Used to record details for Shift
Related To: Reservation
ID
PK

Field
ShiftID
TimeStart
TimeEnd
RateAdult
RateChild

Description
Unique ID for
each Shift
Start Time of
Shift
End Time of
Shift
Rates for
Adults
Rates for
Children

Table name: Items


Table Description: Use to record all details for the Items
Related To: ItemType, Amenity, AmenityDetail
ID
PK

Field
ItemID
ItemName
Description
Quantity

Description
Unique ID for
each Item
Name of Item
Description of
Item
Item Count

Data Type
int

Length
5

Varchar
Varchar

30
30

Int

10

Page 27 of 29

Table name: Discount


Table Description: Use to record all details for Discount.
Related To: Payment
ID
PK

Field
DiscountID
DiscountName
MinTotal

Description
Unique ID for
each Discount
Name of
Discount
Minimum total
to have a
discount

Data Type
int

Length
5

Varchar

30

Int

10

Table name: Payment


Table Description: Use to record all the details for payment
Related To: Billing
ID
PK

Field
PaymentID
TotalAmount
PaymentMode
ReferenceNo

Description
Unique ID for
each Payment
Total Amount
of Payment
Mode of
payment
Voucher
number

Data Type
int

Length
5

Int

10

varchar

30

Int

10

Table name: Accommod_Type


Table Description: Used to record the details for Accommodation Type
Related To: Accommodation
ID
PK

Field
ATypeID

ATypeName

Description
Unique ID for
each
Accommodatio
n Type
Name of
Accommodatio

Data Type
int

Length
5

Varchar

30
Page 28 of 29

n Type

Page 29 of 29