Room from improvement and next iterations.
Ten engineers with strong existing knowledge is a proof of concept,
not a validated rollout. The 30% improvement is real within that group,
but these were participants who could identify a subtly wrong
requirement immediately. Extending the test group with engineers of
varying experience levels would likely show smaller gains and surface
fail points the current validation missed.
The deeper open question is review confidence. In safety-critical
systems, a requirement that is efficiently generated but subtly
incorrect is worse than a slow, accurate one. The tool improved
authoring speed, but the cognitive burden of trusting AI-generated
output in a domain with zero tolerance for ambiguity wasn't fully
resolved. A next iteration would need structured validation steps
built into the tool itself.
Mechanisms that help reviewers catch inferred behaviour before it
enters the submitting the requrirements.
With recent advancements in AI, a larger context window is possible,
so adding the requirement guidelines as context as well as more examples,
could yield a more refined output. The potential showed itself and
the ambition of growing to a full-fleshed tool to handle most of
the authoring was present, but not yet attainable.