In this activity, we will spend some more time thinking about how the database of a system such as Scheduling can be conceptualized. The system requirements for this database are listed below. For simplicity, we are covering only the main features such an application. Check for entities first, then the facts between them and then generalize those facts into relationship types.

a. additions: group of employees for a session, facilitator required for each activity

Part I ( 20 pts)

Use the CSPD procedure here

1. Get the elementary facts

2. Generalize the facts into fact types

3. Draw an ORM diagram to relate the fact types to each other

4. Apply relevant constraints ---- ( steps 4,7)

Scenario: You are tasked with drawing up the conceptual schema for a scheduling application

as follows:

• Certain Rooms are booked for an Activity at a certain Day-Hour.
• Buildings house
• The Room is identified by a building nr and a room nr ( number) note this this would involve a composite reference, how would you indicate that. (think compound key
• The Day-Hour ( TimeSlot) is identified by a dhr identifier ( e.g. M 2:00pm, Th 9:00 am ) means Monday at 2 and Thursday at 9.
• The Activity is designated by an ActivityName
• One constraint is that no room can be booked for the same Activity at the same time.
• Every activity must have a unique name which identifies that activity, and, Each activity has one facilitator
• Each session ( what does a session consist of? Nominalization?) is attended by a group of employees. Model this. Generate a few employees to play with.

Here is a sample table:

TimeSlot	Room	Activity Code	Activity Name	Facilitator
M 9 am	20	ORC	ORM class	TH
T 2 pm	20	ORC	ORM class	TH
M 9 am	30	SFP	Scala FP	MO
F 5 pm	30	SP	Staff Party	MO