Library / Systems Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:45:12 UTC

SYSE.35:4.3 - Define observations and three outcomes

Select observations that can reveal the consequential failures of the changed user task. Include correctness, delay and missing results as the task requires. Infrastructure indicators can help explain effects but do not automatically define user success.

Set the evaluation interval, observation delay and adequate-evidence conditions before judging the candidate. Use an appropriate statistical or domain Method when a quantitative inference requires it. A handful of successful attempts cannot establish a rare-failure probability merely because a tool returns a percentage.

OutcomeMeaning and dependent action
Proceed basisThe stated evidence conditions and acceptance comparison are met for this population and interval; the authorized next exposure may be considered.
Stop basisA stated unacceptable effect or violated operating condition has been observed; apply the qualified restriction or recovery.
InconclusiveRequired observations, attribution or discrimination are insufficient; do not convert absence of a failure signal into a pass.

An inconclusive result can lead to a longer permitted observation, a better measurement, a different representative exercise or abandonment of this exposure strategy. Each changes an identified missing condition; repeatedly waiting on irrelevant traffic does not.