Verification Coverage vs Verification Complexity
Prioritise verification effort by requirement criticality and reuse evidence across related requirements to satisfy lifecycle process obligations without unmanageable complexity.
CyberTRIZ analysis · Space contradiction RMA018 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Spacecraft verification must demonstrate that requirements are satisfied across hardware, software, interfaces, environments, and operational conditions. Increasing coverage can require large numbers of test cases, simulations, inspections, and analyses. As verification expands, maintaining traceability and interpreting results can become increasingly difficult.
Space TRIZ Resolution
Verification should be organized around requirement criticality and information value. Common verification activities can satisfy multiple related requirements, automated environments can execute repetitive cases, and model-based traceability can connect evidence directly to requirements. Testing should concentrate on interactions and uncertainties that cannot be demonstrated efficiently through other methods.
Applicable TRIZ Principles
Principle 5 – Merging combines compatible verification objectives within shared activities.
Principle 6 – Universality uses individual evidence to support multiple requirements where technically justified.
Principle 23 – Feedback redirects verification effort according to unresolved uncertainty.
Expected Outcome
Greater verification coverage
Lower verification-management complexity
Improved requirement traceability
More efficient use of test resources
Decision Indicators
Early indicators include:
Verification matrices grow without corresponding improvement in confidence.
Similar requirements are tested independently.
Teams struggle to maintain links between requirements and evidence.
Repetitive verification consumes substantial engineering effort.
High-risk interactions receive less attention than routine requirement checks.