Problems 1 and 3 on pages XXXXXXXXXXof the course textbook. You must use Draw.IO or MS Visio to complete this case study. Create an ER diagram Explain all normalization issues that exist in the ER...




Problems 1 and 3 on pages 234 - 236 of the course textbook.










  1. You must use Draw.IO or MS Visio to complete this case study.
    Create an ER diagram










  1. Explain all normalization issues that exist in the ER Diagram.








  1. I want the ER Diagram before normalization and after normalization.









  1. Explain all normalization problems that you corrected between the first and second ER diagram.









  1. Normalize the data in the ER Diagram to 3NF See the video for a demonstration on how to do this:

    https://www.youtube.com/watch?v=Nq91b4TQ29Q









  1. Create a dependency diagram using the information from your ER diagram. See the video for a demonstration on how to do this:

    https://www.youtube.com/watch?v=wFOJnRxqrp8







  1. You must label all determinants and dependencies.







  1. Note: You must convert your DrawIO files to .jpg, gif or bmp images before you upload the assignment to Canvas. Copy and paste all diagrams into an  MS  Word document. Please make sure that you enlarge all diagrams so they can be easily read in Canvas preview. This will account for 20% of the lab grade.



236 Part 2 Design Concepts<br>3. Using the INVOICE table structure shown in Table P6.3, do the following:<br>TABLE P6.-<br>ATTRIBUTE<br>SAMPLE VALUE<br>SAMPLE VALUE<br>TABLE P6.3<br>NAME<br>ATTRIBUTE<br>SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE<br>STU NUM<br>NAME<br>211348<br>211349<br>211347<br>STU LNAME<br>211347<br>GH-778345P<br>INV NUM<br>211347<br>AA-E3422QW<br>RU-995748G<br>STU MAJO<br>QD-300932X<br>15-Jan-2018<br>16-Jan-2018<br>PROD_NUM<br>AA-E3422QW<br>15-Jan-2018<br>DEPT_COD<br>SALE_DATE<br>15-Jan-2018<br>15-Jan-2018<br>Power drill<br>Rotary sander<br>DEPT_NAN<br>Band saw<br>PROD LABEL<br>Rotary sander<br>0.25-in. drill bit<br>211<br>157<br>DEPT PHC<br>309<br>VEND_CODE<br>211<br>211<br>ToughGo, Inc.<br>NeverFail, Inc.<br>COLLEGE<br>BeGood, Inc.<br>VEND_NAME<br>NeverFail, Inc.<br>NeverFail, Inc.<br>ADVISOR<br>QUANT_SOLD<br>8.<br>$39.99<br>$49.95<br>$87.75<br>ADVISOR<br>PROD_PRICE<br>$49.95<br>$3.45<br>ADVISOF<br>ADVISOF<br>a. Write the relational schema, draw its dependency diagram, and identify ai<br>dependencies, including all partial and transitive dependencies. You can assume<br>that the table does not contain repeating groups and that an invoice number rf<br>erences more than one product. (Hint: This table uses a composite primary ke<br>STU GP.<br>STU HC<br>STU_CL<br>b. Remove all partial dependencies, write the relational schema, and draw the ne.<br>dependency diagrams. Identify the normal forms for each table structure vo<br>created.<br>you<br>Note<br>assu<br>bet<br>You can assume that any given product is supplied by a single vendor, but a ven-<br>dor can supply many products. Therefore, it is proper to conclude that the follow-<br>ing dependency exists:<br>PROD_NUM → PROD_LABEL, PROD_PRICE, VEND_CODE, VEND_NAME<br>(Hint: Your actions should produce three dependency diagrams.)<br>TA<br>AT<br>c. Remove all transitive dependencies, write the relational schema, and draw the<br>new dependency diagrams. Also identify the normal forms for each table struc-<br>ture you created.<br>ITE<br>IT<br>d. Draw the Crow's Foot ERD.<br>RO<br>4. Using the STUDENT table structure shown in Table P6.4, do the following:<br>a. Write the relational schema and draw its dependency diagram. Identify an der<br>dencies, including all transitive dependencies.<br>b. Write the relational schema and draw the dependency diagram to meet the 3NF<br>2NF is appropriate. If necessary, add or modify attributes to create appropriate<br>determinants and to adhere to the naming conventions.<br>requirements to the greatest practical extent possible. If you believe that practical<br>considerations dictate using a 2NF structure, explain why your decision to retain<br>c. Using the results of Problem 4, draw the Crow's Foot ERD.<br>ШИ<br>5.<br>

Extracted text: 236 Part 2 Design Concepts 3. Using the INVOICE table structure shown in Table P6.3, do the following: TABLE P6.- ATTRIBUTE SAMPLE VALUE SAMPLE VALUE TABLE P6.3 NAME ATTRIBUTE SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE STU NUM NAME 211348 211349 211347 STU LNAME 211347 GH-778345P INV NUM 211347 AA-E3422QW RU-995748G STU MAJO QD-300932X 15-Jan-2018 16-Jan-2018 PROD_NUM AA-E3422QW 15-Jan-2018 DEPT_COD SALE_DATE 15-Jan-2018 15-Jan-2018 Power drill Rotary sander DEPT_NAN Band saw PROD LABEL Rotary sander 0.25-in. drill bit 211 157 DEPT PHC 309 VEND_CODE 211 211 ToughGo, Inc. NeverFail, Inc. COLLEGE BeGood, Inc. VEND_NAME NeverFail, Inc. NeverFail, Inc. ADVISOR QUANT_SOLD 8. $39.99 $49.95 $87.75 ADVISOR PROD_PRICE $49.95 $3.45 ADVISOF ADVISOF a. Write the relational schema, draw its dependency diagram, and identify ai dependencies, including all partial and transitive dependencies. You can assume that the table does not contain repeating groups and that an invoice number rf erences more than one product. (Hint: This table uses a composite primary ke STU GP. STU HC STU_CL b. Remove all partial dependencies, write the relational schema, and draw the ne. dependency diagrams. Identify the normal forms for each table structure vo created. you Note assu bet You can assume that any given product is supplied by a single vendor, but a ven- dor can supply many products. Therefore, it is proper to conclude that the follow- ing dependency exists: PROD_NUM → PROD_LABEL, PROD_PRICE, VEND_CODE, VEND_NAME (Hint: Your actions should produce three dependency diagrams.) TA AT 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. ITE IT d. Draw the Crow's Foot ERD. RO 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 an der dencies, including all transitive dependencies. b. Write the relational schema and draw the dependency diagram to meet the 3NF 2NF is appropriate. If necessary, add or modify attributes to create appropriate determinants and to adhere to the naming conventions. requirements to the greatest practical extent possible. If you believe that practical considerations dictate using a 2NF structure, explain why your decision to retain c. Using the results of Problem 4, draw the Crow's Foot ERD. ШИ 5.

Jun 09, 2022
SOLUTION.PDF

Get Answer To This Question

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here