Online Shop

Info

Microsoft Access Data Model Example

Hotel Room Booking Scenario

The following data model is designed to hold information relating
to a Hotel Room Booking System.

For this scenario we need to define the following facts:

These facts define the requirements which the Database must meet
and should be agreed between the Database User and the Database Designer
prior to physical creation.

A local hotel needs a system that keeps track of its bookings (future,
current and archived), rooms and guests. A room can be of a particular
type and a particular price band. Room prices vary from a room to
a room (depending on its type, available facilities, band, etc.) and
from a season to a season (depending on the time of the year).

A room booking can include more than one room and more than one customer.

The draft facts have been defined as:

The Entities required should include:

Customers

Guests

Rooms

Bookings

Payments

Room Types

Price Bands

Room Facilities

The Entities are related as follows:

A Customer can make one or many Bookings.

A Booking can be for one or many Guests - the Guest is not necessarily
the person who makes the Booking.

A Room can be on one or many Bookings.

A Room may have many different Room Facilities.

When asking questions of the database we may need to know:

How many rooms are currently available for booking?

What facilities are available in particular rooms?

Which Guests are booked in this week?

The following data model allows these questions to be answered and
allows the information contained above to be stored logically and
in a structured manner.