Use a UML modeling tool, of your choice, to develop the domain class diagram for the Cinema E-Booking system. Links for some free tools are available at the contents page on eLC. The class diagram should include all entity classes, dependencies, associations, and multiplicities. Explicitly show composition and aggregation, if any. For each class define the attributes and at least two functionalities identified based on use case analysis. You may not be able to define the exact function signatures; we will specify functionalities during Object Design Phase. Your class diagram should, at least, model the following: -

1.The system will store information about movies (see project document for details).

2- The cinema has one theatre and many showrooms. Each show room has different number of seats.

3- The system should store booking information.

4- A customer may have many bookings. A single booking may have more than one ticket, but all tickets are for the same show time.

5- Shows are scheduled in one of the showrooms. A show is identified by the show Id, data and time, and duration.