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 05:45:20 UTC

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

Anti-patternWorking symptomRepair
Project-name shortcutThe noun in a charter or backlog is used as the selected System without a use or change reason.State the current project decision, generate plausible referents, and compare how each changes the next question.
Tool or provider substitutionThe most visible tool or the System performing realization Work replaces the System whose use the project changes.Keep tool, transformer, provider, changed subject, and project designation as separate claims; compare them as candidates only when each could orient this project.
First-candidate freezeWork has started, so later use or feasibility evidence is treated as irrelevant to project focus.Record the main assumption and reopen condition with the first choice; return evidence to that claim when it changes.
Important-subject inflationA desired state, Work result, description, collection, capability, or transformation is called a System because the project centres on it.Keep the direct subject and use its FPF pattern. Open SYSE.1 only if a System designation is required for the current project decision.
Programme-as-performerShared resources or one programme plan are treated as proof of one composite acting System.Use the programme or portfolio grouping for its coordination decision and establish any System composition separately.