Develops a new metric for assessing module cohesion, indicating design actions for system components.
This paper instantiates the cohesion schema developed in [1] under change-driver-assignment identity β the principle that elements belong together iff they share the same change-driver set (Ξ(π1) = Ξ(π2)). The general cohesion definition is a (2π + π)-tuple: for π partitioning rules and π non-partition constraints, cohesion reports π (purity, completeness) pairs (2π scalar components) plus π per-constraint scores. This paper addresses the π = 1 case β a single modularizing principle β with π left unspecified as the general parameter for all other system constraints (regulatory requirements, business rules, security classifications, deployment plans, platform requirements, protocol disciplines, and any other conditions on module membership that do not partition πΈ). Causal cohesion is therefore one component of the full cohesion profile, not the complete profile. We develop the full formal apparatus: the system tuple, change drivers, driver assignments, equivalence classes, and the normative decomposition. The result is causal cohesion: a two-dimensional metric π»causal(π) = (purity(π), completeness(π)) in ]0, 1] Γ]0, 1], a (purity, completeness) pair that occupies one partitioning-rule slot in the (2π + π)-tuple, with both axes directly interpretable and mapped to design actions (separate elements of impure modules into distinct modules for low purity, merge for low completeness). The metric satisfies all six necessary conditions, and we provide an operational computation procedure. The metric depends on element-level change-driver assignments Ξ(π); the prerequisite of identifying these from domain artifacts is addressed separately.
No takes yet. Share an insight, caveat, or question.
Yannick Loth (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: