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

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

OPS.11:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
Call every connected diagram a flow network.Different structures and descriptions are collapsed.Apply A.22/E.18/E.18.NET only to the object that meets the corresponding conditions.
Optimize material production while ignoring transaction prerequisites.Product can accumulate without an admissible shipment.Recover the actual goods-issue and shared-resource coupling.
Use evidence from the wrong configuration.A completed test does not support the current release claim.Bind the result to the exact subject and conditions.
Turn missing information into a negative world claim.Lack of evidence is mistaken for evidence of absence.Return the exact unresolved basis and its consequence for use.
Treat a coordinated diagram as permission.The relevant decision-maker may not have authorized the action.Establish whether a valid decision already covers the action. If permission is still needed, obtain it from the holder or report the gap.
Build an exhaustive enterprise map when a smaller account already settles the question.Unneeded modeling work delays the useful result.Select only relations that can affect the choice or the grounds for relying on it.