1. Draw a fully-labeled E-R diagram that include entities, relationships, connectivities and cardinalities from the business rule described below. Business Rule: Each dinner is based on a single entree, but each entree can be served at many dinners. Each dinner invitation can be mailed to many guests, and each guest can receive many invitations. A guest can attend many dinners, and each dinner can be attended by many guests. Requirements: A dinner must have at least one guest attending. In other words, the database needs not keep track of the dinners that no one attended. Note: Limit your ERD to entities and relationships based on the business rules shown here. In other words, do NOT add "realism" to your design by expanding or refining the business rules! When needed, provide the rationale to justify your model (e.g., optional participation) 2. Using the INVOICE table structure shown below, 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 references more than one product. Hint: This table uses a composite primary key. ATTRIBUTE NAME INV_NUM PROD_NUM AA-E3422QW QD-300932X SALE_DATE 15-Jan-2006 15-Jan-2006 PROD_LABEL Rotary sander 0.25-in. drill SAMPLE VALUE 211347 SAMPLE VALUE 211347 VEND_CODE 211 VEND_NAME NeverFail, Inc. QUANT_SOLD 1 PROD_PRICE $49.95 bit 211 NeverFail, Inc. 8 $3.45 SAMPLE VALUE 211347 RU-995748G 15-Jan-2006 Band saw 309 BeGood, Inc. 1 $39.99 SAMPLE VALUE 211348 AA-E3422QW 15-Jan-2006 Rotary sander 211 NeverFail, Inc. 2 $49.95 SAMPLE VALUE 211349 GH-778345P 16-Jan-2006 Power drill 157 ToughGo, Inc. 1 $87.75