Question 2 (36 marks) This question is based on Section 2 of Block 2. It assesses your ability to transform a relational representation into an ER conceptual model. For the relational model below, give the corresponding entityrelationship diagram showing the relationships with their cardinality and participation conditions, the corresponding entity type definitions, and the constraints. An entity type should not be used to represent a relationship. relational model EventPlanner Domains EventCodes = {e0001...e9999}

VenueCodes = {v01v99}

CatererCodes = {ca01ca99}

EntertainerCodes = {en01en99}

CustomerCodes = {cu0001cu9999}

InvoiceCodes = {0001...9999}

Dates Times = {0:0023:59}

PeopleCount = {19999}

PriceBands = {economy, midprice, luxury}

EntertainerTypes = {singer, band, magician, comedian} Names = string relation Event EventCode: EventCodes CustomerCode: CustomerCodes Date: Dates StartTime: Times EndTime: Times NumberOfPeopleExpected: PeopleCount VenueCode: VenueCodes CatererCode: CatererCodes primary key EventCode foreign key VenueCode references Venue foreign key CatererCode references Caterer relation Venue VenueCode:VenueCodes Capacity: PeopleCount PriceBand : PriceBands primary key VenueCode constraint ((project Venue over VenueCode) difference (project Event over VenueCode)) is empty relation Caterer CatererCode: CatererCodes MaximumNumberOfPeopleCanCaterFor: PeopleCount PriceBand: PriceBands primary key CatererCode 3 relation Entertainer EntertainerCode: EntertainerCodes Name:Names EntertainerType: EntertainerTypes primary key EntertainerCode relation EntertainedBy EventCode: EventCodes EntertainerCode: EntertainerCodes primary key (EventCode, EntertainerCode) foreign key EventCode references Event foreign key EntertainerCode references Entertainer relation Invoice InvoiceCode: InvoiceCodes EventCode: EventCodes DatePresented: Dates primary key InvoiceCode alternate key EventCode foreign key EventCode references Event