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

Source changed 2026-10-24 05:16:13 UTC · snapshot created 2026-10-24 05:17:08 UTC · last check 2026-10-24 05:40:10 UTC

C.32.LCA:8 - Common Anti-Patterns and How to Avoid Them

MisuseWhy it fails in this useRepair
Draw strategy, planning and execution and call the architecture completeThe drawing leaves the connecting information, authority and feasible actions unspecified.Derive the division from the needed decisions and construct each consequential exchange.
Give every local unit the whole resource limitSimultaneously valid local choices can exceed the shared capacity.Establish a joint allocation or coordination rule and its timing.
Forward every update immediatelyIrrelevant changes consume attention; premature preparation can waste or reserve scarce resources.Identify the receiving action and compare early preparation with waiting.
Escalate every exceptionA decision can arrive after the last useful action or at a participant without the needed means.Bound the actual response path or construct a qualified local continuation.
Call separate controller stability a whole-system guaranteeReference changes, delay, estimation and interactions can violate the individual premises.Derive or obtain the joint behavior under the real interface.
Treat a promise or benchmark average as a hard boundThe required availability, tail behavior or operating condition may be unsupported.Use the warranted bound, uncertainty or conditional claim and change the reliance accordingly.
Improve the local rate while weakening the demanded outcomeThe comparison changes the task and manufactures a gain.Hold the receiving demand fixed or make the changed commitment an explicit alternative.