Normalization Sicheco123
Normalization Sicheco123
In IAD-413
BSOM 4F
Submitted by:
Lovely B. Sicheco
Submitted to:
A logical data model provides more structure and relationship details. It focuses on data connections
without being specific to a database system.
A physical data model is the implementation of the logical model in a database system. This includes
creating tables, columns, indexes, and constraints to organize data effectively.
Think of it like planning a house: conceptual model as blueprint, logical model as detailed floor plan,
physical model as building with specific materials.
3. Types of Normalization
Normalization is a process used in database design to make data more
organized and efficient. It helps to reduce duplication and improve how
data is stored.
There are different levels of normalization, each with its own goals and
guidelines.
First Normal Form (1NF) focuses on getting rid of repeating groups and
making sure that each piece of data is unique.
For example, instead of having separate columns for different phone
numbers, a table in 1NF would have just one column for all phone
numbers.
Second Normal Form (2NF) works to remove partial dependencies by
ensuring that non-primary attributes rely on the entire primary key. In a
table with a primary key made up of multiple columns, all non-key
attributes should be dependent on all of those columns, not just some of
them.
Third Normal Form (3NF) targets transitive dependencies, where non-
primary attributes should directly rely on the primary key. If attribute A
depends on B and B depends on C, then A should directly depend on C.
Boyce-Codd Fourth Normal Form (BC4NF) is a stricter version of 3NF,
where every determinant must be a candidate key. This means that for
any relationship A → B, A must be a super key.
Fifth Normal Form (5NF) focuses on removing multivalued
dependencies, ensuring that no table has two or more independent
multivalued dependencies. Attributes with multiple values should be split
into different tables.
Sixth Normal Form (6NF) aims to remove join dependencies, making
sure that a table cannot be broken down into smaller tables without losing
information. This ensures that data can be accurately reconstructed from
smaller tables without any duplication.