Implement the following UML class diagram in JDO. This is an abridged model of ticket-reservation database

-Venue is an abstract class.

-A non-complex venue is modeled as a single venue that is not a subVenues part of any complex venue.

-Each p Price covers all events in eventsOfPriceEvent(p); however, p is the price of each seat in seatsSeat(p) singly.

-Each t Ticket is a valid ticket for all events in eventsOfTicketEvent(t).

-It holds that seat (price seats), i.e., tTicket sSeat [seat(t, s) (price seats)(t, s)].

-It holds that eventsOfTicket = (price eventsOfPrice), i.e., tTicket eEvent [eventsOfTicket(t, e) (price eventsOfPrice)(t, e)].

-The Java classes should use the same class/attribute/relation names used in the above class diagram.

-All inverse relations must be implemented by class fields of suitable names/types.

erformer name string performs eventsOfTicket icket IDcode (key): string vent payment name string date string ayment amount float method : string price payments eentsOfPrice Price amount: float holds ustomerAccount name string email: string seat enue name string location string seats 0..1 subVenues 01 ComplexVenue eat label string Powered ByVisual Paradigm Community Edition seats