3. Using the INVOICE table structure shown in Table P6.3, do the following: TABLE P6.3 ATTRIBUTE SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE NAME INV_NUNM PROD NUM AA-E3422QW SALE_DATE 15-Jan-2016 PROD LABEL Rotary sander VEND_CODE 211 VEND NAME NeverFail, Inc. QUANT_SOLD PROD PRICE $49.95 211349 GH-778345P 16-Jan-2016 Power drill 157 ToughGo, Inc. 211347 211347 QD-300932X 15-Jan-2016 0.25-in. drill bit 211 NeverFail, Inc. 8 $3.45 211347 RU-995748G 15-Jan-2016 Band saw 309 BeGood, Inc. 211348 AA-E3422QW 15-Jan-2016 Rotary sander 211 NeverFail, Inc. $39.99 $49.95 $87.75 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 ref- erences 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 ote 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: PRODNUM PRODLABEL, PRODPRICE, VENDCODE, VENDNAME ----- (Hint: Your actions should produce three dependency diagrams.)