In the figure below you see a fragment of class diagram that represents parking tickets. Tickets have a state (mostly depending on how long they have been waiting, but the details are not relevant here) represented by the hierarchy in the figure; the operation calculateCharge(), which is abstract in the parent class, is overridden in the child classes because its behaviour depends on the state of the ticket (and obviously on the specific child class). Hierarchy of types of parking tickets Briefly explain why the solution in the figure above is not a good one. (7 marks) Draw a (fragment of) class diagram that represents parking tickets and their states by means of the State pattern, with the overriding of calculateCharge() according to the state. [Note: you are not required to detail the classes; names, association(s), inheritance and the single operation calculateCharge() will be sufficient.] (13 marks)