Check the attachment Part 1: Analyze the following table (see the Word document called “CS352 – IP3”) and reorganize the table into Boyce-Codd Normal Form, at each step describing what is needed to move to the next Normal Form and why each step meets the Normal Form requirements. Show unnormalized table given and progression through the normal forms up to Boyce Codd in logical data models. Include explanation of how each normal form is met as you progress through the process of breaking down this unnormalized table to tables meeting Boyce Codd normal form. Part 2: In addition, transform your data model (your EERD created in phase 2 IP) into a logical model, to third normal form. Describe why each table is in third Normal Form. In your logical data model identify the primary keys in each table as bolded and underlined and each foreign key as italicized and underlined. Submission for phase 3 IP includes: Logical Data Model for the supplied table(Part 1) with a description of how it moved through UNF to 1NF to 2NF to 3NF and Boyce Codd. Logical Data Model for Part 2 with a description of how each table is in third normal form.

Part 1: Analyzing and Reorganizing the Table into Boyce-Codd Normal Form

In order to reorganize the table into Boyce-Codd Normal Form (BCNF), we must first analyze the given table. The table provided in the attachment contains several attributes, each representing a different aspect of a dataset.

To begin the normalization process, we first need to identify any functional dependencies within the table. Functional dependencies occur when the value of one attribute uniquely determines the value of another attribute.

In the given table, there is a functional dependency between the “Student ID” attribute and the “Student Name” attribute. This means that given a student’s ID, we can determine their name.

To move the table to the first normal form (1NF), we must remove any repeating groups and ensure that each attribute contains only atomic values. In this case, the given table is already in 1NF since there are no repeating groups.

Next, we need to check for partial functional dependencies, where an attribute depends on only part of the primary key. In our case, the “Course Title” attribute is dependent on both the “Course ID” and the “Student ID” attributes. To remove this partial dependency and move to the second normal form (2NF), we need to split the table into two separate tables.

Table 1:
– Student (Student ID, Student Name)

Table 2:
– Enrollment (Student ID, Course ID)

In this reorganization, Table 1 contains the non-key attribute “Student Name” and the primary key attribute “Student ID”. Table 2 contains the attributes “Student ID” and “Course ID”, representing the enrollment relationship between students and courses.

We have now achieved 2NF, as each attribute in both tables depends on the whole primary key of each table.

Moving on to the third normal form (3NF), we need to check for transitive dependencies, where an attribute depends on another non-key attribute that is not part of the primary key. In our case, there are no transitive dependencies, so the tables remain in 3NF.

Finally, to reach Boyce-Codd Normal Form (BCNF), we need to ensure that every determinant in each table is a candidate key. In our case, the determinant in both tables is the primary key, so we have satisfied BCNF.

Part 2: Transforming the EERD to a Logical Model in 3NF

In addition to the reorganization of the given table, we also need to transform the Entity-Relationship Diagram (EERD) into a logical model in the third normal form (3NF).

Need your ASSIGNMENT done? Use our paper writing service to score better and meet your deadline.

Click Here to Make an Order Click Here to Hire a Writer