Composite and multivalued 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 each students previous college education. Such an attribute will have one entry for each college previously attended, and each such entry will be composed of 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 will contain the degree name and the month and year the degree was awarded, and each transcript entry will contain a course name, semester, year, and grade. Design an attribute Previous Education to hold this information.

a. Provide the schema for the Previous Education attribute using the written convention

b. Based on your answer to part (a), use ERDPlus to draw an ER schema diagram for a Student entity type that includes only the single complex complex attribute for Previous Education (no need to include other attributes). Be sure to use proper diagramic notation for each multivalued and composite component of the attribute. Note: Your ER diagram must be consistent with the written schema you have provided in (a).