Consider a software system that controls a recycling machine for returnable bottles, cans and crates. A customer can return all three types of items on the same occasion. The system must check, for each item, what type has been returned. The system will register how many items each customer retums and when the customer asks for a receipt, the system will print out what was deposited, the value of the returned items and the total return sum that will be paid to the customer. This system is a standard example within object-oriented software development and has been extensively used as an example during the lectures. A draft class diagram is provided in Figure 1. Customer panel itemReceived(slot : Integer) "printReceipt() Deposit item receiver classifyltem(slot : Integer) : Deposit item createReceiptBasis() printReceipt() Receipt basis additem(item : Deposit item) computeSum() Deposit item number value Receipt printer "print() Carn weight size Bottle weight size Crate weight size Figure 1 Draft class diagram for Recycling Machine Implementation Central to good object-onented design is the principle of separation of concerns. Each class addresses a separate concern. Provide a detailed answer to the following question: Which classes are concerned with interfacing to other software (such as a GUL