Start with a single table (could be in NNF) and then proceed to 1NF (no multi-valued attributes and has good PK). In the 1NF relations, determine all the dependencies. 1. Proceed with 2NF and 3NF just like in the Project example in Chapter 6. Determine the dependencies at each step. li. Or determine the dependencies in the 1NF table using A->B notation and write out all the tables in 3NF. No need to draw and ERD, use the relational schema format: 1. 3NF TABLE_NAME (Attribute1, Attribute2, ....)underline the PK. State clearly any reasonable) assumptions you may make. Parts Invoice Cust ID Invoice # Company Name Date Address Part # Description # Used Price Total Parts Subtotal Price Labor ID Description Labor Subtotal Parts + Labor Subtotal Tax rate Tax Total Business Rules: The tax rate is based on the customer's state. All subtotals, the tax amount and the invoice total are computed. Your answers (text, images) Start with a single table (could be in NNF) and then proceed to 1NF (no multi-valued attributes and has good PK). In the 1NF relations, determine all the dependencies. 1. Proceed with 2NF and 3NF just like in the Project example in Chapter 6. Determine the dependencies at each step. li. Or determine the dependencies in the 1NF table using A->B notation and write out all the tables in 3NF. No need to draw and ERD, use the relational schema format: 1. 3NF TABLE_NAME (Attribute1, Attribute2, ....)underline the PK. State clearly any reasonable) assumptions you may make. Parts Invoice Cust ID Invoice # Company Name Date Address Part # Description # Used Price Total Parts Subtotal Price Labor ID Description Labor Subtotal Parts + Labor Subtotal Tax rate Tax Total Business Rules: The tax rate is based on the customer's state. All subtotals, the tax amount and the invoice total are computed. Your answers (text, images)