Software Engineering · Architecture
Structuring a system so each part owns one distinct responsibility, with minimal overlap between parts.
Example: The code that renders a page shouldn't also decide business rules like discount eligibility.
In practice: Layered architectures — presentation, business logic, data access — are a direct application of this; mixing layers is usually where tangled 'god classes' come from.