1. UML to Java Review the following UML Design. Create the Java classes which correspond to these designs. As always, you will need to create one Java file for each class you will be implementing. You do not need to add code to the methods but each method that is supposed to return should return a value of the proper type. For example: int getintval() { return 0; } String getstringval() { return ""; } Myclass getclassval() { return null; } void noReturnval() {} Order App FoodOrder +orderNumber: long +additem(i: Menultem) +getTotalCost(): double Customer +name: String +chargeCredit Card) 1 +main(args: String): void Menultem +name: String +price: double +getPrice(): double ComboMeal +discount double +getPrice(): double +additem(i: Menuitem): void Notes: Turn in all source files. There should be five. Make sure your classes are not in a package (that is, they are in the default package). Your source code should all be syntactically correct (no errors). Pay attention to the type of relationship between classes and implement each one appropriately. Watch multiplicities and access specifiers! 1. UML to Java Review the following UML Design. Create the Java classes which correspond to these designs. As always, you will need to create one Java file for each class you will be implementing. You do not need to add code to the methods but each method that is supposed to return should return a value of the proper type. For example: int getintval() { return 0; } String getstringval() { return ""; } Myclass getclassval() { return null; } void noReturnval() {} Order App FoodOrder +orderNumber: long +additem(i: Menultem) +getTotalCost(): double Customer +name: String +chargeCredit Card) 1 +main(args: String): void Menultem +name: String +price: double +getPrice(): double ComboMeal +discount double +getPrice(): double +additem(i: Menuitem): void Notes: Turn in all source files. There should be five. Make sure your classes are not in a package (that is, they are in the default package). Your source code should all be syntactically correct (no errors). Pay attention to the type of relationship between classes and implement each one appropriately. Watch multiplicities and access specifiers