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:25:10 UTC

SYSE.2:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWorking symptomRepair
Environment-as-containerOne box called environment, owner, or suprasystem is assumed to contain every relevant System.Name the participating and affected Systems and the direct relation by which each changes the decision.
Representation lock-inA ConOps, use-case, SysML, FAS, requirements, or story format is required before the working question is known.Start from one linked claim and choose representations only for the use they improve.
Concept-as-finished-architectureAn internal concept diagram is treated as the selected architecture and other structures disappear.Stop this pattern at the grounded architecture question; use C.30 and C.32 for architecture relations, selected structures, and candidates.
Fixed outside worldExternal Systems and Work arrangements are treated as fixed while only the designated System or its intended design may change.Compare actual or proposed changes to the designated System, an external System, their relations, or several subjects; obtain specialist results where needed.
Test-as-benefitOne component or integration test is used as proof of outside use, benefit, acceptance, or complete assurance.State which claim the evidence can support, its conditions, and which use or concept claim remains open.