Heuristic
Separate opposite requirements in space
The whole system does not have to be uniform just because the requirement was written in one sentence.
When it fits
- Different parts of a system can carry opposite properties at the same time.
When to avoid it
- Partitioning can create duplication, synchronization or security problems; do not treat separation as free complexity.
Why it matters
Ask where property A is needed and where the opposite property is needed. Split the system by region, component, environment, user group or data segment so each area receives the condition that suits it. Check the interface between zones; spatial separation often moves complexity to the boundary.
An example
Keep strict write permissions in the production mutation path while allowing broader read access in a separate analysis environment.
Check your result
Opposing requirements are satisfied in different defined zones with a controlled interface between them.
Keep this limit in mind
- Partitioning can create duplication, synchronization or security problems; do not treat separation as free complexity.
Evidence and sources
Classical TRIZ lists separation in time, separation in space and separation upon condition among methods for resolving physical contradictions.
These are solution-search heuristics; implementation still needs domain evidence, safety and feasibility checks.
Contradictions · Methods for resolving physical contradictions