ERD:
First Normal Form (1NF)
On first normal form still have a lot of weakness, such us:
Insert, we can not only inserting NOPEG and NAPEG without their PROYEK, so we can inserting their attribute if there is PROYEK.
Update, depend on the table above, many attribute written recurring repeat, if there is updating attribute so all the same attribute must be update.
Delete, when one record vanished, so all data in that record will be vanished though the data still needed.
UMUR attribute must not be written, because every date of now at reducing attribute TGLLAH so will be result attribute UMUR.
Between Proyek entity and Bagian entity have one relation that is Punya relation, that meaning is one Proyek have many Bagian, so on Proyek table is filled NOBAG.
Between Bagian entity and Pegawai entity have two relation that is Anggota relation and Pimpin relation, that meaning is one Bagian have many Pegawai (Anggota relation) and one Pegawai leading one Bagian, so on Bagian table is filled NOPEG.
Pegawai entity have one relation that is Kontrol relation, that meaning is one Pegawai controlling many Pegawai (Unary relationship), that relation just using NOPEG.
On Tanggungan table is filled NOPRO and NOPEG because Tanggungan entity is weak entity, so Tanggungan entity dependency with Proyek entity and Pegawai entity.
On Kerja relationship have one attribute so the primary key from relation between Proyek entity (NOPRO) and Pegawai entity (NOPEG).
From the form above can be seen that 3NF form is equal with 2NF form because when it is created to 2NF form, a whole of attribute in table just depend from the only one attribute in that table. This is in accordance with the requirements of 3NF form that is in a table all of attributes must depend in an attribute that function as a primary key.
