Composite pattern in LLD - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Composite pattern in system design?

The Composite pattern lets you treat individual objects and groups of objects the same way. It organizes objects into tree structures to represent part-whole hierarchies.

beginner

What are the main components of the Composite pattern?

The main components are:
1. Component: The common interface for all objects.
2. Leaf: Represents individual objects.
3. Composite: Represents groups of objects and implements the Component interface.

intermediate

How does the Composite pattern help in managing complex hierarchies?

It simplifies client code by allowing clients to treat single objects and compositions uniformly. This reduces complexity when working with nested structures.

beginner

Give a real-life example of the Composite pattern.

A file system: Files are leaves, folders are composites. Both support operations like open or delete, so clients can treat files and folders the same way.

intermediate

What is a key benefit of using the Composite pattern?

It promotes flexibility and extensibility by allowing new types of components to be added without changing client code.

Which component in the Composite pattern represents individual objects?

A Client

B Composite

C Component

D Leaf

Leaf represents individual objects, while Composite represents groups.

What does the Composite pattern help to simplify?

A Client code by treating objects and groups uniformly

B Database queries

C Network communication

D User interface design

It simplifies client code by allowing uniform treatment of single objects and groups.

In the Composite pattern, what is the role of the Component?

A Handles user input

B Manages database connections

C Defines the interface for objects in the composition

D Stores configuration settings

Component defines the common interface for both leaves and composites.

Which real-world example best illustrates the Composite pattern?

A A network router

B File system with files and folders

C A simple calculator

D A single user login

File systems use folders (composites) and files (leaves) to form a tree structure.

What is a key advantage of the Composite pattern?

A Allows adding new components without changing client code

B Improves database indexing

C Speeds up network requests

D Simplifies UI animations

It promotes extensibility by allowing new components without client changes.

Explain the structure and purpose of the Composite pattern in your own words.

Think about how folders and files work together.

Describe a scenario where using the Composite pattern would be beneficial.

Consider situations with groups and individual items.

Practice

1. What is the main purpose of the Composite pattern in system design?

easy

A. To create a single instance of a class

B. To separate interface from implementation

C. To provide a way to access elements of a collection sequentially

D. To treat individual objects and compositions of objects uniformly

Solution

1. Step 1: Understand the Composite pattern goal

   The Composite pattern allows treating individual objects and groups of objects the same way.

2. Step 2: Compare with other design patterns

   Other options describe different patterns: Singleton (A), Iterator (D), Bridge (B).

3. Final Answer:

   To treat individual objects and compositions of objects uniformly -> Option D

4. Quick Check:

   Composite pattern = treat objects uniformly [OK]

Hint: Composite = treat single and group objects the same [OK]

Common Mistakes:

• Confusing Composite with Singleton pattern
• Thinking Composite only manages single objects
• Mixing Composite with Iterator or Bridge patterns

2. Which of the following is the correct way to declare a composite interface method in a class diagram for the Composite pattern?

easy

A. int calculateSum(int a, int b);

B. void add(Component component);

C. String toString();

D. boolean equals(Object obj);

Solution

1. Step 1: Identify typical Composite interface methods

   Composite pattern usually includes methods like add(), remove(), and getChild() to manage children.

2. Step 2: Match method signature to Composite pattern

   Only void add(Component component); fits the pattern's purpose of managing child components.

3. Final Answer:

   void add(Component component); -> Option B

4. Quick Check:

   Composite interface method = add(Component) [OK]

Hint: Composite interface manages children with add/remove methods [OK]

Common Mistakes:

• Choosing unrelated method signatures
• Confusing standard Object methods with Composite methods
• Ignoring the need to manage child components

3. Given the following code snippet in a Composite pattern implementation, what will be the output?

class Component:
  def operation(self):
    pass

class Leaf(Component):
  def operation(self):
    return "Leaf"

class Composite(Component):
  def __init__(self):
    self.children = []
  def add(self, component):
    self.children.append(component)
  def operation(self):
    results = []
    for child in self.children:
      results.append(child.operation())
    return "Composite(" + ", ".join(results) + ")"

leaf1 = Leaf()
leaf2 = Leaf()
composite = Composite()
composite.add(leaf1)
composite.add(leaf2)
print(composite.operation())

medium

A. Composite(Leaf, Leaf)

B. Leaf, Leaf

C. Composite()

D. Leaf

Solution

1. Step 1: Understand Leaf operation output

   Each Leaf's operation returns the string "Leaf".

2. Step 2: Understand Composite operation output

   Composite calls operation on each child and joins results with commas inside "Composite(...)".

3. Final Answer:

   Composite(Leaf, Leaf) -> Option A

4. Quick Check:

   Composite operation = Composite(Leaf, Leaf) [OK]

Hint: Composite operation joins child operations in parentheses [OK]

Common Mistakes:

• Expecting just 'Leaf' output
• Ignoring the Composite wrapper in output
• Confusing list join syntax

4. In the following Composite pattern code, what is the main error?

class Component:
  def operation(self):
    pass

class Leaf(Component):
  def operation(self):
    return "Leaf"

class Composite(Component):
  def __init__(self):
    self.children = []
  def add(self, component):
    self.children.append(component)
  def operation(self):
    results = []
    for child in self.children:
      child.operation()
    return "Composite(" + ", ".join(results) + ")"

medium

A. The add method does not check component type

B. The Composite class does not initialize children list

C. The operation method does not collect child results

D. The Leaf class does not inherit from Component

Solution

1. Step 1: Analyze operation method in Composite

   The loop calls child.operation() but does not append results to the list.

2. Step 2: Identify missing result collection

   Without appending, results remains empty, causing incorrect output.

3. Final Answer:

   The operation method does not collect child results -> Option C

4. Quick Check:

   Missing append in loop = operation method error [OK]

Hint: Check if child results are collected in operation method [OK]

Common Mistakes:

• Ignoring missing append to results list
• Thinking add method type check is mandatory
• Assuming inheritance error without evidence

5. You are designing a UI framework using the Composite pattern. You want to add a feature to calculate the total number of visible elements in a nested component tree. Which approach best fits the Composite pattern principles?

hard

A. Add a countVisible() method to the Component interface, implemented by Leaf and Composite classes

B. Use a global counter variable updated externally during rendering

C. Only count visible elements in Leaf nodes, ignoring Composite nodes

D. Traverse the tree manually outside the classes to count visible elements

Solution

1. Step 1: Apply Composite pattern principle of uniformity

   Adding countVisible() to Component interface lets all nodes handle counting uniformly.

2. Step 2: Implement counting in Leaf and Composite

   Leaf returns 1 if visible, 0 otherwise; Composite sums counts from children.

3. Final Answer:

   Add a countVisible() method to the Component interface, implemented by Leaf and Composite classes -> Option A

4. Quick Check:

   Uniform method in Component = best Composite design [OK]

Hint: Add counting method to Component interface for uniformity [OK]

Common Mistakes:

• Using external counters breaking encapsulation
• Counting only leaves ignoring composites
• Manual traversal outside object methods