Directions In this assignment, we will use the same database design we had for Assignment 4 (copied below). This design depicts the data transactions taking place in a small College. The assignment is to design two DataMarts to help the administration to keep data about Student Performance and Faculty Performance. They should capture the following information: Student Performance 1. The college is interested in keeping track of the performance of their students thru time. The time dimension can be obtained by the Semester/Section attributes, since Offerings is the only file that provides certain chronology. For example, Spring 2016 is followed by Summer 2016, that is also followed by Fall 2016. The designer may select a coding of these attributes to enforce the chronology 2. Student information should include ID and names. 3. Students performance can be measured in various ways, and it is up to the designer to decide the one s/he considers the best. Student grades in classes could be used directly as a measure of performance, or an aggregate like GPA could also be used for the same purpose 4. The College is interested in following performance per Major and School. Faculty Performance 5. The college is also interested in keeping track of faculty performance through time in the second DataMart. The time dimension would be the same as with Student Performance, using information from the Semester/Section attributes. 6. Faculty information should include ID and names. 7. The DataMart should be able to answer the question of how many courses each Faculty member taught per semester, and if needed, the names of the courses with the average grade per class. Relational Data Model of a Transactional Database COURSE Name FACULTY EirstName LastName EacubPition Years of Tenue Salary OFFERINGS SectionEAcuyp Studertio Grade MEMBER LIST Classification School Majr Adisr0 Deliverables Submit two ERDs, each containing a design for a DataMart for the respective scenarios described above, using the star- schema. Each design may also explain in writing the rationale for the decisions made in the design. In particular, new attributes created for these designs that do not correspond to fields taken directly from the original design should indicate their meaning and how are their values being obtained