. o O 11. Consider a University is designing a new database. One requirement is to store information about its employees. Develop an ERD 1 using appropriate supertypes and subtypes for the following business rules. An employee can be one and only one of the following types: Staff, Professor, and Administrator The following attributes should be stored for all employees First name Last name Middle initial Hire date Staff employees have a work level classification, such as "Level 1", "Level II", etc. Professors have a rank, such as "Asst. Professor", "Assoc. Professor", etc. Administrators have a position title A Professor works for a Department A Department has a department name and office location o O . . . 2. In the University example above it was stated that an employee can be one and only one of the three types of employees. Consider that this requirement is changed to say that an employee can be ONE OR MORE of the three types at the same time. For example, an employee might be both an Administrator and a Professor. Modify your ERD 1 to account for this requirement change. 3. New requirements dictate that the University database above should also store the following information about students. First name 0 Last name . Middle initial There are two types of students: Undergraduate and Graduate. Undergraduates require attributes for Major, GPA, and Hours Completed. Graduate students require attributes for Degree Sought, GPA, and Entrance Exam Score. Modify your ERD 1 from the previous question to account for these new requirements. Given that students and employees share many attributes, begin your special hierarchy with a PERSON entity that can store data for both. Be sure to allow for a student to also be employed by the University