CSE Roadmap

Common tier · about 2 hours · 6 parts

Part 1 of 6 · 1 min read

Why this page comes fourth

In this module you will

  • State the interface segregation principle (ISP) in plain words.
  • Explain how a large interface drags unneeded dependencies into callers.
  • Split a fat interface into small ones by who uses each part.
  • Spot an interface that forces classes to write empty or throwing methods.
  • Say what ISP means beyond Java, at the level of libraries and frameworks.

Module 3 ended with a room that could not honour book, and the fix was a smaller interface. This page turns that fix into a rule. The source is "Clean Architecture" (CA), chapter 10. Code was compiled and run before it was written here. Numbers marked "made up" only show the idea.