3. Using the INVOICE table structure shown in Table P6.3, do the following: TABLE P6.3 SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE 211347 211349 GH-778345P ATTRIBUTE NAME INV_NUM PROD_NUM SALE_DATE PROD_LABEL VEND_CODE VEND_NAME QUANT_SOLD PROD_PRICE 211347 AA-E3422QW 15-Jan-2016 Rotary sander 211 211347 QD-300932x 15-Jan-2016 0.25-in. drill bit 211 RU-995748G 15-Jan-2016 Band saw 309 211348 AA-E34220W 15-Jan-2016 Rotary sander 211 NeverFail, Inc. 2 16-Jan-2016 Power drill 157 ToughGo, Inc. 1 NeverFail, Inc. Never Fail, Inc. BeGood, Inc. 1 8 1 $49.95 $3.45 $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. Note You can assume that any given product is supplied a single vendor, but a vendor can supply many products. Therefore, it is proper to conclude that the following dependency exists: PROD_NUM 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 struc- ture you created. d. Draw the Crow's Foot ERD