The following requirements describe a reservation system for university spaces. Draw an

EER diagram that shows the entity types, attributes, relationship types, and constraints for a

database to capture as many of these requirements as you can. Include weak entity types and

specialization/generalization notation as appropriate. State any assumptions you make, and

note any requirements which you could not capture in the diagram.

(a) A member of the university community has a first name, last name, and id. Every

member of the university community is either a student or an employee. We need to

know whether each student is on-campus or online. Every university employee has a

job title.

(b) A university building has a name and address. Buildings can be identified based on

their name.

(c) A space is a part of a university building. Every space has a label such as room 1023

or first floor atrium. A space can be identified based on the combination of its label

and the building it is in.

(d) An event has a date, start time, end time, name, and description. An event can be

identified based on the combination of its name, date, and start time.

(e) A university employee or student can make a reservation of a specific space for a given

event; and every event

must

have a space reserved for it. But students can only reserve

spaces in some buildings and not others, while employees can reserve spaces in any

building. (For example, it may be that a student can reserve a space in the library

building or the student union building, but not in the science building.)

(f) A space cannot be reserved for two different events which overlap in time.