Database - Project Plan

profileBluSkyy757
KHart-ERD.docx

Entity Relationship Diagram 1

ERD:

Normalization:

1NF:

For the 1st NF we will have to check the tables’ attributes, like there must not be any multivalued attribute, if there is any multivalued attribute then we have to split the table and create a new table for that particular multivalued attribute.

So here in above ERD we can see there are multivalued attributes in three entities and those entities are as follows:

1. Worker

2. Customer

3. Permission

Worker Entity:

In worker entity we can see that worker can have multiple contact numbers and multiple emails so here we have to split the tables and this entity will split up in following way:

Worker Contact Entity:

Worker Email Entity:

Customer Entity:

In customer entity we can see that customer can have multiple contact numbers and multiple emails so here we have to split the tables and this entity will split up in following way:

Customer Email Entity:

Customer contact Entity:

Permission Entity:

Here in above ERD we can see that in Permission entity there can be multiple Permission Modules against a single Permission ID. So we will split up the table accordingly:

Permission Modules Entity:

Rest of the entities don’t have multivalued attributes so they are already in 1st NF

2NF:

For 2nd normalization form we will have to check partial key dependency. Firstly what is partial key, partial key means there is an attribute other than primary key and that attribute is part of the primary key.

Here in above ERD we can see there is no partial key dependency, it means all the entities are already in 2nd NF.

3NF:

In the 3rd normal form, we will have to check the transitive dependency in a way that dependency of non-key attributes on the other non-keys attributes.

Here in above ERD there is no transitive dependency exist in the entities so all the entities are already in 3rd NF.

Here is the ERD after Normalization: