F.Interface Segregation Principle (ISP)

    1. Summary
      1. Clients should not be forced to depend upon interfaces that they don't use.
      2. Clients should not be forced to implement interfaces they don't use
      3. Instead of one fat interface many small interfaces are preferred based on groups of methods, each one serving one submodule. 
      4. If the design is already done fat interfaces can be segregated using the Adapter pattern.
      5. If we are going to apply it more than is necessary it will result a code containing a lot of interfaces so due care need to be given during design.
      6. This bring you closure to ‘Single responsibility principle.”
    2. Applicability
      1. Interface Design
    3. References 
      1. http://www.oodesign.com/interface-segregation-principle.html