Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:55:20 UTC

F.12:7 - Evaluation shapes

The calculation shapes and examples below preserve the delivery Work or population and illustrate an explicit evaluation-Work account. Use that account when its history is current. For an ordinary result, apply the same population, measurement and acceptance conditions through R4 without separately identifying the evaluation occurrence.

F.12:7.1 - Availability share

Promise: availability is at least 99.9% for a calendar month. Delivery Work: the defined service-delivery occurrences or population during that month. Evidence: observations and measurement results for the promised availability characteristic. A System performs evaluation Work; its A.6.1 application binds the in-scope values and returns the declared result.

If the observation model already concerns the promised characteristic, there is no proxy relation. If synthetic probes measure a different characteristic, identify the rule relating it to user experience. State which regions or degradations the probes leave uncovered and how that limits use of their evidence. Without a defining or testing rule return missing-governor. If the rule exists, apply it and limit the verdict to what the probe evidence supports.

F.12:7.2 - Latency percentile

Promise: p95 response latency is at most 120 ms for a stated request population and window. Evidence: response-time observations for that population. Evaluation Work applies the declared sampling, exclusion, and percentile rule and binds its result on the declared acceptance scale. Sampling bias or missing paths can support EvidenceStatus=Inconclusive and leave RequirementStatus=Pending, or yield a locally declared result when the scale specifies that result.

F.12:7.3 - Safety or quality band

Promise: temperature remains within [L,U] during the batch phase. Evidence: calibrated temperature observations for the relevant EntityOfConcern and interval. Evaluation Work applies the stated sampling, uncertainty, and band rule; the exact application binds the values and returns a result on the declared scale. A RequirementStatus follows only through its own rule.

F.12:7.4 - Incident duration

Promise: restoration occurs within 60 minutes for each in-scope incident. Delivery Work: each handling occurrence. Evidence: observations of the defined start and restoration events. Evaluation Work applies the elapsed-time rule to those bindings and returns its declared result. A BPMN design may be a MethodDescription under A.3.2, but it is not either Work occurrence or evidence of the result.