A very popular pizza place needs a new system for keeping track of their pizzas and sales. The description for what they want is as follows:

-Our new program shall handle all pizzas and what we sell. All the pizzas have classic names and as you probably know, different toppings. The program shall store each pizza and what topping is on it so that new chefs can easily access it if needed. The toppings are of two categories, the ones that lasts forever and the ones that have an expire date, like for example tomatoes. And of course, we need to have a list of all the toppings we have.

Yeah, and each pizza can of course have several toppings. For each pizza it shall be possible to add or remove toppings as needed. When a new pizza is added to the system the administrator must specify the toppings. What I mean is that it shall not be possible to create pizzas without any topping on them.

The task is to create in Java a UML class diagram that conforms to the description above. Make sure to include the functionality mentioned but also traits specific to the UML class diagram such as for example access modifiers, methods, multiplicity and associations.