Value
Separation of concerns reduces complex problems into a series of manageable layers and components. It tends to reduce risks as changes are often isolated to a single component as opposed to intermingled throughout a large and complex code base.Encapsulation
Separation of concerns is implemented by encapsulating functionality in components that offer a well-defined interface. Components hide complexity such as user interfaces, business logic, data access and transaction execution from the rest of the code. When something changes, the interface often isn't impacted meaning that the change is isolated to a component.| Overview: Separation Of Concerns | ||
Type | ||
Definition | The principle that code be structured into layers and components that each have distinct functionality with as little overlap as possible. | |
Value | Reduces complexityMakes change more manageable | |
Also Known As | SoC | |
Related Concepts | ||
