SYSE.5:0 - Use This When

Use this pattern when engineers can name a desired outside effect, use situation, or observed functioning failure, but have already treated one familiar bearer cue—for example, a component, product, service, software partition, or supplier offering—as the only candidate. Use it also when a functional diagram exists but no one can show which actual Systems or intended System referents could bear the contributions named by its claims under decision-relevant conditions—for example, operating, interface, placement, integration, or assurance conditions.

The first result is an account that compares several functional organizations with the Systems and interfaces that could realize them. It records proposed many-to-many allocations, the conditions under which each proposal could work, conflicts among proposals, evidence limits, and the first unsupported dependency. The account is a claim-bearing episteme used by later architecture-decision Work. Realization and integration require performed Work; observed functioning and evidence require their own grounding.

First move. In one sentence, name the required outside effect, the current decision question, and the first familiar bearer assumption. Add one materially different way in which the contribution might instead be borne. If no bearer or allocation choice is current, stop and use A.6.F for the function-like claim.

Use this pattern while an allocation choice can change an engineering decision. For one function-like claim, use A.6.F; for one module or interface claim, use A.6.M; for transdisciplinary candidate synthesis across several structures, use C.32; and for choosing an architecture from developed alternatives, use SYSE.6. When a subject-specific Method—for example, one for physics, software semantics, clinical action, electrical protection, or structural integrity—determines the answer, use the relevant application DPF with this allocation account.