Restaurant, Menu, Order classes in LLD - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main responsibility of the Restaurant class in a system design?

The Restaurant class manages the overall restaurant details, including its name, location, and the menus it offers. It acts as a container for menus and handles operations like adding or removing menus.

beginner

What does the Menu class typically represent and contain?

The Menu class represents a collection of MenuItems offered by the restaurant. It contains details like the menu name (e.g., Breakfast, Dinner) and a list of MenuItems with their prices and descriptions.

beginner

What is the role of the Order class in the system?

The Order class tracks customer orders. It contains ordered items, quantities, order status (e.g., pending, completed), and calculates the total price. It connects the customer choices to the restaurant's menu.

intermediate

How do the Restaurant, Menu, and Order classes interact in a typical flow?

The Restaurant holds multiple Menus. Each Menu has MenuItems. When a customer places an Order, it references MenuItems from a Menu in the Restaurant. The Order calculates totals based on MenuItem prices.

intermediate

Why is it important to separate Menu and Order classes in system design?

Separating Menu and Order classes allows independent management of the menu (items and prices) and customer orders. This separation supports scalability, easier updates to menus, and clear tracking of orders without mixing concerns.

Which class should contain the list of available dishes in a restaurant system?

A Restaurant

B Order

C Menu

D Customer

The Menu class holds the list of available dishes (MenuItems) offered by the restaurant.

What does the Order class primarily track?

A Employee schedules

B Restaurant location details

C Menu item prices

D Customer orders and their status

The Order class tracks customer orders, including items ordered and their status.

If you want to add a new dish to the restaurant, which class should you update?

A Invoice

B Menu

C Restaurant

D Order

New dishes are added to the Menu class as MenuItems.

Which class is responsible for calculating the total price of an order?

A Order

B Menu

C Restaurant

D Payment

The Order class calculates the total price based on the ordered MenuItems and their quantities.

Why should Menu and Order be separate classes?

A To keep menu management and order tracking independent

B To combine all data in one place

C To reduce the number of classes

D To avoid using databases

Separating Menu and Order keeps menu management and order tracking independent, improving clarity and scalability.

Explain how the Restaurant, Menu, and Order classes work together in a restaurant system.

Think about how a customer chooses items and places an order.

Describe why separating concerns between Menu and Order classes is beneficial in system design.

Consider what would happen if menu and orders were mixed in one class.

Practice

1. Which class should primarily hold the list of available food items and their prices in a restaurant system?

easy

A. Restaurant

B. Menu

C. Order

D. Customer

Solution

1. Step 1: Understand the role of Menu class

   The Menu class is designed to store food items and their prices, acting as the restaurant's catalog.

2. Step 2: Differentiate from other classes

   Order tracks customer requests, Restaurant manages overall operations, Customer represents the diner. Only Menu holds items and prices.

3. Final Answer:

   Menu -> Option B

4. Quick Check:

   Menu = items and prices [OK]

Hint: Menu holds items and prices, not orders or customers [OK]

Common Mistakes:

• Confusing Order with Menu
• Thinking Restaurant holds item prices
• Assuming Customer stores menu data

2. Which of the following is the correct way to add a new item to the Menu class in a typical object-oriented design?

easy

A. menu.addItem('Pizza', 12.99)

B. Menu.add('Pizza', 12.99)

C. menu.insertItem('Pizza', 12.99)

D. addItem(menu, 'Pizza', 12.99)

Solution

1. Step 1: Identify instance method usage

   Adding an item to a Menu instance uses the instance method, so calling menu.addItem(...) is correct.

2. Step 2: Eliminate incorrect syntax

   Menu.add(...) suggests a static method which is unlikely; insertItem is not standard; addItem(menu, ...) is procedural, not OOP style.

3. Final Answer:

   menu.addItem('Pizza', 12.99) -> Option A

4. Quick Check:

   Instance method call = menu.addItem(...) [OK]

Hint: Use instance.method() to add items, not static or procedural calls [OK]

Common Mistakes:

• Using static method call instead of instance method
• Confusing method names
• Calling functions outside class context

3. Given the following code snippet, what will be the total cost of the order?

menu = Menu()
menu.addItem('Burger', 5.0)
menu.addItem('Fries', 2.5)
order = Order(menu)
order.addItem('Burger', 2)
order.addItem('Fries', 3)
total = order.calculateTotal()

medium

A. 17.5

B. 15.0

C. 20.0

D. 12.5

Solution

1. Step 1: Calculate cost for each item

   Burger price is 5.0, quantity 2 -> 5.0 * 2 = 10.0; Fries price is 2.5, quantity 3 -> 2.5 * 3 = 7.5.

2. Step 2: Sum the costs

   Total cost = 10.0 + 7.5 = 17.5.

3. Final Answer:

   17.5 -> Option A

4. Quick Check:

   (5*2)+(2.5*3) = 17.5 [OK]

Hint: Multiply price by quantity, then add all items [OK]

Common Mistakes:

• Adding quantities instead of multiplying by price
• Forgetting to multiply price by quantity
• Mixing up item prices

4. In a system where the Order class adds items without checking the Menu, what is the main issue that can occur?

medium

A. Order will reject all items by default

B. Menu prices will automatically update in Order

C. Order may include items not available in the Menu

D. Restaurant will close automatically

Solution

1. Step 1: Understand the role of validation

   Order should verify items exist in Menu to avoid invalid orders.

2. Step 2: Identify consequence of missing check

   Without checking, Order can contain items not on Menu, causing errors or confusion.

3. Final Answer:

   Order may include items not available in the Menu -> Option C

4. Quick Check:

   Missing validation = invalid items in Order [OK]

Hint: Always check Menu before adding items to Order [OK]

Common Mistakes:

• Assuming automatic price updates
• Thinking Order rejects items by default
• Confusing system behavior with unrelated effects

5. How would you design the Order class to handle multiple orders from different customers simultaneously in a scalable restaurant system?

hard

A. Store all orders in a single list without identifiers

B. Keep orders only in memory without persistence

C. Allow only one order at a time to avoid conflicts

D. Use unique order IDs and store orders in a centralized database with concurrency control

Solution

1. Step 1: Identify need for unique order tracking

   Each order must have a unique ID to distinguish between multiple customers' orders.

2. Step 2: Ensure scalability and data integrity

   Storing orders in a centralized database with concurrency control allows multiple orders simultaneously without conflicts.

3. Final Answer:

   Use unique order IDs and store orders in a centralized database with concurrency control -> Option D

4. Quick Check:

   Unique IDs + concurrency = scalable order handling [OK]

Hint: Use unique IDs and concurrency-safe storage for multiple orders [OK]

Common Mistakes:

• Ignoring concurrency issues
• Using single list causing data overwrite
• Not persisting orders leads to data loss