When to use Interface Segregation Principle?
The goal of this principle is to reduce the side effects of using larger interfaces by breaking application interfaces into smaller ones. It’s similar to the Single Responsibility Principle, where each class or interface serves a single purpose.
Which design principle states that clients should not be forced to implement interfaces they don’t use?
The Interface Segregation Principle was defined by Robert C. Martin while consulting for Xerox to help them build the software for their new printer systems. He defined it as: “Clients should not be forced to depend upon interfaces that they do not use.”
How does the interface segregation principle affect concrete classes?
The Interface Segregation Principle alerts us of dependencies on “fat interfaces,” forcing concrete classes to implement unnecessary methods and causing a large coupling between all clients. By using more specific interfaces, we break this coupling between client classes.
What is the principle of Interface Segregation ( ISP )?
The interface-segregation principle (ISP) states that no client should be forced to depend on methods it does not use. The ISP splits interfaces that are very large into smaller and more specific ones so that clients will only have to know about the methods that are of interest to them – Wikipedia
What was Robert C Martin’s Interface Segregation Principle?
The Interface Segregation Principle is one of Robert C. Martin’s SOLID design principles. Even though these principles are several years old, they are still as important as they were when he published them for the first time.
How are interfaces segregated in a coffee machine?
And the EspressoCoffeeMachine interface also extends the CoffeeMachine interface, and defines the brewEspresso method. Congratulation, you segregated the interfaces so that the functionalities of the different coffee machines are independent of each other.