Using the table below, and assuming this is the entire universe of data related to this table, identify at least 6 functional dependencies and document them below using functional dependency notation, such as A B. Zip Product ID Category Sub-Category TotalPrice Order ID Order Date Customer ID Customer Name CA-2016-1 11/8/21 CG-12520 Claire $1,200.00 CA-2016-1 11/8/21 CG-12520 Claire CA-2016-2 6/12/21 DV-13045 Darrin 10/11/20 SO-20335 Sean Furniture Sofas Furniture Sofas Office Sup Tech Furniture Tables Office Sup Storage Furniture Sofas US-2014 US-2014 10/11/20 SO-20335 Sean CA-2014 12/12/2022 DV-13045 Darrin US-2015 10/11/20 CG-12520 Claire Office Sup Tech Type 6 functional dependencies below using notation like Manufacturer Serial#: Part 2 - Normalization & Conceptual Design - (30 pts) Normalize the table below so it satisfies Boyce-Codd Normal Form. Consulting Information Table EmpNum EmpName Proj Num 213 Jackson Wilson Adams Stevens 216 293 264 AC11 AC11 INT2 INT2 42420 Couch1 42420 Loveseat 90036 Printer 33311 Coffee Table 33311 Cabinet 90036 Couch1 42420 Printer ProjName Purchasing App Purchasing App DeptNum Dev Dev Int CRM Integration Int CRM Integration $ 900.00 $ 400.00 $ 200.00 $ 800.00 $1,200.00 $ 400.00 DeptName ProjBudget EmpRate Development $ 12,000 $ Development $ 12,000 $ Integrations $ 17,000 $ Integrations $ 17,000 $ 75 60 100 70 To communicate your normalized tables/entities, use "relational notation" similar to the following: PRODUCT(ProductID, ProductName, etc.). Underline your identifier/primary key. (No need to place or identify foreign keys at this point. If you are more comfortable adding them, that's fine too.) Hint: A good way to decide about how to decompose an un-normalized table is to identify functional dependencies and look for partial and transitive dependencies. List your tables in relational notation sentence structure here: