Query Models

Stein, Dominik; Hanenberg, Stefan; Unland, Rainer

doi:10.1007/978-3-540-30187-5_8

Cited by 23 publications

(32 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As already mentioned above and discussed in [26], AOSD is another application area for JPDDs. Here, JPDD are used to visualize selections of join points, i.e., they render those points in program code, or program execution, that are to be enhanced by an aspect.…”

Section: Related Workmentioning

confidence: 96%

“…The respective OCL meta operations are omitted here due to space limitations. Please refer to [26] for a detailed description. Table 3.…”

Section: Relationship Selectionmentioning

confidence: 99%

“…Table 3. Sample relationship patterns for (indirect) relationships, which could be passed to a meta operation as an argument (meta operations are omitted here; see [26] for further details) …”

Section: Relationship Selectionmentioning

confidence: 99%

“…We introduce several abstraction means in order to express various selection criteria, and specify how such selection criteria are evaluated by OCL expressions. Query models built from such abstraction means are called "Join Point Designation Diagrams" [26] (or "JPDD" in short). JPDDs originate in our work on Aspect-Oriented Software Development (AOSD) [7] in general, and on the visualization of aspect-oriented concepts in particular.…”

Section: Introductionmentioning

confidence: 99%

“…We carefully revised that submission taking into account the comments and remarks that we received at the workshop. Meanwhile, JPDDs have also been presented in [26]. While there we have identified the general need to specify queries on software artifacts as a new evolving design issue, here we concentrate on the integration of JPDDs into the MDA context.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

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

Stein

Hanenberg

Unland

2005

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

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.

show abstract

Section: Related Workmentioning

confidence: 96%

“…The respective OCL meta operations are omitted here due to space limitations. Please refer to [26] for a detailed description. Table 3.…”

Section: Relationship Selectionmentioning

confidence: 99%

Section: Relationship Selectionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%