90 likes | 264 Views
Order Database – ER Diagram. Prepared by Bryan Borcher Spring 2014. Designing Databases with Entity Relationship Diagrams. Step 1: Define Entity Classes and Primary Keys. Step 2: Define Relationships Among Entity Classes. Step 3: Define Attributes for each Table.
E N D
Order Database – ER Diagram Prepared by Bryan Borcher Spring 2014
Designing Databases with Entity Relationship Diagrams Step 1: Define Entity Classes and Primary Keys Step 2: Define Relationships Among Entity Classes Step 3: Define Attributes for each Table Step 4: Create Database
Step 1: Define Entity Classes and Primary Keys There is not a limit to the number of orders a customer may place. Each customer can have one order, multiple orders, or be in your database without any orders. Each order is made by a single customer. Ordersmust have at least one product. Ordersmay have multiple products. The same product could be sold through many orders. Products can be listed in your database but not purchased.
Step 2: Define Relationships Among Entity Classes CUSTOMER ORDER PRODUCT
Step 3: Define Attributes for each Table CUSTOMER PRODUCT ORDERITEM ORDER
Step 3: Define Attributes for each Table CUSTOMER PRODUCT ORDER
Step 4: Create Database http://students.uwyo.edu/bborche1/IMGT2400/databaseproject.accdb