SYSE.5:2 - Problem

Starting from the incumbent construction makes familiar parts look necessary. Starting from a functional graph alone makes abstract elements look like purchasable or assignable things. A supplier search can then be mistaken for proof that the proposed functioning is feasible, while an unsuccessful search can be mistaken for proof that no bearer is possible.

The result is an allocation that survives on paper but fails in use. For example, a bearer may lack power, capacity, placement, access, timing, environmental tolerance, or realization support. Two nominally conforming interfaces may fail to interoperate. Several Systems must cooperate but their joint contribution and failure handling are absent. A standard connector admits a damaging wrong connection. A general-purpose supporting System can reduce one development burden while increasing, for example, latency, energy use, certification Work, or continuing-change burden. Procurement and Work are then organized around functional labels before actual supply items, assembly relations, and evidence needs are known.

The opposite failure is endless decomposition and candidate generation. The engineering account is useful only when it exposes alternatives and conflicts for a named decision question and stops at the first unsupported feasibility dependency.