MMT/QVT Declarative (QVTd)
The QVT Declarative (QVTd) component aims to provide a complete Eclipse based IDE for the Core (QVTc) and Relations (QVTr) Languages defined by the OMG QVT Relations (QVTR) language. This goal includes all development components necessary for development of QVTc and QVTr programs and APIs to facilitate extension and reuse.
The QVTo component provides corresponding facilities for the Procedural Language.
QVT Declarative currently provides:
- Editors for QVTc and QVTr
- Parsers for QVTc and QVTr
- Meta-models for QVTc and QVTr
(The EMOF-based implementations of the QVT models are the source of the normative models in ptc/09-11-04 for OMG QVT 1.1.)
QVT Declarative will provide
- a dedicated perspective
- an execution environment for QVTc and QVTo
- an integrated debugger for QVTc and QVTo
The base working document of this component is the OMG QVT 1.2 specification (Meta Object Facility (MOF) 2.0 Query/View/Transformation 1.2 Beta Specification).
The QVTd project includes a special development documentation to identify:
- specification deviance (and explanations)
- specification interpretation
- specification issues
This page is a summary of specification related development choices. Its main purpose is to provide a basis for discussion with the community. Any feed back is welcome. Please use the QVTd newsgroup for the questions and the Bugzilla for issues.
Status and Roadmap
|July 2008||QVT 1.0 models, parsers and editors migrated from GTM/UMLX project|
|August 2008||Editors adapted to use IMP|
|November 2009||Models upgraded and used as basis for OMG QVT 1.1 models|
|August 2012||Work started on QVTr to QVTi chain|
|June 2013||QVTi editing and execution available for Kepler release|
|March 2014||Models upgraded and used as basis for OMG QVT 1.2 models|
|June 2014||QVTi debugging available for Luna release|
Currently working on
After an unsuccessful attempt to use ATL tooling to define a QVTr compiler, an execution engine is being planned that will use transformations and support both QVTc and QVTr.
The OMG specification provides an almost monolithic QVTr to QVTc transformation written in QVTr. This is difficult to understand, and cannot be used until a QVTr execution engine is available.
We therefore plan to transform QVTr to QVTc using QVTc transformations. These will be modularized by semantic concept to aid understanding and facilitate extension and modification. We similarly plan to transform QVTc to a TxVM using transformations to a series of intermediate languages.
More specifically, we recognize that any practical use of a transformation is unidirectional requiring the multi-directional flexibility of QVTr and QVTc to be resolved. We therefore define
- QVTu language as the unidirectional subset of QVTc
- QVTm as the smallest declarative subset of QVTu that supports practical transformation programming
- QVTi as a still smaller syntactic subset of QVTm but with imperative semantics suitable for code synthesis.
Using these subset languages, we plan to realize QVTc and QVTr using the following transformation chains
- QVTi to TxVM using QVTo
- QVTm to QVTi using QVTi
- QVTu to QVTm using QVTm
- QVTc to QVTu using QVTu
- QVTr to QVTu using QVTu
We anticipate that the QVTm language will provide a suitably simple declarative language that will allow for effective application of transformation composition optimizations. These optimizations will be essential to avoid the costs of naive transformation chains. We hope that other transformation languages will provide conversion to QVTm so that transformations developed in a variety of languages can be composed into an efficient composite transformation and then transformed for efficient execution by a good TxVM.
More details on these languages may be found in MMT/QVT Declarative Languages.
Recent work on improving the efficiency of the Eclipse OCL evaluator and providing a direct OCL to Java code generator demonstrates that the OCL evaluator can be regarded as the core of a TxVM. The M2M/QVTO project already exploits this by extending the interpretation capability and adding a debugger. The same interpretation approach should be possible for at least QVTi, QVTm and QVTu, perhaps for QVTc too. Extension of OCL's direct OCL to Java should eliminate the interpretation overheads. Realisation of transformation composition should eventually allow efficient provision of QVTr to QVTc to QVTu to ... and so enable acceptable performance for all languages.
Bug 350917 discusses extending the OCL evaluator with some pattern matching operations to assist in supporting transformations.
The QVT Declarative project is developed by E.D.Willink.
The current commiters are:
- Ed Willink (lead)
- Frédéric Jouault
A QVTd developement environment may be set up by M2M/QVT Declarative Installation.
Questions and discussions about QVT Declarative usage
Questions and discussions about the usage of QVT Declarative should take place on the eclipse.modeling.m2m Eclipse newsgroup for the M2M project (more details about this newsgroup there), of which QVTd is a component. Please, remember to prefix the subject of your QVT Declarative-related posts with [QVTc], [QVTr] or [QVTd].