OCL Well-Formedness Rules as a Verification Mechanism for UML Profiles: A Full-Lifecycle EAI Case Study

Abstract

The UML 1.4.2 standard makes two claims about its lightweight extension mechanism that are rarely tested end-to-end: that profiles can extend UML to model domains far outside object-oriented software, and that this can be done at low cost using the metamodel’s own constraint language, OCL. This paper treats those claims as empirically falsifiable and tests them by constructing and validating a four-phase profile (analysis, design, implementation, deployment) for message-based Enterprise Application Integration (EAI) in small and medium-sized enterprises, in which every domain constraint is expressed as an OCL well-formedness rule (WFR) on the UML metamodel — not merely as prose or a stereotype taxonomy. The profile is exercised against an industrial case study, a laundry facility processing eight metric tons of linen daily for four hospitals under ISO 9002 certification. The resulting account is deliberately self-critical: it reports where OCL-as-WFR succeeded as a specification and verification mechanism, where the UML 1.4.2 Extension System’s own semantic looseness undermined constraint enforcement (in particular a level-crossing problem between the M1 and M2 layers of the MOF hierarchy), and where OCL’s own expressiveness gaps — no tuple types, no closure operator, tri-valued logic with no exception handling — forced work-arounds that a verification and validation audience should know about before adopting the same approach. The contribution is thus not “a profile that works” but a full-lifecycle experience report on using OCL WFRs as a V&V mechanism for a non-trivial domain-specific modelling language built on a standard metamodel extension facility, including its costs and failure modes.