SYSE.4:1 - Problem frame

Use this pattern when an engineering decision depends on a claim from project focus, use and system concepts, architecture, realization, or a specialist practice, but the project cannot yet say what challenge could change reliance on that claim. Also use it when an engineering result—for example, a test, simulation, model, measurement, inspection, acceptance record, certificate, or operating observation—is being treated as proof beyond the conditions it actually addresses.

First useful move: identify what claim the decision uses and what the present basis supports. Reuse sufficient evidence and its account; narrow or stop reliance where that basis does not support the proposed use. A remaining gap calls for a choice about further inquiry, not automatically another test. When choosing or describing a challenge, five short entries make its contribution recoverable:

1. Claim: the named claim episteme and the subject, conditions, configuration, and time for which it is used.
2. Decision question: the current question or contemplated decision whose answer would change if reliance changes.
3. Challenge: one measurement, analysis, simulation, test, integration check, inspection, or operating observation capable of changing that reliance.
4. Validity boundary: the configuration, conditions, scale, uncertainty, and currentness limits that matter to this use.
5. Affected earlier answer: the project-focus, concept, architecture, realization, or specialist answer that the practitioner must reassess if the result does not support present reliance.

This five-line form is a learning and presentation unfolding, not a WorkPlan or a claim about the order of performed Work. It is enough for the engineering-assurance plan. When a future challenge has been selected, use A.15.2 for a separate WorkPlan: its present EntityOfConcern, effective reference scheme, horizon, and the smallest PlanItem that coordinates the intended Method, performer or local role condition, window, capability, resource, dependency, and result target. The engineering-assurance plan references that WorkPlan; the five lines do not constitute it. Expand the assurance plan only when the decision question depends on several evidence kinds, configurations, conditions, scales, or uncertainty sources. When evidence already exists, add the dated Work, direct result, descriptive A.10 evidence/provenance path, current validity limit, changed reliance, and affected earlier answer to obtain the engineering-assurance account. Reuse an existing account where it already supplies this content; update it where the evidence use or reliance changes. If no new challenge is selected, the supported answer and its limits can complete the work without a new plan or a record of waived checks.

If this move is missed, checks are often chosen after an architecture or implementation is already treated as settled. A passed component test can then stand in for System behaviour and outside benefit; a model confidence score can stand in for validity; or acceptance, certification, permission, release, and assurance can collapse into one pass/fail label. The earlier claim remains unchanged even when the evidence applies to another configuration or contradicts its use conditions.

The payoff is decision-centred evidence use. Engineers ask what result could change the current decision, recover the actual evidence through direct FPF patterns, and revise only the earlier answer to which the result applies. Engineering assurance can therefore accompany other Systems Engineering Work without becoming a terminal stage or a fixed test programme.

Use this pattern when the project must choose or interpret a challenge for an engineering decision. Use A.10 when the remaining question is only provenance for an already named bounded evidence use, C.16 for measurement validity, C.32.ACE for an architecture-characteristic eval programme, A.1.1 for model applicability or use under stated conditions, and C.28 for a causal-use claim. Use B.3 only when an assurance claim or material reliance threshold is current. Neighboring specialist questions—for example, safety, security, ethics, legal compliance, finance, certification, acceptance, permission, or release—retain their own criteria, Methods, Work, and decisions.

At the first consequential use of an assurance cue such as verification, validation, test, acceptance, certification, or assurance, ask: which claim is relied on, for which decision? Name the claim, the challenge or obtained result, its configuration and conditions, and the decision question whose answer can change. Source terminology remains a retrieval cue until those distinctions are recoverable.