Question 1 [20 pts] Composite and multi-valued attributes can be nested to any number of levels. Suppose we want to design an attribute for a STUDENT entity type to keep track of previous college education. Such an attribute will have one entry for each college name, start and end dates, degree entries (degrees awarded at that college, if any), and transcript entries (courses completed at that college, if any). Each degree entry contains the degree name and the month and year the degree was awarded, and each transcript entry contains a course name, semester, year, and grade. Create an ER diagram to represent the description above, using only one entity type, STUDENT. All other items must be attributes (note: an attribute can be both a compound attribute and a multi-valued attribute). There must be no relationships. Question 2 [20 pts] Create an ER diagram to represent the description in Question 1, except this time, you may use any number of entities and relationships, but you can not use any multi-valued attributes Question 3 [10 pts] Create a UML class diagram equivalent to your answer to Question 2. Question 4 [20 pts] Create the SQL code to implement the tables described in your answer to Question 2 (or to Question 3; t should be the same)