Scribd
Upload
7 views3 pages

CS2203 Unit 4 Written Assignment

The document discusses normalizing a hospital database management system to three normal forms. It describes removing duplicates and repeated values to satisfy first normal form, breaking tables to eliminate partial dependencies to satisfy second normal form, and removing transitively dependent attributes to satisfy third normal form.

Uploaded by

tamiriraishetekede
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views3 pages

CS2203 Unit 4 Written Assignment

The document discusses normalizing a hospital database management system to three normal forms. It describes removing duplicates and repeated values to satisfy first normal form, breaking tables to eliminate partial dependencies to satisfy second normal form, and removing transitively dependent attributes to satisfy third normal form.

Uploaded by

tamiriraishetekede
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

CS2203 Unit 4 Written Assignment

First Normal Form:

To make the changes to get the relations into the first normal form, we need to get remove any
duplicates/ repeated groups and values from the value, and have each set of data identify with a
primary key. In the case of the hospital database management system, all relations have no
duplicates nor repeated values hence there are no changes that are needed (it is already in first
normal form).

Second Normal Form:

To make the changes to get the relations into the second normal form, we need to make sure that
there are no partial dependency. To do this, we have to break the table into two parts, where the
candidate key: “iddoctor”, “Phone”, “Name”, and “Specialty”. Special in a non-key attribute, thus
we also need to create a separate table for specialty and Doctors. It should look like the image
below:
Third Normal Form:

To make the changes to get the relations into the third normal form, the table has to be in the
second normal form and non-prime attributes must depend on prime attributes. In our Appointment
Relation, “idpatient” is dependant on “iddoctor”, which is dependent on the “idappointment”. Thus
the “idpatient” transitively depends on “idappointment”, violating the third normal form. To fix
this, we need to create a separate table “PatientApointment”.

Finally we will be left with the final E-R diagram below.


Reference:

Sharma, N., Perniu, L., Chong, R. F., Iyer, A., Nandan, C., Mitea, A. C., Nonvinkere, M. &
Danubianu, M. (2010). Database fundamentals.

You might also like