Why Inheritance and interface notation in LLD? - Purpose & Use Cases

The Big Idea

What if you could fix a bug once and watch it disappear everywhere instantly?

The Scenario

Imagine building a software system where every new feature requires copying and rewriting similar code again and again, like manually drawing each piece of a puzzle instead of using ready-made shapes.

The Problem

This manual approach is slow and full of mistakes. If you want to change a common behavior, you must find and update every copy, risking inconsistencies and bugs.

The Solution

Inheritance and interface notation let you define shared behaviors once and reuse them easily. Interfaces set clear contracts, and inheritance allows new parts to build on existing ones without repeating code.

Before vs After

✗ Before

class Car { void start() { /* code */ } }
class Truck { void start() { /* code */ } }

✓ After

class Vehicle { void start() { /* code */ } }
class Car extends Vehicle {}
class Truck extends Vehicle {}

What It Enables

It enables building flexible, maintainable systems where changes in one place update all related parts automatically.

Real Life Example

Think of a smartphone app where many screens share common buttons and behaviors. Using inheritance and interfaces, you define these once and apply them everywhere, saving time and avoiding errors.

Key Takeaways

Manual code duplication is slow and error-prone.

Inheritance and interfaces promote code reuse and clear design.

They make systems easier to maintain and extend.

Practice

1. What does the notation <|-- represent in system design diagrams?

easy

A. Dependency, where one class depends on another

B. Interface implementation, where a class follows a set of rules

C. Inheritance, where one class is a specialized version of another

D. Aggregation, where one class contains another

Solution

1. Step 1: Understand notation meanings

   The notation <|-- is used to show inheritance in system design diagrams.

2. Step 2: Differentiate from interface notation

   Interface implementation uses <|.., not <|--.

3. Final Answer:

   Inheritance, where one class is a specialized version of another -> Option C

4. Quick Check:

   Inheritance = <|-- [OK]

Hint: Inheritance uses solid arrow <|-- [OK]

Common Mistakes:

• Confusing inheritance with interface implementation
• Mixing aggregation with inheritance notation
• Assuming dependency uses <|--

2. Which of the following is the correct notation for a class implementing an interface?

easy

A. Class <|-- Interface

B. Class <|.. Interface

C. Interface <|-- Class

D. Interface <|.. Class

Solution

1. Step 1: Recall interface implementation notation

   Interface implementation is shown by a dashed arrow <|.. from class to interface.

2. Step 2: Verify direction and notation

   The arrow points from the class to the interface, so Class <|.. Interface is correct.

3. Final Answer:

   Class <|.. Interface -> Option B

4. Quick Check:

   Interface implementation = <|.. from class to interface [OK]

Hint: Interface uses dashed arrow <|.. from class [OK]

Common Mistakes:

• Reversing arrow direction between class and interface
• Using solid arrow for interface implementation
• Confusing interface and inheritance notation

3. Given the following UML snippet:

interface IAnimal
class Dog <|.. IAnimal
class Labrador <|-- Dog

Which statement is true?

medium

A. IAnimal inherits from Dog and Labrador

B. Labrador implements IAnimal and inherits from Dog

C. Dog inherits from Labrador and implements IAnimal

D. Dog implements IAnimal and Labrador inherits from Dog

Solution

1. Step 1: Analyze interface implementation

   Dog implements IAnimal, shown by <|.. from Dog to IAnimal.

2. Step 2: Analyze inheritance

   Labrador inherits from Dog, shown by <|-- from Labrador to Dog.

3. Final Answer:

   Dog implements IAnimal and Labrador inherits from Dog -> Option D

4. Quick Check:

   Interface = <|.., Inheritance = <|-- [OK]

Hint: Dashed arrow = interface, solid arrow = inheritance [OK]

Common Mistakes:

• Mixing inheritance and interface directions
• Assuming interface inherits classes
• Confusing which class inherits which

4. Identify the error in this UML notation:

class Vehicle <|.. Car
interface Drivable <|-- Vehicle

medium

A. Vehicle cannot implement Car because Car is a class

B. Drivable cannot inherit Vehicle because interfaces use dashed arrows for inheritance

C. Arrow directions are reversed for both lines

D. No error, notation is correct

Solution

1. Step 1: Check first line meaning

   Vehicle <|.. Car means Vehicle implements Car, but Car is a class, not an interface, so this is invalid.

2. Step 2: Check second line meaning

   Drivable <|-- Vehicle means Drivable inherits Vehicle, but Drivable is an interface and Vehicle a class, so invalid.

3. Final Answer:

   Vehicle cannot implement Car because Car is a class -> Option A

4. Quick Check:

   Classes implement interfaces only [OK]

Hint: Classes implement interfaces, not other classes [OK]

Common Mistakes:

• Allowing classes to implement classes
• Reversing inheritance arrow direction
• Ignoring interface vs class roles

5. You are designing a system where Smartphone inherits from Device and implements two interfaces: Camera and GPS. Which UML notation correctly represents this?

hard

A. Smartphone <|-- Device
Smartphone <|.. Camera
Smartphone <|.. GPS

B. Device <|-- Smartphone
Smartphone <|.. Camera
Smartphone <|.. GPS

C. Device <|.. Smartphone
Camera <|-- Smartphone
GPS <|-- Smartphone

D. Smartphone <|.. Device
Camera <|.. Smartphone
GPS <|.. Smartphone

Solution

1. Step 1: Identify inheritance direction

   Smartphone inherits from Device, so arrow <|-- points from Smartphone to Device: Smartphone <|-- Device.

2. Step 2: Identify interface implementation

   Smartphone implements Camera and GPS interfaces, so dashed arrows <|.. point from Smartphone to each interface.

3. Step 3: Verify all notations

   Smartphone <|-- Device
   Smartphone <|.. Camera
   Smartphone <|.. GPS

   correctly shows inheritance and interface implementation directions.

4. Final Answer:

   Smartphone <|-- Device Smartphone <|.. Camera Smartphone <|.. GPS -> Option A

5. Quick Check:

   Inheritance arrow points to parent, interface arrow dashed from class [OK]

Hint: Inheritance arrow points to parent class, interface arrow dashed from class [OK]

Common Mistakes:

• Reversing inheritance arrow direction
• Using solid arrow for interface implementation
• Pointing interface arrows from interface to class