Criteria

Maintained relationships explain which requirements each design decision addresses, which code implements that design, and which tests verify the required behaviour.

A complete, integrated description of the intended system for a selected version is available before implementation finishes. Proposed, approved but unimplemented, and implemented changes are distinguishable. Delivered code identifies the governing design version.

A check identifies a possible disagreement and opens or updates an affected-area finding or task. Review decides whether code, documentation or both need correction. The finding is tracked through correction and recheck.

Maintained relationships, constraints and version baselines identify affected requirements, designs, code and tests, and support evaluating alternatives against the same requirements. The assessment records trade-offs, assumptions and unanswered questions.

At the end of implementation, executable tests check delivered behaviour against requirements or acceptance criteria. Results identify the tested code version and show passed, failed, missing and unverified requirements.

A retained record identifies the delivered build and changes, governing requirement and design versions, reviews, approvals and waivers. It references the applicable test results.

The workflow definitions, orchestration and checks can continue running on different supported systems without the original hosted factory service.