Question 3. (38 points total) . Draw an E-R diagram to represent the proposed database described below. Where and if a relationship needs to be modeled as an associative entity, show it correctly on the diagram Show all minimum and maximum cardinalities. Do not show attributes for any of the entities. Some attributes are provided as examples in the problem so that you can better understand what is being stored and the structures they require. These should not be shown on your diagram. Do not use any structures that imply multi-valued attributes would exist. ID-Dependent vs. non-ID-Dependent relationships do not have to be distinguished for this diagram ($this will not be a grading point). Clearly list any non-obvious assumptions you made (if any). . . Background: This database project is being initiated by the Human Resources (HR) department of a medium-sized manufacturing plant that produces consumer electronics for the retail market. Problem: This database project is being initiated with the goal of enabling the storage and retrieval of data associated with employee benefit selections and the storage and retrieval of data associated with the employee's termination of employment with the organization. Every employee in the organization selects choices from a list of offered benefits. Laws and regulations mandate Do not use any structures that imply multi-valued attributes would exist ID-Dependent vs. non-ID-Dependent relationships do not have to be distinguished for this out this will not be a grading point), Clearly list any non-obvious assumptions you made (if any). Background: This database project is being initiated by the Human Resources (HR) department of a medium-sid manufacturing plant that produces consumer electronics for the retail market. Problem: This database project is being initiated with the goal of enabling the storage and retrieval of data associated with employee benefit selections and the storage and retrieval of data associated with the employee's termination of employment with the organization. Every employee in the organization selects choices from a list of offered benefits. Laws and regulations mandate some benefits and these are entered for the employee with default selections when the employee is hired and entered into the database. Therefore, each employee always has at least one benefit selection. Each benefit that employees may elect may also be elected by any other employees, and it is possible that no employee elects a particular benefit. Therefore, employees will always be related to at least one benefit and some employees will elect many benefits. Benefit coverage has specific start and end dates for the coverage to be active. The dates must also be stored in the database along with the benefit selection An employee's employment may end for a variety of reasons, and the organization needs to capture and store the relevant data for each type. An employee may have zero (still employed) to one terminations. Each termination is related to one and only one employee. All terminations (ending of employment) store basic data such as the date the termination is effective. Additionally, each type of termination stores some differing data. For example, "Terminated_by_self" stores an image of any resignation letter offered by the employee. Additionally, other types of termination that require different specific data are "Terminated_by_org. "Retirement," and "Disability." Terminations must be one type only; i.e., you cannot be officially terminated for more than one of these types (reasons). There are no logical termination types other than the four listed here
