Interface Segregation Principle- Program to an interface

by

Robert Martin has a very good explanation of Interface segregation principle (ISP), in his book “UML for Java Programmers”. Based on that, I don’t think ISP is about an interface being “focused” on one logical, coherent group of things. Because, that goes without saying; or, at least it should go without saying. Each class, interface or abstract class should be designed that way.

So, what is ISP? Let me explain it with an example. Say, you have a class A and a class B, which is the client of class A. Suppose, class A has ten methods, of which only two are used by B. Now, does B need to know about all ten methods of A? Probably not – the principle of Information hiding. The more you expose, the more you create the chance for coupling. For that reason, you may insert an interface, call it C, between the two classes (segregation). That interface will only declare the two methods that are used by B, and B will depend on that Interface, instead of directly on A.

So now, 

class A {
  method1()
  method2()
  // more methods
  method10()
}

class B {
   A a = new A()
}

will become 

interface C {
  method1()
  method2()
}

class A implements C{
  method1()
  method2()
  // more methods
  method10()
}

class B {
  C c = new A()      
}

This, prevents B from knowing more than it should.

More Related Contents:

  1. In SOLID, what is the distinction between SRP and ISP? (Single Responsibility Principle and Interface Segregation Principle)
  2. Can’t seem to understand SOLID principles and design patterns [closed]
  3. Does the Single Responsibility Principle work in OOP?
  4. What is an example of the Liskov Substitution Principle?
  5. Examples of GoF Design Patterns in Java’s core libraries
  6. What is Inversion of Control?
  7. What does “program to interfaces, not implementations” mean?
  8. Does functional programming replace GoF design patterns?
  9. Where do I use delegates? [closed]
  10. What is the dependency inversion principle and why is it important?
  11. What is the scope of the Single Responsibility Principle? [closed]
  12. What is the meaning and reasoning behind the Open/Closed Principle?
  13. What is an example of the Single Responsibility Principle? [closed]
  14. Are there any rules for OOP?
  15. Mediator Vs Observer Object-Oriented Design Patterns
  16. What is composition as it relates to object oriented design?
  17. Differences between Proxy and Decorator Pattern
  18. adapter-Any real example of Adapter Pattern [closed]
  19. Learning/Implementing Design Patterns (For Newbies) [closed]
  20. Switch statements are bad? [closed]
  21. What’s the difference between a method and a function?
  22. Mutable vs immutable objects
  23. What is the difference between loose coupling and tight coupling in the object oriented paradigm?
  24. Why do we use Interface? Is it only for Standardization? [closed]
  25. OOP vs Functional Programming vs Procedural [closed]
  26. Simple way to understand Encapsulation and Abstraction
  27. Is it bad practice to make a setter return “this”?
  28. What is an abstract data type in object oriented programming?
  29. How to preallocate an array of class in MATLAB?
  30. Why doesn’t generic ICollection implement IReadOnlyCollection in .NET 4.5?

Leave a Comment