SOLID PRINCIPLES – INTERFACE SEGREGATION

PRINCIPLE [ISP]

BY PIYAWAN AND NITISAK M

PRESENT IN CERTIFIED SCRUM DEVELOPER CLASS

ORIGIN

Robert C. Martin

INTEND

“No client should be forced to depend on methods it does not use”

Make fine grained interfaces that are client specific

EXAMPLES

REFACTORING

CONCLUSION

• [1] ISP splits interfaces which 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. Such shrunken interfaces are also called role interfaces.

• [2] ISP is intended to keep a system decoupled and thus easier to refactor, change, and redeploy.

Q&A