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

Source changed 2026-11-21 18:11:08 UTC · snapshot created 2026-11-21 18:12:06 UTC · last check 2026-11-21 22:15:20 UTC

A.14:10 - Common Anti-Patterns and How to Avoid Them

  • Member as component. A person, team, document, or object belongs to a collection and is then counted as structurally integrated.
  • Aspect by label. A Characteristic, concern, viewpoint, view, projection, partition, heading, dashboard slice, or time window is called an aspect and entered into a part tree. Recover the claim; require the full AspectOf occurrence when structural parthood is intended.
  • System-role expression as part. A local kind, assignment, or relation position is put into a part tree instead of using its direct pattern.
  • Method as part. A Method, recipe, or algorithm is treated as a structural component instead of using Method, MethodDescription, Work, or transformation patterns.
  • Portion without measure. Some fuel, data, time, or text is named as a portion without measure kind, unit, boundary, and additivity conditions.
  • Phase as replacement or lineage. Another episteme, version label, or Work segment is treated as PhaseOf without applying C.2.1 or A.15.1.
  • Diagram or trace as relation. The presence or form of a breakdown, graph, table or trace is taken as proof of parthood or identity. Inspect its content and the applicable relation and identity rules; the content may supply grounds, while the representation alone establishes no occurrence.