Formalization of UML Composition in OCL

Abstract

With the increasing use of design models during the development process, developers now face a daunting task to maintain consistency between the design models and their implementation. Consistency maintenance is particularly challenging when a design model language introduces constructs that have no direct counterpart in programming languages. For example, the UML composition, an important relationship in software development, reflects some important principles in software engineering such as encapsulation. Unfortunately, influenced by the ownership model, existing approaches supporting UML composition require the non-accessibility property. However, composition in the UML specification does not support the ownership model. In this paper we present a UML composition formalization using the Object Constraint Language (OCL) that strictly adheres to the UML specification.

Revisiting UML Class Relationship Recovery for Online Education (SEKEEO) (S)

“…To this end, [14,3] check whether a reference to an object is exported by its owner object to a third-party object. However, [15] states that the definition of composition based on the nonaccessibility property is not consistent with the UML spec-ification. [15] further states that the lifetime and the shareability properties are the properties that should be used for recognizing composition relationships.…”

“…However, [15] states that the definition of composition based on the nonaccessibility property is not consistent with the UML spec-ification. [15] further states that the lifetime and the shareability properties are the properties that should be used for recognizing composition relationships. [15] specifies an OCL formalization of the above properties.…”

“…[15] further states that the lifetime and the shareability properties are the properties that should be used for recognizing composition relationships. [15] specifies an OCL formalization of the above properties. However, the complete verification of the above properties needs both static and dynamic code analyses.…”

“…According to [15], composition should be defined based on the lifetime and the share-ability properties. The shareability property requires that an object of a classifier, along with the references to the object, must be owned by at most one composite classifier.…”

Logical Intervention in the Form of Work Breakdown Strategy using Object Constraint Language for e-Commerce Application

“…In [20] an extension of OCL, Soil (Simple OCL-like Imperative Language) has been proposed, using declarative representation. Author in [21] presents a UML composition formalization that strictly adheres to the UML specification. This formalization paves the way for future work to check the consistency between a design model and its implementation in terms of the UML composition.…”