Should the requirement template include a section about acceptance criteria or verification method? Should the verification method be an enum field?
Systems engineering has converged on four (INCOSE, ISO/IEC/IEEE 15288, MIL-STD-961 lineage):
Inspection — examination of the item or its documentation against the requirement, without operating it: design review, code review, configuration inspection, dimensional check. Sometimes labelled Examination or Review of design.
Analysis — reasoning from established theory, models, calculation, simulation, or similarity to an already-verified item. Includes worst-case analysis and statistical inference from partial test data.
Demonstration — operating the item and observing qualitative or functional behaviour, without instrumented measurement. "The operator can complete the recovery procedure."
Test — operating under controlled, defined conditions with instrumented, quantitative data collection against defined pass criteria.
Some organisations add Certification (an accredited third party attests) or Analysis by Similarity as separate entries. Adding entries is fine; the important thing is that the list is closed and each entry is defined in the document's conventions clause, because the boundary between demonstration and test is exactly where people quietly downgrade rigour.
Should the requirement template include a section about acceptance criteria or verification method? Should the verification method be an enum field?
Systems engineering has converged on four (INCOSE, ISO/IEC/IEEE 15288, MIL-STD-961 lineage):
Inspection — examination of the item or its documentation against the requirement, without operating it: design review, code review, configuration inspection, dimensional check. Sometimes labelled Examination or Review of design.
Analysis — reasoning from established theory, models, calculation, simulation, or similarity to an already-verified item. Includes worst-case analysis and statistical inference from partial test data.
Demonstration — operating the item and observing qualitative or functional behaviour, without instrumented measurement. "The operator can complete the recovery procedure."
Test — operating under controlled, defined conditions with instrumented, quantitative data collection against defined pass criteria.
Some organisations add Certification (an accredited third party attests) or Analysis by Similarity as separate entries. Adding entries is fine; the important thing is that the list is closed and each entry is defined in the document's conventions clause, because the boundary between demonstration and test is exactly where people quietly downgrade rigour.