In the context of programming, UML class diagrams provide an overview of your programming goal without wrapping yourself around the metaphorical axle. UML class diagrams list the two essential components of a class: its fields and its methods. Consider the UML diagram below, which represents the TicketMachine class in your reading. Notice that a horizontal line separates the fields (above) from the methods (below). The symbols preceding each line indicate whether the fields or methods are designated private (-) or public (+).

TicketMachine

- price : int - balance : int - total : int

+ getPrice() : int + getBalance() : int + insertMoney (int amount) : void + printTicket() : void + refundBalance() : int

Think about a machine with which you are familiar, whether it be an ATM or the coffee machine at your office. All machines take some sort of input, generate an output, and can be described by some state. In the case of the TicketMachine class, input is provided via the insertMoney() method, output is generated by methods such as getPrice() and printTicket(), and the state is described by fields like balance. Think about the methods and fields that would best characterize your machine if it were a Java class, including the variable and return types for each.

Post the name of your machine and briefly describe it. Then, generate a UML class diagram for that machine, includingat least twofields andat least fourmethods. Remember, methods can collect input, provide output, or govern the internal operations of the machine itself.