Scribd
Upload
4 views3 pages

Understanding Data Normalization and ER Models

The document discusses normalization as a data modeling technique aimed at eliminating redundancies in relational databases. It explains the Entity-Relationship Model (ERM) and its graphical representation through ER Diagrams, detailing entities, relationships, and attributes. Additionally, it covers the classifications of attributes and concepts such as functional dependency and partial functional dependency.

Uploaded by

ScribdTranslations
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views3 pages

Understanding Data Normalization and ER Models

The document discusses normalization as a data modeling technique aimed at eliminating redundancies in relational databases. It explains the Entity-Relationship Model (ERM) and its graphical representation through ER Diagrams, detailing entities, relationships, and attributes. Additionally, it covers the classifications of attributes and concepts such as functional dependency and partial functional dependency.

Uploaded by

ScribdTranslations
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Brasília May 31, 19

Prophet Ozias Lima dos Santos

1- What is normalization?
Normalization is a data modeling technique related to the relational model.
which aims to define a set of tables ready to be implemented
In a relational database, normalization serves to eliminate redundancies.

2- SEA and LAND


OMER known as Entity-Relationship Model is a conceptual model
used in software engineering to describe the objectives the 'Entities'
involved in a business domain, with their characteristics the 'Attributes' and
how they relate to each other (Relationships).

While the MER is a conceptual model, the Entity Diagram


Relationship (ER Diagram or also DER) is its graphic and main representation.
tool. In practical situations, the diagram is often considered synonymous with
model, since without a way to visualize the information, the model can
becomes too abstract to assist in the development of the system.

3–Entity, relationship, Attribute, and Tuple.


Entity - The objects or parts involved in a domain, also called
entities can be classified as physical or logical, according to their existence in
real world. Physical entities: they are those that are truly tangible, existing and visible in
real world, like a customer (a person, a company) or a product (a car,
a computer, an outfit).

Relationship-

One-to-one relationship: each of the two entities involved


must necessarily refer to only one unit of the other. For example, in a
resume database, each registered user can only have one
curriculum in the database, while each curriculum belongs to only one unique
registered user.
Relationship 1..n or 1..* (one to many): one of the entities involved can
referencing several units from the other, however, on the other side each of the several
referenced units can only be connected to one unit of another entity. For
For example, in a health plan system, a user can have several dependents.
but each dependent can only be linked to one main user. Note that we have
only two entities involved: user and dependent. What changes is the quantity.
of units/copies involved on each side.
N..N or *..* (many-to-many) relationship: in this type of relationship, each
entity, on both sides, can reference multiple units of the other. For
for example, in a library system, a title can be written by multiple authors,
at the same time that an author can write several titles. Thus, an object of
An author type can reference multiple objects of the title type, and vice versa.

4–Table and Records


5–Relational Database

A relational database is a storage mechanism that allows for


data persistence and optionally implement functionalities

6–Tool case

It is a tool that helps in defining a model as a representation,


frequently graphical of the components of a project, the main use of this
tools and the happiness with which it produces a diagram from the efforts of
modeling also has the advantage of documenting the system that is being
modeling.

What is the main rule of normalization?

It is to verify whether a certain field actually belongs to the table.

What is functional dependency?

It consisted of a restriction between two or more sets of attributes of the same


table or relationship.

9 - When does a partial functional dependency occur?

When a field or attribute that is not part of the primary key has a dependency
functionality of only some of the attributes that are part of the primary key

10–What are the classifications of attributes?

• Simple or atomic attribute: it is the attribute that is indivisible and has a meaning.
unique, like the RG or CPF of a person, these two examples show that both the
RG and CPF cannot be split into two other fields.

Composite attribute: it is an attribute that can be divided into several parts, a good
example is the address. We can split this attribute into: street, number, complement,
neighborhood.

• Single-valued attribute: it is an attribute that has only one value for the table,
Like a student's enrollment, this number cannot be repeated in the table.

You might also like