Enhanced Entity Relationship Diagram

All you need is to use Rectangles, Ovals/Circles, Diamonds, and Lines. Be sure to label everything.

Online Electronic Commerce Store (OECS), Inc. - keeps information on employees, customers, products, orders, and purchases and needs you to develop the underlying database. Using the Chen Entity-Relationship data modeling techniques (including the any EER enhancements) learned in class model the following scenario (define your entities with attributes and label your relationships - be sure to transform any Many:Many relationships to associative entities): - The following information is needed about all employees (EmpID, First Name, Last Name, Birth Date, Address (Street, City, State, and Zip), and Hire Date). - OECS would like to keep the following information about its customers: A unique CustomerID, Name (First and Last), Phone, and Email. - Order information should include a unique way to track the order (OrderID) an order date, and a field for whether or not the order has been shipped. - Other Purchase details that need to be known are the quantity of the products purchased and if it has been returned. - For the Products there needs to be a unique identifier (ProdID), a name, description, price, and a place to tell how many units in stock we have left. - There are two types of employees: Manager or Sales Associate, each employee must be one type or another. For managers we also want to track their yearly salary and college degree. For sales associates we also want to track if they have a high school diploma, and their hourly rate. Only Sales associates can place orders. Some business rules for OECS are: - It is important to know which employee sold what product to which customer. - You do not need to store a total for each order, but there should be a way to calculate it. - Please be sure to identify all primary and foreign keys. - Please transform any Many:Many relationships to associate entities