Currently the relation only consists of a start time, and it is believed to last 1 hour. The addition of a M:N relationship means that a single event can have multiple time-slots, and thus we can now imply how long the event takes and thus satisfy the new criteria. It also allows for simultaneous events, which is also a good thing.

close

Currently the relation only consists of a start time, and it is believed to last 1 hour. The addition of a 1:N relationship means that a single event can have multiple time-slots, and thus we can now imply how long the event takes and thus satisfy the new criteria. It however stops more than one event happening at the same time, which would severly weaken the timetable.

close

Currently the relation only consists of a start time, and it is believed to last 1 hour. By adding a duration in minutes, we can now imply how long the event takes and thus satisfy the new criteria.

close

Currently the relation only consists of a start time, and it is believed to last 1 hour. By adding a duration in hours, we can now imply how long the event takes and thus satisfy the new criteria. This implies that event durations are in multiples of hour-long periods.

close

Currently the relation only consists of a start time, and it is believed to last 1 hour. By adding an end time, we can now imply how long the event takes and thus satisfy the new criteria.

close

 A B C D E TELL ME NEXT INDEX

A timetable database is required for a University Department. Each taught event is part of a module, each event will have exactly one member of staff associated and several individual students. Each event takes place in a single weekly time slot. Each time slot has a day of the week and a time of day associated.

Each of the weekly time slots is exactly one hour long, however we wish to represent the fact that some events take more than one hour. Which of the following does not represent a possible solution.
1. A many-to-many relation between Events and Time-Slots is established
2. A one-to-many relation between Events and Time-Slots is established
3. Each event has an attribute "start" which refers to Time-Slots and "duration" which gives the length of the event in minutes
4. Each event has an attribute "start" which refers to Time-Slots and "duration" which gives the number of slots spanned
5. Each event has two attributes "first" and "last" each of which refer to Time-Slots