Journal of Systems Thinking · Volume 6, Issue 1 · 2026-07-31
Is UML Made of DSRP?
A Structural Decomposition of Elements, Relationships, Classes, Behavior, and Views
Derek Cabrera
DOI 10.54120/jost.v26i1.dc6umld6 (registration pending)
Abstract
ABSTRACT: Unified Modeling Language (UML) is a standardized modeling language whose vocabulary spans structure, behavior, interaction, deployment, and extensibility. This paper asks whether UML introduces any organizational structure not already expressible by DSRP-484. Following the structural-remainder protocol used in companion analyses of system dynamics and network science, we separate information (I) from organization (O), and we replace the earlier practice of nominating constructs by judgment with a pre-registered extraction rule applied to the OMG UML 2.5.1 normative Abstract Syntax Metamodel. The rule yields 242 metaclasses, of which 100 normalize into their ancestors under a purely structural criterion, leaving a closed candidate set of 142. The inclusion filter excludes none of them, because a normative abstract syntax has already been filtered by the standards body. The entire metamodel, 6,785 elements, is assembled from eighteen element types, of which eight are plainly informational. Ruling the remaining construction kit therefore rules UML: Class is identity and part-whole under two undeclared perspectives; Property performs three jobs on one organization, selected by a flag; Association carries two ordered action and reaction ends; Generalization is Distinction and Relationship simultaneously on one link. Twenty further constructs were selected before ruling on the criterion of whether each could break the claim, including conditionality, the temporal metaclasses, ordering, negation, templates, and the metalevel. A separately counted adversarial block was drawn from the Unified Foundational Ontology, whose authors hold that UML requires more primitives rather than fewer; its four load-bearing challenges are rigidity, existential dependence, four irreducible parthood relations, and relators. No residual organizational primitive X was identified anywhere. A second result concerns what the omissions cost: UML has no way to express negation and builds it eleven times, no way to name a point and hard-codes framing in sixty-nine Boolean flags, no Link construct and builds a surrogate for one, and no loop construct while ninety of its own metaclasses sit inside cycles. The result does not make UML unnecessary. It locates UML as a domain-specific modeling language whose higher-order constructs are generated from a more elemental organizational calculus, and whose recurring workarounds are the measurable cost of the structures it declines to name.
© 2026 Journal of Systems Thinking (JoST) · CC BY-NC-ND 4.0
