0% found this document useful (0 votes)
2 views4 pages

Data Base Assegnment

The document outlines a database design and modeling workshop assignment focused on normalization, progressing through various normal forms (1NF, 2NF, 3NF). It details the structure of tables for customers, orders, products, and order details, along with their functional dependencies and keys. The conclusion emphasizes that the database has been normalized to 3NF, minimizing redundancy and clarifying relationships between entities.

Uploaded by

mohomedriham10
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)
2 views4 pages

Data Base Assegnment

The document outlines a database design and modeling workshop assignment focused on normalization, progressing through various normal forms (1NF, 2NF, 3NF). It details the structure of tables for customers, orders, products, and order details, along with their functional dependencies and keys. The conclusion emphasizes that the database has been normalized to 3NF, minimizing redundancy and clarifying relationships between entities.

Uploaded by

mohomedriham10
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

Database Design ang Modelling Workshop

Assignment

 Student Name: WELAGAMAGE SAHAN LAKSHAN GAMAGE


 Student ID:
 Lecture name:

Normalization
Orde Custom Product Quanti Pric Order Address Contact
r ID er ty e Date
Name
101 PA kaya Pen 2 1.50 2025-01-20 121 Palm St, 666-789
NY
101 PA kaya Book 1 2.00 2025-01-20 121 Palm St, 666-789
NY
102 Junda Pencil 5 0.75 2025-01-21 456 Ough St, 666-987
CA
 Initial Dataset (UNF)

1NF
Ord Custom Product Quanti Pric Order Address Contact
er er ty e Date
ID Name
101 PA kaya Pen 2 1.50 2025-01-20 121 Palm St, 666-789
NY
101 PA kaya Book 1 2.00 2025-01-20 121 Palm St, 666-789
NY
102 Junda Pencil 5 0.75 2025-01-21 456 Ough St, 666-987
CA

2NF
Separate entities into tables:
 Customer Table
Customer Customer Adders Contact
ID Name
C001 PA kaya 121 Palam St, NY 666-789
C001 PA kaya 121 Palam St, NY 666-789
C002 Junda 456 Ough St, CA 666-987

 Order Table
Product Product Price
ID
P001 Pen 1.50
P001 Book 2.00
P001 Pencil 0.75
Order ID Customer Order
ID Date
101 C001 2025-01-
20
101 C001 2025-01-
20
102 C002 2025-01-
21

 Products Table

 Order Details Table


Order Detail ID Order ID Product ID Quantity
1 101 P001 2
2 101 P002 1
3 102 P003 5

3NF
All tables are in 3NF as no transitive dependencies exist.

Functional Dependencies and Keys


Functional Dependencies:
01.Customers: Customer ID Customer Name,
Adders, Contact.
02.Orders : OrderID CustomerID, Order Date.
03.Products: ProductID Product, Price.
04.OrderDetails: OrderDetailID OrderID ,ProductID ,
Quantity.
Keys:
 Primary Keys ( PK )
o Customers: CustomerID
o Orders : OrderID
o Products: ProductID
o OrderDetails: OrderDetailID

 Foreign Keys (FK)

o Orders: CustomerID ( FK referencing Customers )


o OrderDetails: OrderID (FK referencing Orders),
ProductID (FK referencing Products).

ER Diagram Below is the ER diagram illustrating


relationships among the entities.

ER Diagram
Conclusion The database has been normalized to
3NF , ensuring minimal redundancy and clear
relationships between entities. The functional
dependencies and keys have been clearly defined and
illustrated in the ER diagram.

You might also like