Design a normalized order management database using the information below. Each record should have at least one primary key field specified. After identifying the records and their corresponding fields, draw an entity-relationship (ER) diagram to illustrate the relationships between entities and attributes ORDER MANAGEMENT Entity-Relationship ITEM: Customer Header · customer number · buyer name · bill-to address · buyer phone · buyer email · credit rating Customer Shipping · location number · receiver name · receiver phone · receiver email · ship-to address Order Header · order number · order date · shipment method Order Detail · item number · part number · unit price · total quantity Delivery Schedule · delivery number · location number · quantity · due date Part · part number · standard price Customer-Part Relationship · customer number · part number · special price
Design a normalized order management
Each record should have at least one primary key field specified. After identifying the records and their corresponding fields, draw an entity-relationship (ER) diagram to illustrate the relationships between entities and attributes ORDER MANAGEMENT
Entity-Relationship
ITEM:
Customer Header
· customer number
· buyer name
· bill-to address
· buyer phone
· buyer email
· credit rating
Customer Shipping
· location number
· receiver name
· receiver phone
· receiver email
· ship-to address
Order Header
· order number
· order date
· shipment method
Order Detail
· item number
· part number
· unit price
· total quantity
Delivery Schedule
· delivery number
· location number
· quantity
· due date
Part
· part number
· standard price
Customer-Part Relationship
· customer number
· part number
· special price
Trending now
This is a popular solution!
Step by step
Solved in 3 steps with 2 images
