Consider a typical sales invoice that would include the following information:
- Order_id
- Order_date
- Customer_id
- Customer_name
- Customer_address
- Customer_city
- Customer_state
- Item_id
- Item_description
- Item_qty
- Item_price
- Item_total_price
- Order_total_price
Design a single table to hold all of the information required to store an invoice including this information. Next, apply normalization to reduce this table to third normal form. Attach a Word document showing the original and final tables. Describe the problems with the original single table design and how normalization improved the design.
SUMMIT SEPERATE FROM NEXT STEP……………………………………………………………………..
| PLEASE INCLUDE 1 Fully Documented ERD A description of the multiplicity that is chosen and setup between entities | |
| Details: |
Once requirements analysis is completed, the 1st step in Database Design can be completed. This step is the conceptual model (or Entity Relationship Diagram). Using any modeling tool you choose (SmartDraw, Visio, Erwin, or even PowerPoint or Word), create an Entity-Relationship Diagram (ERD) from the Entity and attributes list defined in the previous step. Your submission should ensure that:
Adhere to APA formatting and reference guidelines when writing your response. Additionally, your response should be free of grammatical errors, use complete sentences, and give specific details to support statements. |
0 comments