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

Normalization Sicheco123

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)
27 views4 pages

Normalization Sicheco123

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

ASSIGNMENT

In IAD-413
BSOM 4F

Submitted by:

Lovely B. Sicheco

Submitted to:

Sir. Mauro C. Tolentino

November 19, 2024


1. Types of Associations
Associations refer to the relationship between two data items, A and B.
There are two types of associations: one-association and many-association.
One-association means that for every value of data item A, there is only
one corresponding value of data item B. This means that if you know the
value of A, you automatically know the value of B. For example, if A
represents a student's ID number, then the corresponding B could be the
student's name. Each student ID has only one name associated with it.
Many-association, on the other hand, means that for a given value of data
item A, there can be one or more corresponding values of data item B. This
means that one value of A can be linked to multiple values of B. For instance,
if A represents a book title, then the corresponding B could be the authors of
the book. One book title can have multiple authors associated with it.
In a database, relationships between tables help organize and connect data.
One type of relationship is a one-to-one relationship, where each record in
one table is linked to only one record in another table. For example, in a
school database, each student has a unique student ID that is assigned to
only one person.
Another type of relationship is a one-to-many relationship, where one
record in a table can be connected to multiple records in another table. For
instance, in a business database, the Customer ID in the Orders table can
match with multiple Customer IDs in the Customers table, indicating that one
customer can have multiple orders.
Lastly, a many-to-many relationship occurs when multiple records in one
table are linked to multiple records in another table. For example, in a retail
database, customers can purchase different products, and products can be
bought by many customers, creating a many-to-many relationship between
the customers and products tables.

2. What is Data Models? Name the Three types of data models.


Data models refer to the organization, documentation, and definition of data
within a database. They standardize the system by defining elements like
associations, entities, and requirements. These models help in structuring
data for easy storage, access, and management.
There are three main types of data models that are commonly used in
database management:
A conceptual data model is a big picture view of data in a business context. It shows what the data
represents without technical storage details.

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.

You might also like