0% found this document useful (0 votes)
5 views15 pages

Normalization and ERD

The document presents a project proposal for a Billing Management System (BMS) for Limpiado Laundry Shop, detailing the database normalization process for various entities including Customer, Invoice, Service, Payment, Payment Method, Tax, User, Billing Cycle, and Reminder. It outlines the attributes of each entity, their dependencies, and the results of normalizing the database to the third normal form (3NF). Additionally, it includes sample data for each table and an entity relationship diagram (ERD).
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
0% found this document useful (0 votes)
5 views15 pages

Normalization and ERD

The document presents a project proposal for a Billing Management System (BMS) for Limpiado Laundry Shop, detailing the database normalization process for various entities including Customer, Invoice, Service, Payment, Payment Method, Tax, User, Billing Cycle, and Reminder. It outlines the attributes of each entity, their dependencies, and the results of normalizing the database to the third normal form (3NF). Additionally, it includes sample data for each table and an entity relationship diagram (ERD).
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/ 15

MCO 1

Milestone Two: Project Proposal

Billing Management System(BMS) Of Limpiado Laundry Shop In Poblacion 1,San


Jorge Samar

In Partial Fufillment of the Requirements in IT 102


Fundamentals of Database Systems
BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

By

JONAS DELA CRUZ CINCO


JAMBIE DONADELLO CODERA
ARIANNE HILO BULOS

Submitte to

NOIME MUJERES-MANTE
Instructor I

Date: June 03 2024


Database Normalization

1. CUSTOMER
 CUSTOMER_ID
 FNAME
 LNAME
 CONTACT
 ADDRESS
 PAYMENT_ID
 PAYMENT_METHOD_ID
 REMINDER_ID

First Normal Form (1NF) Dependency Diagram

1NF (CUSTOMER_ID,FNAME, LNAME, CONTACT, ADDRESS,


PAYMENT_ID,PAYMENT_METHOD_ID, REMINDER_ID)

PARTIAL DEPENDENCIES:

(CUSTOMER_ID →FNAME, LNAME, CONTACT, ADDRESS,


PAYMENT_ID,PAYMENT_METHOD_ID, REMINDER_ID)

TRANSITIVE DEPENDENCY:
(PAYMENT_ID→PAYMENT_METHOD_ID)

Second Normal Form (2NF) Conversion Results

Table name: CUSTOMER


CUSTOMER (CUSTOMER_ID,FNAME, LNAME, CONTACT, ADDRESS,
PAYMENT_ID,PAYMENT_METHOD_ID, REMINDER_ID)

TRANSITIVE DEPENDENCY
(PAYMENT_ID→PAYMENT_METHOD_ID)

Third Normal Form (3NF) Conversion Results

Table name: CUSTOMER


CUSTOMER (CUSTOMER_ID,FNAME, LNAME, CONTACT, ADDRESS,
PAYMENT_ID,PAYMENT_METHOD_ID, REMINDER_ID)

Table name: PAYMENT


PAYMENT (PAYMENT_ID,PAYMENT_METHOD_ID)

CUSTOMER TABLE
Customer_ID FName LName Contact Address Payment_ID Payment_ Reminder_ID
Method_ID
101 Cinco Jonas 09617803440 Brgy. 401 501 901
Sapinit

102 Bulos Arianne 09163087044 Brgy. 402 502 902


San
Juan

103 Codera Jambie 09814197155 Brgy. 403 503 903


San
Agustin
2. INVOICE
 INVOICE_ID
 DATE
 TOTAL_AMOUNT
 STATUS
 CUSTOMER_ID
 PAYMENT_METHOD_ID
 REMINDER_ID

First Normal Form (1NF) Dependency Diagram

1NF (INVOICE_ID, DATE,TOTAL_AMOUNT, STATUS, CUSTOMER_ID,


PAYMENT_METHOD_ID,REMINDER_ID)

PARTIAL DEPENDENCIES:
(INVOICE_ID →DATE, TOTAL_AMOUNT, STATUS)

TRANSITIVE DEPENDENCY:
(CUSTOMER_ID →PAYMENT_METHOD_ID, REMINDER_ID)

Second Normal Form (2NF) Conversion Results

Table name: INVOICE

INVOICE (INVOICE_ID,DATE, TOTAL_AMOUNT, STATUS)

TRANSITIVE DEPENDENCY
(CUSTOMER_ID →PAYMENT_METHOD_ID, REMINDER_ID)

Third Normal Form (3NF) Conversion Results


Table name: INVOICE
INVOICE (INVOICE_ID,DATE, TOTAL_AMOUNT, STATUS)

Table name: CUSTOMER


CUSTOMER (CUSTOMER_ID,PAYMENT_METHOD_ID, REMINDER_ID)

INVOICE TABLE
Invoice_I Date Total_Amoun Status Customer_I Payment_Method_ID Reminder_I
D t (Check D D
if paid
or
unpaid)
201 2024- 340.00 Paid 101 501 901
01-04
202 2024- 170.00 Unpaid 102 502 902
05-22
203 2024- 510.00 Paid 103 503 903
05-23

3. SERVICE
 SERVICE_ID
 PRICE
 INVOICE_ID
 USER _ID

First Normal Form (1NF) Dependency Diagram


1NF (SERVICE_ID, PRICE, INVOICE_ID, USER_ID)

PARTIAL DEPENDENCIES:
(SERVICE_ID →PRICE)

TRANSITIVE DEPENDENCY:
( INVOICE_ID→USER_ID)

Second Normal Form (2NF) Conversion Results

Table name: SERVICE

SERVICE (SERVICE_ID,PRICE)

TRANSITIVE DEPENDENCY
( INVOICE_ID→USER_ID)

Third Normal Form (3NF) Conversion Results

Table name: SERVICE


SERVICE (SERVICE_ID,PRICE)
Table name: INVOICE
INVOICE ( INVOICE_ID,USER_ID)

SERVICE TABLE
Service_ID Price Invoice_ID User _ID
301 340.00 201 701
302 170.00 202
303 510.00 203

4. PAYMENT
 PAYMENT_ID
 DATE
 AMOUNT
 PAYMENT_METHOD_ID

First Normal Form (1NF) Dependency Diagram

1NF (PAYMENT_ID, DATE, AMOUNT, PAYMENT_METHOD_ID)

PARTIAL DEPENDENCIES:
(PAYMENT_ID→ DATE, AMOUNT, PAYMENT_METHOD_ID)

Second Normal Form (2NF) Conversion Results

Table name: PAYMENT

PAYMENT (PAYMENT_ID, DATE, AMOUNT, PAYMENT_METHOD_ID)

Third Normal Form (3NF) Conversion Results


Table name: PAYMENT
PAYMENT (PAYMENT_ID, DATE, AMOUNT, PAYMENT_METHOD_ID)

PAYMENT TABLE
Payment_ID Date Amount Payment_Method_ID
401 2024-01-04 340.00 501
402 170.00 502
403 2024-05-23 510.00 503

5. PAYMENT_METHOD
 PAYMENT_METHOD_ID
 CASH
 CARD
 ONLINE_PAYMENT
 CUSTOMER_ID
First Normal Form (1NF) Dependency Diagram

1NF (PAYMENT_METHOD_ID, CASH, CARD, ONLINE_PAYMENT,


CUSTOMER_ID)

PARTIAL DEPENDENCIES:
(PAYMENT_METHOD_ID→ CASH, CARD, ONLINE_PAYMENT,
CUSTOMER_ID)

Second Normal Form (2NF) Conversion Results

Table name: PAYMENT_METHOD

PAYMENT_METHOD (PAYMENT_METHOD_ID, CASH, CARD,


ONLINE_PAYMENT, CUSTOMER_ID)

Third Normal Form (3NF) Conversion Results


Table name: PAYMENT_METHOD
PAYMENT_METHOD (PAYMENT_METHOD_ID, CASH, CARD,
ONLINE_PAYMENT, CUSTOMER_ID)

PAYMENT METHOD TABLE


Payment_Method_ID Cash Card Online_Payment Customer_ID
501 Paymaya 101
502 Cash 102
503 Cash 103

6. TAX
 TAX _ID
 NAME
 RATE

First Normal Form (1NF) Dependency Diagram

1NF (TAX _ID, NAME, RATE)

PARTIAL DEPENDENCIES:
(TAX _ID→ NAME, RATE)

Second Normal Form (2NF) Conversion Results

Table name: TAX

TAX (TAX _ID, NAME, RATE)


Third Normal Form (3NF) Conversion Results

Table name: TAX


TAX (TAX _ID, NAME, RATE)

TAX TABLE
Tax _ID Name Rate
601 Abby Rose Basilan 15%

7. USER
 USER _ID
 USERNAME
 PASSWORD
 ROLE
 PAYMENT_ID
 TAX _ID
 REMINDER_ID

First Normal Form (1NF) Dependency Diagram

1NF (USER _ID,USERNAME,PASSWORD,ROLE,PAYMENT_ID,TAX


_ID,REMINDER_ID)

PARTIAL DEPENDENCIES:
(USER _ID→USERNAME,PASSWORD,ROLE,REMINDER_ID)

TRANSITIVE DEPENDENCY:
( PAYMENT_ID→TAX _ID)

Second Normal Form (2NF) Conversion Results

Table name: USER


USER (USER _ID,USERNAME,PASSWORD,ROLE,REMINDER_ID)
TRANSITIVE DEPENDENCY
( PAYMENT_ID→TAX _ID)

Third Normal Form (3NF) Conversion Results

Table name: USER


USER (USER _ID,USERNAME,PASSWORD,ROLE,REMINDER_ID)

Table name: PAYMENT


PAYMENT ( PAYMENT_ID,TAX _ID)

USER TABLE
User Username Password Role Payment_I Tax Reminder_ID
_ID D _ID
701 Dona 87654321 Employee 401 601 901
Delarmente

8. BILLING_CYCLE
 BILLING _CYCLE_ID
 NAME
 FREQUENCY
 USER _ID
 CUSTOMER_ID
First Normal Form (1NF) Dependency Diagram
1NF (BILLING _CYCLE_ID,NAME,FREQUENCY,USER_ID,CUSTOMER_ID)

PARTIAL DEPENDENCIES:
(BILLING _CYCLE_ID→NAME,FREQUENCY,USER _ID,CUSTOMER_ID)

Second Normal Form (2NF) Conversion Results

Table name: BILLING _CYCLE

BILLING _CYCLE (BILLING


_CYCLE_ID,NAME,FREQUENCY,USER_ID,CUSTOMER_ID)

Third Normal Form (3NF) Conversion Results

Table name: BILLING _CYCLE


BILLING _CYCLE (BILLING
_CYCLE_ID,NAME,FREQUENCY,USER_ID,CUSTOMER_ID)

BILLING CYCLE TABLE


Billing Name Frequency User _ID Customer_ID
_Cycle_ID
801 Dona 8 Hours 701 101
Delarmente

9. REMINDER
 REMINDER_ID
 DATE
 MESSAGE
 CUSTOMER_ID
 INVOICE_ID
 PAYMENT _ID
 BILLING_CYCLE_ID

First Normal Form (1NF) Dependency Diagram

1NF(REMINDER_ID,DATE,MESSAGE,CUSTOMER_ID,INVOICE_ID,PAYMENT
_ID,BILLING_CYCLE_ID)

PARTIAL DEPENDENCIES:
(REMINDER_ID→ DATE,MESSAGE)

TRANSITIVE DEPENDENCY:
(CUSTOMER_ID→ INVOICE_ID,PAYMENT _ID,BILLING_CYCLE_ID)

Second Normal Form (2NF) Conversion Results

Table name: REMINDER

REMINDER (REMINDER_ID, DATE,MESSAGE)

TRANSITIVE DEPENDENCY
(CUSTOMER_ID→ INVOICE_ID,PAYMENT _ID,BILLING_CYCLE_ID)

Third Normal Form (3NF) Conversion Results


Table name: REMINDER
REMINDER (REMINDER_ID, DATE,MESSAGE)

Table name: CUSTOMER

CUSTOMER ( CUSTOMER_ID, INVOICE_ID,PAYMENT


_ID,BILLING_CYCLE_ID)

REMINDER TABLE
Reminder_ID Date Message Customer_ID Invoice_ID Payment Billing_Cycle_ID
_ID
901 2024- Good day 101 201 401 801
01-04 ma’am/sir your
laundry is
done.

902 2024- Good day 102 202 402


05-22 ma’am/sir your
laundry is
done.

903 2024- Good day 103 203 403


05-23 ma’am/sir your
laundry is
done.
ENTITY RELATIONSHIP DIAGRAM (ERD)

You might also like