Requirements and Physical Block diagram analysis; Class diagram for system

The problem: You have been assigned the task to implement a Point of Sale (POS) system for a restaurant. However, before you can begin work, you have been asked by the team’s system engineer to review a set of system requirements and a high level physical block diagram. You have also been asked to describe how you would go about implementing the POS system. Your description should include: what steps you would need to take to implement the system, what tests are needed to verify the system, and a class diagram of what classes you might need. NO CODING IS REQUIRED. Be as formal or as informal as you want, but be prepared to defend your answers and for additional requirements or changes to be provided on-the-spot during the audition. If you find yourself creating lots of new diagrams, making formal requirements, etc., you are probably doing too much work. Your presentation should provide: Your review of the provided system requirements and high level physical block diagram. Your steps to implement the system A list of tests to verify the system Class diagram for the system, including public/private variables and methods Additional considerations for your review: Are the requirements good? If not, describe why. Are the requirements complete? If not, describe what is missing and how they need to be fixed. Is the physical block diagram complete? If not, describe what is missing. Is the physical block diagram consistent with the requirements? If not, describe the differences and how they should be addressed. What else is required before a software design can be created and implementation can begin? System Requirements The system shall provide point of sale (POS) functionality. The system shall support a threshold of 10 tables, with a goal of 30 tables. A table shall support a minimum of 1 seat. The system shall support combining a minimum of 2 tables to a maximum of 3 tables. The system shall support a minimum of 1 active waiter to a maximum of 5 active waiters. The system shall support a minimum of 10 menu items to a maximum of 50 menu items. A menu item shall contain at a minimum the following fields: unique identifier, friendly name, cost, serving size, ingredients list, date created, whether or not a house specialty, and calorie information. The system shall maintain a list of menu items ordered by seat at a table. The system shall calculate the cost of the menu items ordered by a table (bill), including applicable taxes. The system shall generate a printed copy of the bill for a table. The printed bill shall display at a minimum: table identifier, waiter name, current date, current time, list of items ordered, cost associated to each item, and applicable taxes. The system shall accept both electronic and cash payment of a bill. The system shall generate a receipt of the paid bill which includes at a minimum: fields on the original printed bill, area for customer to fill in tip amount, area for customer to fill in total amount, and area for customer to sign as applicable. The system shall support adding a tip to an electronic payment before the payment is finalized. The system shall support separating the menu items order by a table by a group of 1 or more seats. The system shall generate a printed copy of the bill for each group of seats at a table. The POS system shall integrate into the inventory system. The POS system shall decrease the inventory as appropriate for each menu item ordered by a seat at a table.