Visible to the public Transformation Tools Contest 2016 - Call for casesConflict Detection Enabled

No replies
Anonymous's picture

** Call for cases **

9th Transformation Tool Contest 2016

8th July 2016 | Vienna, Austria. |

Part of STAF 2016 (

About TTC

The aim of this event is to evaluate and compare transformation tools, with respect to their expressiveness, usability and performance over a number of challenging case studies. That is, we want to learn about the pros and cons of each tool considering different applications.
A deeper understanding of the relative merits of different tool features will help to further improve the existing tools, to indicate open problems, and to integrate and standardize transformation tools.

This contest is the ninth of its kind after an AGTiVE 2007 session, GraBaTs: The Contest in 2008 and 2009, and the TTC 2010, 2011, 2013, 2014 and 2015 contests.

TTC 2016 is co-located with the international conference on model transformation (ICMT), the international conference on graph transformations (ICGT), the European conference on modelling foundations and applications (ECMFA), the international conference on Tests and Proof (TAP), and the international conference of software engineering and formal methods (SEFM).


There is a wide range of application domains of transformation tools, including software engineering, business intelligence, logistics, healthcare and bioinformatics, as well as semantic web and social network analysis.

Specific areas of transformations relevant for the TTC include (among others):

  • model synchronisation and merging,
  • program manipulation and translation
  • interoperability and migration
  • model execution and simulation
  • verification of models and transformations
  • knowledge extraction and semantic search.

If you are working in one of these area or a different domain where structured data transformations are relevant, please consider submitting a case.

In addition to the above list of applications, we particularly encourage submitting cases for the following focus topics of the TTC 2016:

  • reactive transformations
  • program transformations

TTC Procedure

Phase 1: Case proposal submission. In order to facilitate the comparison of transformation tools, we are soliciting potential case studies. If you have a suitable case study, please describe it shortly but as detailed as needed and submit it to the online submission system. Please include a reference solution to your case to support the evaluation of the correctness of submitted solutions. Our program committee will select a small, but representative set of case studies to be used for the contest.

Case descriptions should answer the following questions:

What is the context of the case? (provide a short description and references)

What is the subject to be modeled? (what are the input and output modeling languages?)

What is the purpose of the models? (what are they typically used for from a larger perspective than the proposed case study?)

What are variation points in the case? (divide up your case in core characteristics and extensions)

What are the criteria for evaluating the submitted solutions to the case?

  • Correctness test: which are the reference input/ouput documents (models/graphs) and how should they be used? Ideally, a case description includes a testsuite, as well as a test driver (The test driver can be an online web service, or a local script that can be deployed in SHARE (see

  • Which transformation tool-related features are importantand how can they be classified? (e.g., formal analysis of the transformation program, rule debugging support, ...)

  • What transformation language-related challenges are important and how can they be classified?(e.g., declarative bidirectionality, declarative change propagation, declarative subgraph copying, cyclic graph support, typing issues, ...)

  • How to measure the quality of submitted solutions, at the design level? (e.g., measure the number of rules, the conciseness of rules, ...)

How can the solutions be evaluated (ranked) systematically using information technology?

Please provide one of the following:

  • a simple spreadsheet (an evaluation form that can be aggregated easily (See for example,

  • a so-called "classification scheme" in ResearchR (See (or a similar web 2.0 platform.)

Please submit at

Your submission should include:

(i) a case description answering the above questions in PDF format using the CEUR-WS style and not exceeding 10 excluding references and appendices, and

(ii) a URL to a publicly available repository hosting service (e.g., github, bitbucket) that contains all test artifacts as well as the evaluation / ranking instrument and any other necessary resources. The repository hosting should additionally provide a basic issue tracking system to keep track of any problems encountered by solution authors. This link should be referenced in the PDF document.

Phase 2: Case solution submission. All those who like to participate in the contest will be asked to choose one or more case studies, take their favorite transformation tool and submit their solutions. A separate call for solutions will be distributed after the cases have been selected.

Phase 3: Open peer review. The solution reviewing before the workshop will be done by other solution submitters. All solution submitters have to review some other solutions to the case that they have addressed. These reviews will not be anonymous, since these reviewers ideally will also be the opponents at the workshop. The purpose of the peer reviewing is that the participants get as much insight into the competitor's solutions as possible and also to raise potential problems. Case submitters should be available at this stage to resolve conflicting interpretations (if any) about the case description.

Phase 4: Workshop and live contest. Besides the presentations of the submitted solutions, the workshop will comprise a live contest. For more details (such as example cases and solutions from previous editions), please consult the TTC website:

Important dates

  • Call for cases: 15 January 2016
  • Case submission deadline: 17 March 2016
  • Call for solutions: 31 March 2016
  • Solution submission deadline: 09 May 2016
  • Open peer review deadline: 25 May 2016
  • Notification: 27 May 2016
  • Workshop: 8 July 2016

All deadlines are on midnight Anywhere on Earth (AoE).


Organizing Committee

  • Antonio Garcia-Dominguez (University of York, United Kingdom)
  • Filip Krikava (Czech Technical University, Czech Republic)
  • Louis Rose (University of York, United Kingdom)

Steering Committee

  • Pieter Van Gorp (Eindhoven University of Technology, The Netherlands)
  • Richard Paige (University of York, United Kingdom)
  • Arend Rensink (University of Twente, The Netherlands)
  • Bernhard Schatz (Technical University Munich, Germany)
  • Albert Zundorf (University of Kassel, Germany)

Program Committee