<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">István Ráth</style></author><author><style face="normal" font="default" size="100%">Gergely Varró</style></author><author><style face="normal" font="default" size="100%">Dániel Varró</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Change-driven Model Transformations</style></title><secondary-title><style face="normal" font="default" size="100%">Proc. of MODELS'09, ACM/IEEE 12th International Conference On Model Driven Engineering Languages and Systems</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">Lecture Notes in Computer Science</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.springerlink.com/content/n60j0r8m14506183/</style></url></web-urls></urls><volume><style face="normal" font="default" size="100%">5795/2009</style></volume><pages><style face="normal" font="default" size="100%">342-356</style></pages><isbn><style face="normal" font="default" size="100%">978-3-642-04424-3</style></isbn><abstract><style face="normal" font="default" size="100%">Nowadays, evolving models are prime artefacts of model-driven software engineering. In tool integration scenarios, a multitude of tools and modeling languages are used where complex model transformations need to incrementally synchronize various models residing within different external tools. In the paper, we investigate a novel class of transformations, that are directly triggered by model changes. First, model changes in the source model are recorded incrementally by a change history model. Then a model-to-model transformation is carried out to generate a change model for the target language. Finally, the target change history model is processed (at any time) to incrementally update the target model itself. Moreover, our technique also allows incremental updates in an external model where only the model manipulation interface is under our control (but not the model itself). Our approach is implemented within the VIATRA2 framework, and it builds on live transformations and incremental pattern matching.</style></abstract></record></records></xml>