Library / Method Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:35:14 UTC

ME.10:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
“The Method Base is the repository.”Identify the collection, membership rule, edition, publication, access, task set, and observed uses separately.
“The profile row chose the support arrangement.”Use the row only for its exact representation/action claim group; compare and select support configurations in ME.10.
“C.37 selected the representation, so the task passed.”Keep use-bounded disposition separate from performed Work and the receiving task result.
“The PLM route passed, so manual lookup is insufficient.”Record PLM as observed pass and manual lookup as untested unless a declared missing feature proves insufficiency.
“Choose the smallest arrangement for each task and combine them.”Check shared currentness, maintenance, confidentiality, latency, authority, and provider effects; return a retained set or stated split when the union has no supported order.
“The interface gives users access.”Establish the actual access relation and relevant permission; an interface is only one System or presentation element.
“The AI supported the decision.”Name provider interaction, consumed suggestion, reviewing Work, permission, authority, result, and evidence separately, or return the missing branch.
“All components are listed, so the structure is selected.”Keep a proposed organization until A.22 selection-use facts obtain.
“Three users passed, so the team is capable.”Report the three Work-task observations and evaluate capability under A.2.2 only when its holder, Work family, envelope, measures, and window are present.
“Feedback is available through the form.”Require actual feedback Work or SpeechAct and a named receiving use before claiming feedback occurred or was used.