convention-solid-srp

The single responsibility principle (SRP) states that a class or function should have only one reason to change, preventing responsibilities from mixing and changes from rippling across code.

Refactor a God Class by separating mixed responsibilities into focused, cohesive components like data loading, preprocessing, analysis, and reporting to reduce coupling and improve testability.

Detect SRP violations by identifying classes with multiple reasons to change, then applying organizational patterns to separate concerns into focused, modular components.

Separate concerns into distinct classes when a single component handles multiple roles like loading, preprocessing, and reporting, to ensure each class has only one reason to change and ease maintenance.

Applying SRP reduces coupling by isolating changes to single responsibilities, which improves testability and ensures modifications do not ripple across unrelated code modules.

Enforcing single responsibility in code refactoring can increase the number of classes and components, potentially complicating initial code organization if responsibilities are split too granularly.