Pictures can be seen above there is an awkwardness that is:
1. kardinalitas part of the project
2. kardinalitas between officials with the project
3. the absence of a key dependent on the entity
After structured correctly akan as:
After which the repair will be clearly visible:
1. Kardinalitas a part of - part of a project with which the 1-N is one or more parts have more or many projects
2. An employee with kardinalitas 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 a project. And the only employee working on the project and only have a dependent
3. On an entity have a dependent as a unique key of an entity. And
In the normalization that is there:
1. On a 1NF occur where the multiplication or similar field is the same and allows the field to be empty in which,
employees (NOPEG, NAPEG, ALM1, KDPOS, TGLLAH, AGE);
section (NOBAG, NABAG, LOCATION);
project (NOPRO, NAPRO, LOKAPR);
dependent (NAME, JNKELT, CONNECTING);
Flow mapping of the above we can see a 1NF be 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 flow mapping 2NF know that we also have met the 3NF can be made. Normal form 3NF fulfilled if the form meets 2NF, and when no non-primary key attribute that has a dependence on non-primary key attributes of the other, or with the term (transitive dependencies).
