Translation of QVT Relations into QVT Operational Mappings

Romeikat, Raphael; Roser, Stephan; Müllender, Pascal; Bauer, Bernhard

doi:10.1007/978-3-540-69927-9_10

Cited by 21 publications

(19 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Jouault and Kurtev [8] propose to execute QVT Relations within the ATL Virtual Machine (ATL VM), by transforming QVT Relations into ATL VM code. Romeikat et al [9] propose to transform QVT Relations into QVT Operational Mappings and execute the result with QVT Operational tools such as SmartQVT (http://smartqvt.elibel.tm.fr/). These two approaches transform QVT Relations into code which is on a lower level of abstraction and are therefore not suitable for debugging.…”

Section: Related Workmentioning

confidence: 99%

Common Pitfalls of Using QVT Relations - Graphical Debugging as Remedy

Kusel

Schwinger

Wimmer

et al. 2009

2009 14th IEEE International Conference on Engineering of Complex Computer Systems

View full text Add to dashboard Cite

OMG's Model-Driven Architecture (MDA) has emerged as a new approach for the development of software. For this, the Query/View/Transformation (QVT) standard plays a central role, since it allows for the specification of model transformations. Nevertheless, until now, QVT-tool support in general and debugging support in particular in the context of MDA are rather limited, supposable being a reason, that the adoption of QVT in practice has not yet been achieved. We therefore propose graphical debugging for the QVT Relations language based on TROPIC -a model transformation approach on the basis of Coloured Petri Nets. By enabling debugging on the TROPIC level, one gains several advantages when developing transformations. Firstly, debugging can take place at a high level of abstraction. Secondly, it serves for explicating the operational semantics of a transformation. Thirdly, it provides a homogenous representation of all transformation artifacts. As a first step towards QVT debugging, this paper aims at a deeper understanding of the operational semantics of QVT, classifying common pitfalls by using QVT and discussing how they may be identified at the TROPIC level.

show abstract

Section: Related Workmentioning

confidence: 99%

Common Pitfalls of Using QVT Relations - Graphical Debugging as Remedy

Kusel

Schwinger

Wimmer

et al. 2009

2009 14th IEEE International Conference on Engineering of Complex Computer Systems

View full text Add to dashboard Cite

show abstract

“…Jouault and Kurtev [13] propose to execute QVT Relations within the ATL Virtual Machine (ATL VM), by transforming QVT Relations into ATL VM code. Romeikat et al [21] transform QVT Relations into the QVT Operational Mappings language and execute the result with tools such as SmartQVT 4 . These two approaches transform QVT Relations into code on a lower level of abstraction and seem to be therefore not suitable for debugging QVT Relations adequately.…”

Section: Related Workmentioning

confidence: 99%

A Petri Net Based Debugging Environment for QVT Relations

Wimmer

Kappel

Schoenboeck

et al. 2009

2009 IEEE/ACM International Conference on Automated Software Engineering

View full text Add to dashboard Cite

In the Model-Driven Architecture (MDA) paradigm the Query/View/Transformation (QVT) standard plays a vital role for model transformations. Especially the high-level declarative QVT Relations language, however, has not yet gained widespread use in practice. This is not least due to missing tool support in general and inadequate debugging support in particular. Transformation engines interpreting QVT Relations operate on a low level of abstraction, hide the operational semantics of a transformation and scatter metamodels, models, QVT code, and trace information across different artifacts.We therefore propose a model-based debugger representing QVT Relations on bases of TROPIC, a model transformation language utilizing a variant of Colored Petri Nets (CPNs). As a prerequisite for convenient debugging, TROPIC provides a homogeneous view on all artifacts of a transformation on basis of a single formalism. Besides that, this formalism also provides a runtime model, thus making the afore hidden operational semantics of the transformation explicit. Using an explicit runtime model allows to employ model-based techniques for debugging, e.g., using the Object Constraint Language (OCL) for simply defining breakpoints and querying the execution state of a transformation.

show abstract

“…Romeikat and others [9] translated QVT-R transformations, restricted to the acyclic case, to QVT Operational. The focus is on unidirectional use of QVT-R.…”

Section: Related Workmentioning

confidence: 99%

Enforcing QVT-R with mu-Calculus and Games

Bradfield

Stevens

2013

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. QVT-R is the standard Object Management Group bidirectional transformation language. In previous work, we gave a precise game-theoretic semantics for the checkonly semantics of QVT-R transformations, including the recursive invocation of relations which is allowed and used, but not defined, by the QVT standard. In this paper, we take up the problem of enforce semantics, where the standard attempts formality, but at crucial points lapses into English. We show that our previous semantics can be extended to enforce mode, giving a precise semantics taking the standard into account.

show abstract

Translation of QVT Relations into QVT Operational Mappings

Cited by 21 publications

References 7 publications

Common Pitfalls of Using QVT Relations - Graphical Debugging as Remedy

Common Pitfalls of Using QVT Relations - Graphical Debugging as Remedy

A Petri Net Based Debugging Environment for QVT Relations

Enforcing QVT-R with mu-Calculus and Games

Contact Info

Product

Resources

About