Reason to Change
← Back to Single Responsibility Principle
A class should have only one reason to change, meaning it should serve one stakeholder or actor. If a class serves multiple actors, changes for one actor can unintentionally break functionality for another.