Single Responsibility Principle

← Back to SOLID Principles

A class should have one reason to change. Each module or class should be responsible for a single part of the functionality, and that responsibility should be entirely encapsulated by the class.

Key Properties

• Cohesion
• Reason to Change
• Module Boundaries

Related

• Separation of Concerns (broader application)
• Interface Segregation Principle (similar idea for interfaces)

---

solid srp