Database Normalization and Design

This assignment focuses on the concept of database normalization. It involves identifying functional, partial, and transitive dependencies within a dataset. The student is tasked with demonstrating these dependencies through diagrams and then proceeds to normalize the database into its first, second, and third normal forms. The assignment also includes the creation of a relational schema using MariaDB (2017) and an Entity Relationship Diagram (ER Diagram) using Oracle (2000). Finally, relevant references are provided for further understanding.

Normalisation
Student ID –
Student Name –
Subject Code -
Date -

Report
Dependency Diagram
Functional dependency is showing below-
Partial Dependency
FildProductName  FildProductCode
FildProductPrice  FidProductCode
FildVendorID  FildProductCode
FildVendorName  FildProductCode
FildPurchaseDate  FildInvoiceNumber
FildInvoiceDate  FildInvoiceNumber
FildQuantitySold  FildProductCode
FildQuantitySold  FildInvoiceNumber
Transitive Dependency
FildVendorName  FildVendorID

Normal Form Relations
First Normalised Tables
Second Normalised Tables

Third Normalised Tables
Third normalized tables follow the below rules-
- Records in the entities are identified by primary key.
- All fields depend upon the selected primary key.
- There is no transitive dependency existing in any table.

Relational Schema
(MariaDB 2017)

ER Diagram
(Oracle 2000)
References
Oracle (2000), Drawing the Entity Relationship Diagram, Retrieved from
http://docs.oracle.com/cd/A87860_01/doc/java.817/a81358/05_dev1.htm
MariaDB (2017), Relational Databases: Foreign Keys, Retrieved from
https://mariadb.com/kb/en/the-mariadb-library/relational-databases-foreign-
keys/