 <div class="image-550">
<img src="https://cdn.kahimyang.com/resources-24/isp11.avif" alt="Interface Segregation Principle" loading="lazy"/>
</div>
<h4>
Why ISP?
</h4>
<p>
The goal of ISP is to reduce the impact of changes and ensure that classes that implement interfaces are not burdened with methods they do not use. This leads to a more modular, maintainable, and flexible codebase.
</p>
<h4>
Implementing ISP in C++
</h4>
<p>
Let's start with an example. 
</p>
<p>
Suppose we have a Worker interface that includes several methods:
</p>
<pre style="font-size: 90%;">
<code class="language-cpp normalize-whitespace line-numbers" >
class Worker {
public:
    virtual void writeCode() = 0;
    virtual void fixBugs() = 0;
    virtual void submitReport() = 0;
    virtual void attendMeeting() = 0;
};
</code>
</pre>
<p>
This interface might be too broad, forcing classes that implement it to define methods they do not need. To adhere to ISP, we can split this interface into smaller, more specific ones.
</p>
<h4>
Step-by-Step Implementation
</h4>
<ol class="k-list">
<li>
<b>Identify the responsibilities</b>: Break down the Worker interface into distinct responsibilities.
</li>
<li>
<b>Define smaller interfaces</b>: Create interfaces that encapsulate these responsibilities.
</li>
</ol>


C++ Implementation of the Interface Segregation Principle