CCP is the component-level equivalent of which SOLID principle?

CCP is the component-level equivalent of which SOLID principle?

• A. ISP
• B. DIP
• C. LSP
• D. SRP

Answer: (D)

Single Responsibility Principle means a module should have one reason to change. At the component level, this translates to keeping a component focused on a single cohesive purpose. When a component tries to do multiple unrelated things, changes in one area cause ripple effects in others, making the component harder to maintain and reuse. So, the component-level equivalent is SRP: each component should encapsulate one well-defined responsibility. Other SOLID principles cover different concerns: interface size and client-specific needs (ISP), dependency direction (DIP), and substitutability of derived types (LSP). They don’t map as directly to the idea of a single, cohesive responsibility within a component. For example, a UI component that both fetches data and renders it violates SRP, and you’d split it into a data service and a presentation component to restore a single responsibility per component.

Single Responsibility Principle means a module should have one reason to change. At the component level, this translates to keeping a component focused on a single cohesive purpose. When a component tries to do multiple unrelated things, changes in one area cause ripple effects in others, making the component harder to maintain and reuse. So, the component-level equivalent is SRP: each component should encapsulate one well-defined responsibility.

Other SOLID principles cover different concerns: interface size and client-specific needs (ISP), dependency direction (DIP), and substitutability of derived types (LSP). They don’t map as directly to the idea of a single, cohesive responsibility within a component. For example, a UI component that both fetches data and renders it violates SRP, and you’d split it into a data service and a presentation component to restore a single responsibility per component.