Design for change and extensibility in Software Engineering - Time & Space Complexity

Time Complexity: Design for change and extensibility

O(n)

Understanding Time Complexity

When designing software to handle change and grow over time, it is important to understand how the cost of making changes scales as the system grows.

We want to know how adding new features or modifying parts affects the work needed as the project size increases.

Scenario Under Consideration

Analyze the time complexity of adding new features using a design that supports extensions.

class FeatureManager {
  constructor() {
    this.features = [];
  }

  addFeature(feature) {
    this.features.push(feature);
  }

  runAll() {
    for (const feature of this.features) {
      feature.execute();
    }
  }
}
    

This code manages a list of features that can be added and run. It supports adding new features without changing existing code.

Identify Repeating Operations

Look at the operations that repeat as the number of features grows.

• Primary operation: Looping through all features in runAll() to execute them.
• How many times: Once for each feature added, so the loop runs as many times as there are features.

How Execution Grows With Input

As you add more features, the time to run all features grows proportionally.

Input Size (n)	Approx. Operations
10	10 feature executions
100	100 feature executions
1000	1000 feature executions

Pattern observation: The work grows directly with the number of features added.

Final Time Complexity

Time Complexity: O(n)

This means the time to run all features grows linearly as you add more features.

Common Mistake

[X] Wrong: "Adding more features won't affect performance much because each feature runs quickly."

[OK] Correct: Even if each feature is fast, running many features adds up, so total time grows with the number of features.

Interview Connect

Understanding how design choices affect time complexity helps you build software that stays efficient as it grows, a skill valued in real projects and interviews.

Self-Check

"What if each feature called other features recursively? How would that affect the time complexity?"

Practice

1. What does design for change primarily aim to achieve in software development?

easy

A. Make it easy to update and modify software without major rewrites

B. Create software that never needs updates

C. Focus only on the initial release speed

D. Avoid adding new features after launch

Solution

1. Step 1: Understand the meaning of design for change

   Design for change means planning software so it can be updated or modified easily later.

2. Step 2: Identify the goal of this approach

   The goal is to avoid major rewrites and reduce effort when changes are needed.

3. Final Answer:

   Make it easy to update and modify software without major rewrites -> Option A

4. Quick Check:

   Design for change = easy updates [OK]

Hint: Think about software that adapts easily to updates [OK]

Common Mistakes:

• Assuming software never needs updates
• Confusing speed of initial release with flexibility
• Believing no new features should be added

2. Which of the following is a correct principle to support extensibility in software design?

easy

A. Always rewrite existing code when adding features

B. Hardcode all feature options to prevent changes

C. Avoid modular design to keep code simple

D. Use the Open/Closed Principle to allow adding features without changing existing code

Solution

1. Step 1: Recall the Open/Closed Principle

   This principle states software entities should be open for extension but closed for modification.

2. Step 2: Match principle to extensibility

   It allows adding new features without changing existing code, supporting extensibility.

3. Final Answer:

   Use the Open/Closed Principle to allow adding features without changing existing code -> Option D

4. Quick Check:

   Open/Closed Principle = extensibility [OK]

Hint: Remember Open/Closed means extend without changing [OK]

Common Mistakes:

• Thinking rewriting existing code is needed
• Avoiding modular design reduces flexibility
• Hardcoding features limits extensibility

3. Consider a software module designed with interfaces to add new payment methods without changing existing code. What is the main benefit of this design?

medium

A. It forces rewriting the entire payment system for each new method

B. It allows adding new payment methods easily without breaking existing ones

C. It prevents adding any new payment methods

D. It makes the code harder to maintain due to complexity

Solution

1. Step 1: Understand interface-based design

   Interfaces let you add new features by implementing new classes without changing existing code.

2. Step 2: Identify the benefit for payment methods

   This means new payment methods can be added easily without affecting current ones.

3. Final Answer:

   It allows adding new payment methods easily without breaking existing ones -> Option B

4. Quick Check:

   Interfaces enable easy feature addition [OK]

Hint: Interfaces help add features without breaking old code [OK]

Common Mistakes:

• Assuming entire system must be rewritten
• Thinking new methods are blocked
• Believing complexity always increases maintenance difficulty

4. A developer wrote code that tightly couples modules, making it hard to add new features. What is the main design flaw here?

medium

A. Using interfaces to separate concerns

B. Good modular design with loose coupling

C. Tight coupling reduces extensibility and increases change difficulty

D. Following the Open/Closed Principle correctly

Solution

1. Step 1: Define tight coupling

   Tight coupling means modules depend heavily on each other, making changes risky.

2. Step 2: Understand impact on extensibility

   This reduces extensibility because adding features requires changing many parts.

3. Final Answer:

   Tight coupling reduces extensibility and increases change difficulty -> Option C

4. Quick Check:

   Tight coupling = hard to extend [OK]

Hint: Loose coupling improves extensibility, tight coupling blocks it [OK]

Common Mistakes:

• Confusing tight coupling with good design
• Thinking interfaces cause tight coupling
• Assuming Open/Closed Principle means tight coupling

5. You have a system that uses a dictionary to map feature names to functions. To design for extensibility, which approach is best when adding new features?

hard

A. Use a plugin system where new features register themselves without changing core code

B. Modify the existing dictionary directly each time a new feature is added

C. Hardcode all features in one large function to avoid dictionary changes

D. Remove old features before adding new ones to keep dictionary small

Solution

1. Step 1: Understand the problem with modifying dictionary directly

   Changing the dictionary each time can cause errors and requires core code changes.

2. Step 2: Explain plugin system advantage

   A plugin system lets new features register themselves independently, keeping core code stable and extensible.

3. Final Answer:

   Use a plugin system where new features register themselves without changing core code -> Option A

4. Quick Check:

   Plugin system = extensibility without core changes [OK]

Hint: Plugins add features without touching core code [OK]

Common Mistakes:

• Directly modifying core dictionaries often
• Hardcoding all features reduces flexibility
• Removing old features unnecessarily