Scribd
Upload
55 views4 pages

Liquor Case Study

This document outlines the normalization process for a database to manage a motel/mini hotel. It includes 10 business rules, sample data in first normal form, dependency diagrams showing the conversion to second and third normal forms, an entity-relationship diagram, and a data dictionary defining the tables and attributes. The goal is to normalize the data into multiple tables to eliminate data anomalies and dependencies.

Uploaded by

Edward
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
55 views4 pages

Liquor Case Study

This document outlines the normalization process for a database to manage a motel/mini hotel. It includes 10 business rules, sample data in first normal form, dependency diagrams showing the conversion to second and third normal forms, an entity-relationship diagram, and a data dictionary defining the tables and attributes. The goal is to normalize the data into multiple tables to eliminate data anomalies and dependencies.

Uploaded by

Edward
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Edward Darren B.

Navarro DBMS Case Study


BSIT-TSM-REQUESTED MOTEL/ MINI HOTEL MANAGEMENT

Table of Contents
Sections
1 BUSINESS RULES
2 NORMALIZATION PROCESS
2.1 REPORT LAYOUT (MANUAL)
2.2 TABLE IN 1ST NORMAL FORM
2.3 1st NORMAL FORM DEPENDENCY DIAGRAM (1NF)
2.4 2nd NORMAL FORM CONVERSION RESULTS (2NF)
2.5 3rd NORMAL FORM CONVERSION RESULTS (3NF)
3 ENTITY-RELATIONSHIP DIAGRAM (ERD)
4 DATA DICTIONARY
5 UML CLASS DIAGRAM

Section 1. BUSINESS RULES

BR# BUSINESS RULE DESCRIPTION


1 Customers must show valid ID’s
2 Each room can only accommodate up to 3 persons
3 Customers must surrender at least 1 valid ID before
going to their rooms
4 Before accommodating, rooms must be cleaned by
staff
5 Staff must keep proper sanitization of rooms
6 If the customer failed to leave on time they are going
to be asked for an extra fee
7 Customers must pay first before getting
accommodated
8 Reservations need a down payment
9 Down payments of customers are non-refundable
10 Prices are fixed even if the customers are late

Section 2. NORMALIZATION PROCESS

Section 2.1. Report Layout (Manual)


CUST_ID CUST_FNAME CUST_LNAME CUST_STAY RM_ID RM_PRICE RM_STATUS

Section 2.2. Table in First Normal Form

CUST_ID CUST_FNAME CUST_LNAME CUST_STAY RM_ID RM_PRICE RM_STATUS


1 EDWARD NAVARRO 3 DAYS 1 800/night OCCUPIED
2 KIM SANTIAGO 1 DAY 2 800/night OCCUPIED
3 AMOS CORTEZ 2 DAYS 3 800/night OCCUPIED
4 MICHAEL GONZALES 7 DAYS 4 800/night OCCUPIED
5 NONE 5 800/night VACANT
6 NONE 6 800/night VACANT

Section 2.3. First Normal Form Dependency Diagram (1NF)

CUST_ID CUST_FNAME CUST_LNAME CUST_STAY RM_ID RM_PRICE RM_STATUS

PARCIAL DEPENDENCY

Section 2.4. Second Normal Form Conversion Results (2NF)


TABLE NAME:Transaction

CUST_ID CUST_FNAME

CUST_ID CUST_NAME CUST_LNAME CUST_STAY

CUST_STAY RM_ID RM_STATUS


Section 2.5. Third Normal Form Conversion Results (3NF)

CUST_ID CUST_NAME CUST_ID CUST_NAME CUST_STAY

RM_ID RM_STATUS
CUST_ID CUST_STAY RM_ID

Section 3. ENTITY- RELATIONSHIP DIAGRAM

CUSTOMER PRODUCT
PK Cust_id
PK RM_ID
Cust_fname RM_PRICE
Cust_lname
RM_STATUS

ASSIGNMENT
Transaction
PK Cust_id
RM_price
Rm_id
Cust_stay
Section 4. DATA DICTIONARY

NAME DATA TYPE Constrain Description


Cust_id int Primary Key Customer Id
Cust_fname varchar Not Null Customer First
Name
Cust_lname Varchar Unique Key Customer Last
Name
Cust_stay Varchar Unique Key Customer Stay
Rm_id Int Null Room Id
Rm_price Int Not Null Room Price
Rm_status varchar Not Null Room Status

You might also like