Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 22:54:38 UTC

A.1.STM:9 - Common anti-patterns

Anti-patternRepair
Mantra as fixed work sequenceUse its connected questions to construct and criticize hypotheses; use direct patterns for local truth and WorkPlan for planned order.
Correct parts, unsupported wholeRecover the conditions under which the particular answers can be used together; revise the failed connection or candidate rather than counting completed questions.
Short formula replaces knowledgeReturn to the developed subject explanation and bring its premises and limits into the common account.
A new contract hides an unchanged purposeFor the same organizational work, retain the product use, creator capability and finite local acceptance under section 4.1.1. A new product supply needs its own usable result, recipients and fitness obligations; a new budget or contractor does not provide them.
Role becomes an intrinsic system typeSeparate the SoI role from its holder and description; test the actual System under A.1 and any technical role claim under A.2/A.2.1.
Project equals networkKeep actual project as composite U.Work and E.18.NET as a selected non-agentive U.Structure.
Case equals subnetworkKeep the local question and its receiving use clear. Recover the closure basis when closure is at issue; select a structure only when one receiving use needs the whole organization.
Creator graph importExplain the required creator contributions and their relations. When a TFS network is claimed, identify its members and obtaining cross-member occurrences; an arrow adds no creator kind or generic creates relation.
Shared entity as edgeName the directly governed production, inception, participation, use, feedback, or other occurrence and bind its participants.
Architecture or provision chosen before its use basisRecover receiving changes and the joint functioning of the containing whole at the operating time, then derive the system’s contribution and justify inward and creation-side choices.
Environment description substitutes for the upward moveIdentify the larger functioning whole and the system’s part relation; when either is unknown, investigate it and retain the resulting limit on the dependent design judgement.
Maker treated as suprasystemRecover the creation or provision relation; use a containing-system claim only where the product is actually or prospectively a proper part at the stated time.
Intended system actsKeep it in plan or description content until identity inception; only an existing admitted system can perform Work.
Systemhood proves WorkTest causal participation, system-role assignment, Method, Work, and transformation separately.