Scribd
Upload
63 views

2.2.3 Logical Data Structure 2.2.3.1 Entity Relationship Diagram

This document summarizes the logical data structure and procedures for a hotel reservation system. It includes an entity relationship diagram showing the relationships between tenants, operators, suppliers, cashiers and rooms. It also includes a data dictionary defining the fields in each database table. The document outlines the reservation procedures and policies for tenants, cash payments, and login security codes for employees. It analyzes problems through a fishbone diagram and requirement matrices. The goal is to have an automated system to monitor rooms, reservations and billing in real-time.

Uploaded by

Bunny Bhenj
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
63 views

2.2.3 Logical Data Structure 2.2.3.1 Entity Relationship Diagram

This document summarizes the logical data structure and procedures for a hotel reservation system. It includes an entity relationship diagram showing the relationships between tenants, operators, suppliers, cashiers and rooms. It also includes a data dictionary defining the fields in each database table. The document outlines the reservation procedures and policies for tenants, cash payments, and login security codes for employees. It analyzes problems through a fishbone diagram and requirement matrices. The goal is to have an automated system to monitor rooms, reservations and billing in real-time.

Uploaded by

Bunny Bhenj
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 7

2.2.

3 Logical Data Structure

2.2.3.1 Entity Relationship Diagram

CLIENT-OPERATOR-SUPPLIER

Tenant
Reserva Cashier
Name
tion
No.of Adults
No.of children
Vehicle
Plate No.

Room
Inform availability
current checking
available
rooms
SUPPLY

Verified
Room
Cashier List admin
Room No.
Amount
Floor
Occupant
2.2.3.2 Data Dictionary of ERD

Database Fields Data Types Description Sample


Name
Tenant Name Character This is for Juan Dela
Information No.of Adults Character applying for Cruz
No.of children Character reservation. 2
Vehicle Character 1
Plate No. Character Mazda 3
BNY004
Room List Room No. Character List of occupied 105
Amount Character and non 5,000
Floor Character occupied. 1
Occupant Character Juan dela
Cruz
Cashier Payment Character Information BDO
O.R. Number records about 1548889
payment.
Security Code Password Character Code to Log-In / 123
unique code for
each employee.

2.3 Policies and Procedure


2.3.1 Procedures

2.3.1.1 Context Diagram


Client /
Guest

Tenant’s

information
Tenant 0 Tenants Admin/
List
Monitori Cashier
Tenant’s
ng Billing
Payment
information System s
Tenant

Application form

2.3.1.1 Context Diagram


2.3.1.2 Process of Flow Diagram

Start

Tenant
Reservation

Verifying
Room not
Reservatio
n Available

FALSE

TRUE

APPLICATION
FORM

FALSE
Requiremen Reject
t Checking Application

TRUE

Input Reservation Payment


2.3.2 Policies
Employees should agree and understand that as a condition of their employment,
they are responsible for securing the company’s compute and information system against
unauthorized access and/or abuse. Any attempt to violate any provision of this policy will
result in disciplinary action.
Employees should agree and understand that they are also responsible for obeying
all regulations regarding the use of the company’s system and equipment. Whoever try to
attempt to break the policies through the Louise San Diego it may result to a criminal or
civil charges and fines and the company will cooperate fully in the information needed by
the authorities.

2.4 Problem Analysis

2.4.1 Fishbone Diagram


2.4.2 Problem and Requirements

Problem

Monitoring

Room List

Reservation

Requirements

We require the owner and the staff of the company to be knowledgeable in

computer. The company needs enough money for the requirements to be used in our

proposal automated system.


2.4.3 Requirements Feature Matrix

Features The System Allow the Records Records Admin


uses real admin to the Time the Name have
time and create and Date of the the
allows the delete and each tenat’s author
multiple edit employee/ who ity to
simulations employee user log-in make add
access and log- reservati tenat’
out on s in
the
datab
ase


Ability to
ADD and
DELETE
Employee
’s Record

 
Real Time


Manual
computati
on of
Tenat’s
based on
employee
s records


Time in
time-out
are
manually
recorded


Maintena
nce of
employee

You might also like