Step by step if possible. Thanks.

1. List the major entities identified in the table above

2. After examining the table carefully identify candidate keys. Remember from the lecture that a candidate key field has to be unique, but should not hold private information that might compromise person's identity. For example SSN is unique and can be used to determine student information, so it is a candidate key, but using SSN might compromise student security for that it will not be used as primary key. The combination of first name and last name is not unique and cannot be used as a candidate key. Once the candidate keys been identified, some will be as primary keys and will be used to normalize the table. To connect the tables, the primary key of one table can be used as a foreign key in the other.

3. Identify the functional dependences. Functional dependencies uses the identified candidate key as determinant field to determine other attributes/fields in the table. For example student ID in the DSC system can pull student information including DOB, address, city, state, zip code, so on. This is what we call functional dependency. Student ID is a determinant field and a candidate key in this example.

4. Put the previous relation (table) in a normalized Boyce-Codd Normal Form (BCNF)

5. If you have multiple values for the department phone number (the department has multiple phones), what will be the best solution to convert the data into relations. Review the lecture titled normalization before answering this question.