Requirements

Functional Requirements:

• Brew different beverage types from recipes, such as Espresso, Latte, Cappuccino, and Hot Water, each with specific ingredient requirements.
• Track and deduct ingredient quantities (water, milk, coffee beans, sugar) when brewing beverages, rejecting orders if ingredients are insufficient.
• Customize beverage options with extra shots, sugar levels, milk type, or size, adjusting ingredient quantities accordingly.
• Allow an operator to refill ingredient containers to their maximum capacity and display current ingredient levels, alerting when supplies run low.

Non-Functional Requirements:

• List the key non-functional requirements (eg thread safety, extensibility, maintainability, etc.)...

Core Objects & Relationships

Based on the requirements and use cases, identify the main objects of the system and analyze how they interact and relate to each other...

Step 1 — Find the core objects Read the requirements and pull out every noun that has data or behavior. For coffee machine:

Step 2 — Find the relationships

Step 3 — Identify interaction patterns

APIs & Class Members

For each class, define the attributes (data) it will hold and the methods (functions) that operate on the attributes. Ensure they align with the object's responsibilities and adhere to the principle of encapsulation. Write your code in the code editor below.

Deep Dive

Explain design tradeoffs you considered. Check and explain whether your design adheres to SOLID principles. Explain how your design can handle changes in scale and whether it would be easy to extend with new functionalities. Identify areas for future improvement...