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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 03:45:20 UTC

SYSE.3:4.3 - Find the first unsupported answer

Use the A.1.STM long mantra to keep the architecture result, intended outside use, and builder dependencies in attention. Read the logical dependency backward and find the first unsupported answer that prevents one credible next realization action. First means logically first for this dependency, not earliest in a calendar or prescribed process. Use these six working questions to classify the first gap:

Working questionResult or next practice that resolves the gap
Which existing System could perform the intended Work?Name a candidate transformer System and role condition, or use the System-recognition or specialist-search Method that can supply one.
Can that System perform the Work under the required conditions?State the missing A.2.2 capability claim, threshold, envelope, qualification, or currentness result.
Which Method and means make the intended result plausible?Name the Method question and the missing resource, tool, access condition, or platform contribution.
Can the selected structures be constituted and connected?Name the missing interface, integration, configuration, placement, or production-feasibility result.
Which prior change makes the transformer or means available?Open one recursive realization branch for that System, capability, Method, tool, or platform contribution.
Does the proposed architecture still have an admissible realization?If no branch remains, name the C.32 candidate, architecture decision, or linked use-and-system concept that the failure requires the practitioner to reopen.

Record the first gap even when later gaps are already suspected. Use it to choose the next action.