A Graphical Notation to Specify Model Queries for MDA Transformations on UML Models

Abstract

Abstract.Specifying queries on models is a prerequisite to model transformations in the MDA because queries select the model elements that are the source of transformations. Current responses to OMG's MOF 2.0 QVT RFP mostly propose to use (and/or extend) OCL 2.0 as specification language for queries. In this paper, we demonstrate that using textual notations (like OCL) quickly leads to complex query statements even for simple queries. In order to overcome this handicap, we present a graphical notation based on the UML that facilitates comprehension of query statements as well as estimation of the (ultimately) selected model elements. We advocate that queries should be specified in terms of user model entities and user model properties (rather than meta model entities and meta model properties) for the sake of feasibility and comprehensibility to the user.

Using UML for Modeling Procedural Legal Rules: Approach and a Study of Luxembourg’s Tax Law

“…Visualization of logical languages. Bottoni et al [3] and Stein et al [27] propose visualizations for OCL, and Amàlio et al [2] -for the Z language [25]. These approaches are not tailored to legal rules and lack means for addressing the information requirements and complexity factors discussed in Section 2.…”

Approaching the Model-Driven Generation of Feedback to Remove Software Performance Flaws

“…In general, model element patterns can be seen as model queries, i.e., diagrammatic notations which corresponds to first-order predicates, which can be naturally expressed by means of OCL [18] expressions. Therefore, each model conforming to APML can be given an OCL-based semantics in a similar way to the approach in [24], which interrogates the elements of a system model to detect antipatterns and eventually to give them a solution. Especially, having an antipattern expressed in APML is convenient as long as we are able to translate it into a concrete modeling language, e.g., UML+MARTE, as describe above by means of weaving models.…”

“…Finally, we highlight that our model-driven approach is inspired by the mechanisms in [24] and [8]. [24] presents a graphical notation to specify selection queries on models based on UML by means of "Join Point Designation Diagrams" (JPDD).…”

“…[24] presents a graphical notation to specify selection queries on models based on UML by means of "Join Point Designation Diagrams" (JPDD). They aim to facilitate comprehension of query statements and estimation of the selected model elements.…”

Designing and Weaving Aspect-Oriented Executable UML Models.

“…In C-SAW, pointcuts and advices are modelled using the ECL language, defined by the authors, which is a subset of OCL. This kind of declarative and OCL-based textual languages might be cumbersome for specifying pointcuts, as demonstrated by Stein et al [28]. Advices are also modelled using the ECL language, therefore, aspect and base models are expressed in different notations, which could generate some understanding problems.…”