Problem statement: The Odeon Cinema needs software for managing bookings made by customers, the screens, the films and the timing of each projection. The cinema has six screens, and all contain 50 seats, 10 of which are VIP seats (extra room for legs, bigger chair). For each screen, there are 4 shows per day: 1 in the afternoon, 1 in the evening and 2 at night. A customer who wants to book a ticket, needs to select the specific show time. The pricing of the shows is different: the afternoon show is the cheapest, the first night show is the most expensive. Customers can decide to pay using a credit card or cash and may change the date/time of the show, provided there are still seats available for the new selected date. After the show, customers are able to write a review of the film they watched and provide a numerical rating of the film ranging from 1 to 5. All this information will be recorded in the system. After each month, the user of the system must print: - a report containing the number of spectators per film, along with the average rating; Updated August 2021 1 of 3 - a report containing the film which generated the highest Income. Create a UML Use Case Diagram and Use Case descriptions for all the use cases of the system (L01-2) (35 marks available for this part). (If you use the Problem statement from the Level 2 Group project (option 1), you have to author at least two non-trivial Use Cases and have to highlight those Use Cases in the submission.) Mark breakdown - The diagram contains all the possible actors involved in the system (10 marks) - The diagram contains all the uses cases necessary for the functionality of the system and the relations among actors and use cases are correct (15 marks) - All the use case description tables are provided (10 marks)