C.13:7.1 - Common Anti-Patterns and How to Avoid Them

• Constructor as public relation. A Γ_m trace is shown as the relation the working reader should use. Keep the exact direct relation in ordinary prose and use the trace only for the construction account.
• Trace as cause. A diagram, formula, parts list, or trace publication is said to create the assembly. Recover the actual inputs, obtaining relations, assembly, and identity rule.
• Item in a collection treated as a component. A set construction is used to infer integrated assembly structure. Keep collection belonging distinct; use sum only after constructive part relations and assembly independently obtain.
• Same parts, same whole. Two assemblies with the same component names are treated as one whole. Compare their obtaining relations, assembly rules, boundaries, and identity conditions.
• Temporal constructor drift. A phase, schedule, or assembly order is modeled as a Compose-CAL constructor. Keep temporal and method claims in their own planes.
• Method or work shortcut. Recipe steps, plan items, or WBS rows are called parts of an actual method or work occurrence. Use the direct method- or work-composition owner first.
• Transformation shortcut. Changes of constituents are called parts of one transformation because the entity was assembled. Return the exact missing transformation-composition governor and retain the separately identified changes.