SOLID Class Design Principle
Useful resource to know more about using SOLID principle in enterprise level application.
https://www.codeproject.com/Tips/1000719/High-Cohesion-Low-Coupling-using-SOLID-Principles
Single-responsibility principle
A class should only have a single responsibility, that is, only changes to one part of the software’s specification should be able to affect the specification of the class.
“Software entities … should be open for extension, but closed for modification.”
“Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.” See also design by contract.
Interface segregation principle
“Many client-specific interfaces are better than one general-purpose interface.”
Dependency inversion principle
One should “depend upon abstractions, [not] concretions.”
