a. Write the relational schema, draw its dependency diagram, and identify all dependencies, including all partial and transitive dependencies. You can assume that the table does not contain repeating groups and that an invoice number references more than one product. (Hint: This table uses a composite primary key.)
b. Remove all partial dependencies, write the relational schema, and draw the new dependency diagrams. Identify the normal forms for each table structure you created.
Note: You can assume that any given product is supplied by a single vendor, but a vendor can supply many products. Therefore, it is proper to conclude that the following dependency exists:
PROD_NUM S PROD_lABEl, PROD_PRICE, vEND_CODE, vEND_NAME
(Hint: Your actions should produce three dependency diagrams.)
c. Remove all transitive dependencies, write the relational schema, and draw the new dependency diagrams. Also identify the normal forms for each table structure you created.
d. Draw the Crow's Foot ERD.
4. Using the STUDENT table structure shown in Table P6.4, do the following:
a. Write the relational schema and draw its dependency diagram. Identify all dependencies, including all transitive dependencies.
b. Write the relational schema and draw the dependency diagram to meet the 3NF requirements to the greatest practical extent possible. If you believe that practical considerations dictate using a 2NF structure, explain why your decision to retain 2NF is appropriate. If necessary, add or modify attributes to create appropriate determinants and to adhere to the naming conventions.