WEEK 7 (ERD NORMALIZATION)

May 2, 2009, 3:33 pm
Filed under: Uncategorized

This image is provided for the ERD to normalization

gambar20er From the image above, we can see the 2 errors are:
1. nocardinality between BAGIAN entity and PROYEK entity
2. no need relationship between TANGGUNGAN entity and PROYEK entity

Mapping of ERD image above:

NORMALIZATION OF MAPPING ABOVE :1NF/First Normal Form

At 1 NF

First Normal Form have the characteristics of each data file was formed in the flat, the data was in a record by one record and the value of the form field “atomic value”. There is no set of attributes that recurrent or re-valued attribute (multi value). Each field is only one definition, is not a collection of data that have meaning fork. Only one meaning only and is not a fraction also said the word so that means another.
First normal form does not permit:
- Composite attributes,
- Multi value attributes,
- Nested relations.

2NF/Second Normal Form

2nf-pegawai

2nf-bagian

2nf-proyek

2nf-tanggungan

2nf-kerja

Second Normal Form has to meet criteria of First Normal Form. Non-key attributes must depend on the function key, so for the Second Normal form must be pre-determined keys field. The key field must be unique and may represent other attributes that become members

3NF/Third Normal Form

To become a Third Normal form of the relationship should be in the form of second normal and not all the attributes do not have a primary relationship transitive. This means every non-key attributes must depend only on the primary key completely. Second Normal form of the example above, including of thrid Normal Because all the attributes that there depend on the full primer key.

Like this:

Be the first to like this post.

Kancutberbunga’s Blog

Categories

Archives

Links

Like this:

Leave a Reply Cancel reply

Follow “Kancutberbunga's Blog”