Each performer is represented. The information about a Performer is the performer's id (Pid) which uniquely identifies a performer object, the performer's name (PName), his manager's name (MgrName), his booking agent (BookAgent), the last date that he performed (LastDateUp) and the last company that used the performer (LastUser). Each performer headlines zero or more events. Each event is represented. The information about an event is the event id (Eid), the event name (EName), the creation date (CreateDate), the last time the show was performed (LastUpDate) and the last user of the show (Show LastUser). An event is uniquely identified by its event id. Each event is booked for zero or more event performances and is headlined by exactly one performer Each event performance is represented. The information about an event performance is the event performance date (EPDate) which only partially identifies an event performance. The event performance date, the event id, and the arena id (Aid) used to identify an arena, uniquely identifies an event performance object. Each event performance is held in exactly one arena. Each event performance has for sale many event tickets and each event performance has many event ticket prices. Each arena is represented. The information about an arena is the arena id (Aid) which uniquely identified an arena, the arena name (AName), the address of the arena (StAddr), the province in which the arena is located (Province), the city (City) and the zip (ZIP). Each arena has many seats. Each arena seat is represented. The information that represents an arena seat is the seat section number (SectionNo), the aisle (Aisle), the row (Row) and the seat number (SeatNo). This information is unique only for an arena. An arena seat has many event ticket prices. Each event ticket price is represented. The information that represents an event ticket price is the seat category (SeatCategory) which is unique only for an event performance, and the ticket price (TicketPrice). Each event ticket price is associated with many event tickets. The same event ticket price is for many arena seats. Each event ticket is represented. The event ticket is identified by the identifier of an event performance and is assigned exactly one event ticket price. - Construct an UML class diagram for the concert event system. - Determine the key for each class and any partial keys for each weak class. - Indicate the minimum and maximum multiplicities and any ID dependency constraints for each association