Task 2: Normalization

In task 2 you will ensure that all tables are normalized to 3NF or make a convincing argument why particular tables should not be fully normalized. Normalization and definition of functional dependencies is not a task that erwin support sdirectly, so this is a task that must be done manually.

1. For each table from Task 1a, draw an initial functional dependency diagram, based on the business rules provided in DBProjectPartA_Task2.docx. Please note: these rules differ slightly based on the suggested solution that you choose to model. If you find that the business rules listed are unclear or incomplete, you may send me (the surrogate user/client) an e-mail requesting clarification.
2. Normalize each table through 3^rd normal form. You may find that some, perhaps many, tables from task 1a are already normalized. This is not a problem, just a sign of a good E-R diagram.
3. Update the E-R diagram as necessary to reflect the results of normalization. In other words, if normalization has resulted in the creation of new tables or the moving around of attributes between tables, then make these changes in erwin DM.

MPAA PERSON \begin{tabular}{|l|} \hline \\ \hline pers_fName \\ pers_IName \\ \hline \end{tabular} \begin{tabular}{|l|} \hline Dogpaa_rating \\ \hline mpaa_description \\ \hline \end{tabular} studio_name MPAA PERSON \begin{tabular}{|l|} \hline \\ \hline pers_fName \\ pers_IName \\ \hline \end{tabular} \begin{tabular}{|l|} \hline Dogpaa_rating \\ \hline mpaa_description \\ \hline \end{tabular} studio_name