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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:40:10 UTC

SYSE.5:8 - Common Failures and Repairs

FailureSymptomRepair
Incumbent-parts decompositionThe current bill of materials becomes the functional organization.Restate the outside effect and develop rival functional organizations before preserving the incumbent allocation.
Functional element as purchase itemA box named sensor, protection, or storage is treated as a procurement specification or purchase item.Recover the function-like claim, candidate actual or intended bearer, interfaces, placement, capability need, and assembly relation.
One-to-one allocationEvery contribution is forced into one component and every component into one contribution.Permit many-to-many and mode-dependent proposals; inspect joint and shared functioning.
Diagram overlap as relationMatching labels or co-located symbols establish identity, allocation, or functioning.State the direct claim and supporting evidence; keep representation correspondence separate.
Interface label as proofStandard, open, or a connector name establishes compatibility or substitution.State interface conditions and test conformance, integration, intended interaction, and consequential wrong use separately.
Available product as only candidateCatalogue availability is treated as the boundary of possible construction.Keep physical candidate generation separate from the choice of obtaining arrangement; use SYSE.24 when that obtaining choice becomes current.
Unavailable product as no constructionAn unsuccessful search erases candidate bearer descriptions already examined.Retain the candidates and failure reasons; distinguish market absence, physical infeasibility, and missing project capability.
Fewer bearers as automatic improvementConsolidation or a universal platform is assumed superior.State transferred contributions, affected characteristics, scale window, losses, and evidence burden; keep it as one candidate.
AI graph as design truthA generated function graph is accepted because it is connected or plausible.Recover claims and bearers, challenge physical and interface dependencies, and qualify the generator and evidence.
Trial as universal proofOne simulation or bench result establishes full functioning and architecture adequacy.State the Agent, Method, conditions, configuration, observations, claim limits, and the later claim-assessment Work that can use them.
Architecture decision hidden in generationThe preferred candidate is silently selected during modeling.Preserve the decision-usable candidate account, including explicit losses and unresolved claims, as an input to architecture-decision Work governed by SYSE.6.
Whole-project stopOne missing bearer blocks every Work stream.Pause only the unsupported commitment; select another bearer, revise the function, change realization capability, explore, or stop the bounded proposal.