Open table of contents
Conclusion
Track whether reducing exploration changes the property being checked.
Context
As input and state combinations grow, exploration can reach time or memory limits. Record what remains incomplete before adding constraints.
Design and verification scope
Assess the following responsibilities and boundaries when designing and verifying a configuration.
- State-space explosion
- Harnesses
- Loop bounds
- Assumptions
- Timeouts
- Counterexamples
Decision rationale
Use the relationship between State-space explosion and Counterexamples to compare the responsibilities of the selected approach and alternatives. Separate retained constraints from what the new boundary can change.
Trade-offs
Compare the implementation, maintenance and review work introduced by Harnesses with the control it provides. Include failure paths, operator effort and conditions in which the approach should not be adopted.
Limitations
Record a minimal reproducer, constraints, timings and incomplete runs. Timeouts are not safety evidence.
Related case context
These cases provide attributed design context. They do not establish that the proposed experiments or configurations were delivered in those engagements.