<span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; color: rgb(68, 68, 68); "><font class="Apple-style-span" face="'courier new', monospace">[ PDF: <a href="http://is.tm.tue.nl/staff/pvgorp/events/TTC2011/CfC.pdf" target="_blank" style="color: rgb(34, 34, 34); ">http://is.tm.tue.nl/staff/pvgorp/events/TTC2011/CfC.pdf</a> ]<br>
<br>The Transformation Tool Contest (or TTC) aims at bringing the<br>people from application domains together with the people that<br>master tools for solving their transformation problems. Since it<br>is difficult for people unfamiliar with model transformation to<br>
judge whether their problem is appropriate for TTC and, if so, to<br>specify their problem in a way understandable by model<br>transformation professionals, the organizing committee (see<br>below) welcomes any questions in this respect.<br>
<br>This contest is the fifth of its kind (after an AGTiVE 2007<br>session, as GraBaTs 2008 and 2009 workshops, and as the TTC 2010<br>workshop). For the third time, it is organized as a satellite<br>event of the TOOLS conference, this time TOOLS 2011 in Zürich,<br>
Switzerland. Since TOOLS is colocated again with the<br>international conference on model transformation (ICMT), teams<br>from the major international players in the development and use<br>of model transformation tools are expected to participate again.<br>
<br>===> Phase 1: Case proposal submission <===<br><br> In order to facilitate the<br> comparison of transformation tools, we are soliciting potential<br> case studies. If you have a suitable case study, please<br>
describe it shortly but as detailed as needed and submit it<br>
before March 7th to the online submission system. Cases that<br> have already been solved using a particular tool (or general<br> purpose programming language) are also very welcome.<br><br> A committee will select a small, but representative set of case<br>
studies to be used for the contest. Case descriptions should<br> answer the following questions:<br><br> • What is the context of the case?<br> (provide a short description and references)<br> – What is the subject to be modeled?<br>
(what are the input and output modeling languages?)<br> – What is the purpose of the models?<br> (what are they typically used for from a larger perspective than<br> the proposed case study?)<br><br> • What are variation points in the case?<br>
(divide up your case in core characteristics and extensions)<br><br> • What are the criteria for evaluating the submitted solutions<br> to the case?<br> – Correctness test: which are the reference input/ouput<br> documents (models/graphs) and how should they be used?<br>
Ideally, a case description includes a testsuite, as well<br> as a test driver (an online web service, or a local script<br> that is deployed in <a href="http://is.tm.tue.nl/staff/pvgorp/share/" target="_blank" style="color: rgb(34, 34, 34); ">http://is.tm.tue.nl/staff/pvgorp/share/</a>).<br>
– Which transformation tool-related features are important<br> and how can they be classified?<br> (e.g., formal analysis of the transformation program, rule<br> debugging support, ...)<br> – What transformation language-related challenges are <div>
important and how can they be classified?</div><div> (e.g., declarative bidirectionality, declarative change </div><div> propagation, declarative subgraph copying, cyclic graph </div><div> support, typing issues, ...) </div>
<div> – How to measure the quality of submitted solutions, at the </div><div> design level?</div><div> (e.g., measure the number of rules, the conciseness of rules, </div><div> ...)</div><br> • How can the solutions be evaluated systematically using<br>
information technology?<br> Please provide one of the following:<br><br> – a simple spreadsheet (an evaluation form that can be<br> aggregated easily.<br> See for example <a href="http://is.tm.tue.nl/staff/pvgorp/events/TTC2010/synthesis-evaluation.pdf" target="_blank" style="color: rgb(34, 34, 34); ">http://is.tm.tue.nl/staff/pvgorp/events/TTC2010/synthesis-evaluation.pdf</a>,<br>
<br> – a so-called "classification scheme" in ResearchR<br> (or a similar web 2.0 platform.)<br> See <a href="http://swerl.tudelft.nl/twiki/pub/Main/TechnicalReports/TUD-SERG-2010-10.pdf" target="_blank" style="color: rgb(34, 34, 34); ">http://swerl.tudelft.nl/twiki/pub/Main/TechnicalReports/TUD-SERG-2010-10.pdf</a><br>
<br> Please submit at <a href="http://www.easychair.org/conferences/?conf=ttc2011" target="_blank" style="color: rgb(34, 34, 34); ">http://www.easychair.org/conferences/?conf=ttc2011</a><br> Your submission should include (i) a case description (in PDF<br>
format) answering the above questions, (ii) a ZIP archive that<br> contains all test artifacts, and (iii) an evaluation scheme (a<br> spreadsheet file or a pointer to an online "classification<br> scheme").<br>
<br>Besides the presentations of the submitted solutions, the<br>workshop will comprise a live contest. For more details (such<br>as example cases and solutions from previous editions), please<br>consult the website of the last, completed TTC:<br>
<a href="http://is.tm.tue.nl/staff/pvgorp/events/TTC/" target="_blank" style="color: rgb(34, 34, 34); ">http://is.tm.tue.nl/staff/pvgorp/events/TTC/</a><br><br>! Important dates !<br><br>+-------------------------------+--------------+-----------------+<br>
| Event | Deadline | Interval to |<br>| | | next deadline |<br>+-------------------------------+--------------+-----------------+<br>+-------------------------------+--------------+-----------------+<br>
| Call for cases | 24 January | 6 weeks |<br>| Case submission deadline | 7 March | 2 weeks |<br>| Call for solutions | 21 March | 6 weeks |<br>| Solution submission deadline | 2 May | 3 weeks |<br>
| Notification | 23 May | 5 weeks |<br> --------------------------------+<br>| Workshop | 29-30 June 2011 |<br>+-------------------------------+--------------------------------+<br>
<br>Organizing Committee<br><br>• Steffen Mazanek (formerly Universität der Bundeswehr München)<br>• Louis Rose (University of York, United Kingdom)<br>• Pieter Van Gorp (Eindhoven University of Technology, The<br> Netherlands)<br>
<br>Steering Committee<br><br>• Richard Paige (University of York, United Kingdom)<br>• Arend Rensink (University of Twente, The Netherlands)<br>• Bernhard Schätz (Technische Universität München, Germany)<br>• Albert Zündorf (University of Kassel, Germany)<br>
<br>Case Committee<br><br>• Jordi Cabot, (École des Mines de Nantes, INRIA, France)<br>• Barbara König (University of Duisburg-Essen, Germany)<br>• Tihamér Levendovszky (Budapest University of Technology and<br> Economics, Hungary)<br>
• Steffen Mazanek (formerly Universität der Bundeswehr München,<br> Germany)<br>• Anantha Narayanan (Vanderbilt University, Nashville, Tennessee)<br>• Arend Rensink (University of Twente, The Netherlands)<br>• Louis Rose (University of York, United Kingdom)<br>
• Bernhard Schätz (Technische Universität München, Germany)<br>• Gabriele Taentzer (University of Marburg, Germany)<br>• Pieter Van Gorp (University of Antwerp, Belgium)<br>• Gergely Várro (Budapest University of Technology and Economics,<br>
Hungary)<br>• Albert Zündorf (University of Kassel, Germany)<br><br>Looking forward to your submission,<br clear="all">Pieter Van Gorp, Assistant Professor (UD)<br> Information Systems Group, School of Industrial Engineering <br>
Eindhoven University of Technology (TU/e), The Netherlands<br> Phone: +31 40 247 2062, Skype: pvgorp, Fax: +31 40 243 2612<br> <a href="http://is.tm.tue.nl/staff/pvgorp/research/" target="_blank">http://is.tm.tue.nl/staff/pvgorp/research/</a><div style="display:inline">
</div><br>
</font></span>