You have been hired to design the Ticket Tout software system that will allow users to browse and purchase tickets for events via an online portal. Each event has a name, a venue and a genre (such as a rock concert or monster trucks rally, there may be more). It may have just one offering on a particular time and date, or it may have several offerings over a range of times and dates.

For each offering of an event there are a fixed quantity of tickets available. The tickets come in various classes (which might reflect the quality of the view/experience offered), and each class has its own price. Each ticket has a unique serial number and may have other information such as a seat number or section, depending upon the type of event and venue. Each ticket is purchased by a single customer. Customers may buy as many tickets per event as they wish within a single transaction, and the tickets can be of mixed class.

To successfully purchase tickets, customers will need to provide name, address, contact email, contact phone number and credit card information. A typical visit to the portal would see a customer browse the selection of events, get further information on an interesting event and then purchase tickets to go to that event. The administrator of the Ticket Tout system will need to be able to add new events to the system and remove old ones.

The organizations who run the events (such as bands) want to know how many tickets have been sold for an event so far (and for which offerings if applicable), as will venue managers. Administrators should be able to provide that information if requested. Sadly sometimes events have to be cancelled, and in these circumstances the administrator will need to make sure that the event is shown as cancelled in the portal, inform and refund existing customers and prevent new customers from purchasing tickets.

The below is a domain model for the Ticket Tout scenario given above:

Event name 1.. 1 Offering date time Tickets serial number class allows attendance at venue has ticket number price 1.. 1.." browses runs attends Organisation Customer Purchase 1 credit card number name name makes address date You must assume that no more conceptual classes or attributes need to be added. So don't say "Genre is missing", or anything like that. Given that, identify 5 mistakes in this model