$3\mathrm{.}17.$ 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 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 col. lege, if any$).$ Each degree entry contains the degree name and the month and year the degree was awarded, and each trajscript entry contains a course name, semester, year, and grade. Design an attribute to hold this information. Use the conventions in Figure $3\mathrm{.}5.$

$3\mathrm{.}18.$ Show an alternative design for the attribute described in Exercise $3\mathrm{.}17$ that uses only entity types $($including weak entity types, if needed$)$ and relationship types.