Inheritance and interface notation in LLD - Architecture Diagram

System Overview - Inheritance and interface notation

This system models how inheritance and interfaces work in object-oriented design. It shows how classes inherit properties and methods from parent classes and how interfaces define contracts that classes must follow. The key requirement is to clearly represent the relationships between classes and interfaces.

Architecture Diagram

          +----------------+
          |   Interface A  |
          +----------------+
                  ^
                  |
          +----------------+
          |   Class B      |
          +----------------+
                  |
                  v
          +----------------+
          |   Class C      |
          +----------------+

Components

Interface A

interface

Defines a contract with method signatures that implementing classes must follow

Class B

class

Implements Interface A and provides concrete method implementations

Class C

class

Inherits from Class B and can override or extend its behavior

Request Flow - 3 Hops

Class C → Class B

Class B → Interface A

User → Class C

Failure Scenario

Component Fails:Class B

Impact:Class C cannot inherit or use methods from Class B, breaking functionality

Mitigation:Refactor Class C to implement Interface A directly or fix Class B implementation

Architecture Quiz - 3 Questions

Which component defines the method signatures that must be implemented?

A Interface A

B Class B

C Class C

D User

Design Principle

This architecture demonstrates how interfaces define contracts that classes must implement, and how inheritance allows classes to reuse and extend behavior. It separates the 'what' (interface) from the 'how' (class implementation), promoting modular and flexible design.

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