All the basic design principles converge on the use of abstraction for incorporating flexibility using loose coupling behaviour. Interface Segregation Principle (ISP) is a guideline for designing different interfaces.
Interfaces are useful in designing real world systems, where every object can have multiple aspects. This aspect can be a facet, a behaviour, a role – any entity that qualifies the object with that aspect. Lets take a real world example – a modern cell phone (mobile) acts more than just a phone, it is a phone, a MP3 player and a video player. When I am using it as a MP3 player, I will like to specify the song I want to play and listen to it, nothing more nothing else. When I am using it as a mobile phone, I will like to provide the number and speak, nothing more nothing else. I will get extremely irritated if I am asked for a phone number when I want to listen to a song. It is better if only the relevant questions are asked.
This is the essence of Interface Segregation Principle.
Clients should not be forced to depend upon interfaces that they do not use.
The cell phone had interfaces of a phone and a MP3 player. ISP advises to keep these two interfaces completely independent of each other. This way the phone can be treated purely as a phone or as a MP3 player. Programmatically, I can use only the interface of a MP3 player in my method called
playSong. In future even if the interface for the phone is modified,
playSong would remain the same.
Logically, all ISP says is that if there are two non-cohesive functionalities, keep them separate. So that they can be used independent of other. This avoids design of fat interfaces, and provides a clear design to the user (client). Break the functionalities into atomic interfaces that can be then individually accessed by the user. A good usage of Law Of Demeter can help in designing these atomic interfaces.
- ISP by Robert Martin (pdf)
Back to Design Principles.