Association Relationships in Java Using the revised UML Class diagram Resto Fun Final i posted, continue developing the Resto Fun system by modifying class definitions Create an Order class to break the Many-To-Many relationship between Customer and Item. This is a Relationship Class, a class that contains information on the association between to classes. Implement the relationship WaitsOn between Waiter and Customer, knowing that the relationship indicates that this is a One-to-Many relationship mandatory in both ends, i.e., a waiter must wait on a customer and a customer must be waited on by a waiter. Implement the relationship Orders between Customer (Table) and Item, another One-to-Many, since there are many Items a Customers can order, but each Item ordered is for one customer only. Implement the Add relationship between Order and Item. Include a method to assign the Order to a Customer before you start adding Items to the Order! There is enough information now to implement the generateBill method for the Customer (Table) class. Also, the systems will have to indicate that a Waiter has started their shift by displaying the time they started. Also, when they finish a shift. This can be done by implementing the startShift() & finishShift() methods of the Waiter class. [Hint: use the java.time.LocalDateTime class to do the work!] Include a Tester class, which will contain the main method and serve to generate and display two instances of each one of the classes, except abstract classes

Computer Networking: A Top-Down Approach (7th Edition)

7th Edition

ISBN:9780133594140

Author:James Kurose, Keith Ross

Publisher:James Kurose, Keith Ross

Chapter1: Computer Networks And The Internet

Section: Chapter Questions

Problem R1RQ: What is the difference between a host and an end system? List several different types of end...

See similar textbooks

Related questions

Question

Association Relationships in Java

Using the revised UML Class diagram Resto Fun Final i posted, continue
developing the Resto Fun system by modifying class definitions

Create an Order class to break the Many-To-Many relationship between Customer and Item. This
is a Relationship Class, a class that contains information on the association between to classes.
Implement the relationship WaitsOn between Waiter and Customer, knowing that the
relationship indicates that this is a One-to-Many relationship mandatory in both ends, i.e., a
waiter must wait on a customer and a customer must be waited on by a waiter.
Implement the relationship Orders between Customer (Table) and Item, another One-to-Many,
since there are many Items a Customers can order, but each Item ordered is for one customer
only.
Implement the Add relationship between Order and Item. Include a method to assign the Order
to a Customer before you start adding Items to the Order!

There is enough information now to implement the generateBill method for the Customer (Table)

class. Also, the systems will have to indicate that a Waiter has started their shift by displaying the
time they started. Also, when they finish a shift. This can be done by implementing the startShift()
& finishShift() methods of the Waiter class. [Hint: use the java.time.LocalDateTime class to do
the work!]
Include a Tester class, which will contain the main method and serve to generate and display two
instances of each one of the classes, except abstract classes