SYSE.4:10 - Rationale

Engineering assurance is useful when it changes engineering action. Starting from the relied-on claim prevents the project from selecting familiar tests merely because tools, standards, or organizational routines make them available. Naming the decision question makes sufficiency and effort decision-relative: the same evidence can be enough for a reversible exploration and inadequate for safety, legal compliance, certification, or release.

The plan–account distinction keeps expected and actual evidence separate. When a new challenge is worthwhile or required for the selected use, the engineer records it and its intended Work in the plan. A sufficient present basis can instead finish the current question. The account records actual Work, direct results, their bounded evidence use, and changed reliance. Applying that change only to the affected earlier answer makes assurance part of continuing Systems Engineering rather than a final checkpoint.