Create a database that will record employees and their salary histories. For each employee record their first name, last name, DOB and start date and termination date (if applicable). The salary history should include the $s alary, the range of dates for which the salary is effective (the current salary will not have an end date). The database should also record a history of which departments they have worked for. An employee may only work for one department at a time. For departments, you only need to record the department name. 1. Write the business rule for the database (15 points) 2. Create an ERD for the database (15 points) 3. Create INSERTs for the entities. Have a least three employees and 2-4 salary ranges per employee (15) 4. Write SQL queries to display the salary and department history for a given employee (5 points)

We will continue with week 4 modeling with the following additional requirements 1. Your ERD must successfully forward engineer 2. The inserted data must not contain any NULLs, nor the possibility of entering any NULLs 3. The model must allow for employees to leave the company (termination) and then to possibly be rehired (multiple times) 4. All SQL shall be contained in VIEWS (which we will discuss in class) What to turn in 1. Your bi-directional business rules. The business rule must state the relationship (1:M, M: N, 1:1) (20 points) 2. Your MBW file with all inserts (15 points) Preferable to create VIEWs to store your SQL 3. A query that answers show all of the hiring events for a specific employee (5 points)