From the picture above we see there is an awkwardness that is on:
1. kardinalitas part of the project
2. kardinalitas between officials with the project
3. the absence of a key dependent on the entity
and when corrected to be :
After which the improvements described above, that clearly:
1. kardinalitas between the project with the N-1 where one or more of the project has many
2. kardinalitas between officials with the project, where the relationship between them is not related to each other, where the employee does not have a project but a part that has proyek.pegawai only work on the project and only have a dependent
3. dependent on the entity have a key as a unique entity
in the normalization are:
1. 1NF on the field where the multiplication occurs and allows a kind of empty fields
where,
pegawai (NOPEG, NAPEG, ALM1, KDPOS, TGLLAH, UMUR);
bagian (NOBAG, NABAG, LOKASI);
proyek (NOPRO, NAPRO, LOKAPR);
tanggungan (NAMA, JNKELT, HUBUNGAN);
Mapping of the above we know that can 1NF fulfilled, after that we can make it 2NF. Normal form 2NF met in a table if it meets the form of 1NF, and all the attributes than the primary key, have a full Functional Dependency on primary key. A table does not meet 2NF, if there are attributes that ketergantungannya (Functional Dependency) are only partial (only depending on the part of the primary key). If there are attributes that have no dependence on the primary key, then the attributes must be moved or removed. View from above mapping we also know that 2NF also met the 3NF can be made. Normal form 3NF fulfilled if the form meets 2NF, and if there are no non-primary key attribute that has a dependence on non-primary key attributes of the other (transitive dependencies).
