Open/Closed Principle (OCP) – Complete Guide

What is OCP?

The Open/Closed Principle (OCP) is a core concept in SOLID programming. It states that software entities should be open for extension but closed for modification. This means we can add new functionality without changing existing code, making the system more stable and maintainable.

Why OCP is Important

• Allows adding new features safely.
• Prevents unintended side effects when extending functionality.
• Supports scalable and maintainable architecture.
• Encourages using abstractions and interfaces.

Stepwise Implementation of OCP

1. Step 1 – Identify Areas Prone to Change: Find parts of the code that often require modifications.
2. Step 2 – Use Abstraction: Define interfaces or abstract classes for core behavior.
3. Step 3 – Extend via New Classes: Implement new functionality using subclasses or new modules.
4. Step 4 – Avoid Modifying Existing Code: Ensure base code is untouched when adding features.
5. Step 5 – Test Extensions: Verify that new functionality works without breaking existing behavior.

Example: OCP in Action

Suppose we have a notification system:

• Base class: Notification
• Subclass 1: EmailNotification
• Subclass 2: SMSNotification

Each new notification type can extend the system without modifying existing classes:

interface Notification {
    void send(String message);
}

class EmailNotification implements Notification {
    public void send(String message) {
        // send email
    }
}

class SMSNotification implements Notification {
    public void send(String message) {
        // send SMS
    }
}
      

This approach allows the system to be extended safely, following OCP principles.