1) 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 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. Design an attribute to hold this information (Class 3, objective 1)

Use this format: {Address_phone( {Phone(Area_code,Phone_number)},Address(Street_address

(Number,Street,Apartment_number),City,State,Zip) )}