Part 1 CREATE an ER diagram for Volkswagen. You should have a notion for cars (models, features), parts (engines, door handles, windows, ec.., suppliers, warehouses, dealerships, employees, managers and anything else that you believe Volkswagen would need to use to run their business. Be detailed! 1) 2) You MUST specify multiplicities->many-many, many-one, one-one Be sure to specify keys 3) Our database should be able to model the following data: Employees-come up with pertinent data to store for an employee based on examples we have seen in class. (ideas: Address, date of birth, hire date, salary, etc..) Managers-a special case of employees (what makes a manager different from an employee) You need to have a way to list the employees that are managed by a manager. You also need to be able to model which manager manages which department. Departments-you need to model which employees work in which department. Dealerships-payment information needs to be tracked along with orders Products-need a price. We can assume that each product will have a single price Orders-needs to be associated with dealerships. A single dealership can have multiple orders. An Order should have products and quantities. Has an order shipped yet? Suppliers-Parts need suppliers- where will the product come from. We can assume to simplify that each product is only supplied by a single supplier at a given price Be creative and thoughtful-go beyond what I have listed here. Come up with appropriate attributes Recall that each Entity Set should have a key Part 2 4) Convert your ER diagram into a set of Tables (Relations) Part 1 CREATE an ER diagram for Volkswagen. You should have a notion for cars (models, features), parts (engines, door handles, windows, ec.., suppliers, warehouses, dealerships, employees, managers and anything else that you believe Volkswagen would need to use to run their business. Be detailed! 1) 2) You MUST specify multiplicities->many-many, many-one, one-one Be sure to specify keys 3) Our database should be able to model the following data: Employees-come up with pertinent data to store for an employee based on examples we have seen in class. (ideas: Address, date of birth, hire date, salary, etc..) Managers-a special case of employees (what makes a manager different from an employee) You need to have a way to list the employees that are managed by a manager. You also need to be able to model which manager manages which department. Departments-you need to model which employees work in which department. Dealerships-payment information needs to be tracked along with orders Products-need a price. We can assume that each product will have a single price Orders-needs to be associated with dealerships. A single dealership can have multiple orders. An Order should have products and quantities. Has an order shipped yet? Suppliers-Parts need suppliers- where will the product come from. We can assume to simplify that each product is only supplied by a single supplier at a given price Be creative and thoughtful-go beyond what I have listed here. Come up with appropriate attributes Recall that each Entity Set should have a key Part 2 4) Convert your ER diagram into a set of Tables (Relations)
