Format

  1. Phase 1: Call for Cases
  2. Phase 2: Case solution submission
  3. Phase 3: Workshop and live contest

Phase 1: Call for Cases

In order to facilitate the comparison of graph transformation tools, we are solliciting potential case studies. If you have a suitable case study, please describe it shortly but as detailed as needed and submit it to the GraBaTs EasyChair This includes cases that have already been carried out using a given tool. A committee will select a small, but representative set of case studies to be used for the contest.

Case descriptions should include:

  • A short description of the context of the case, with references
  • A clear description of the case itself, including implicit or explicit answers to the following questions:
    • What is the subject to be modeled?
    • What should the model be (able to) do, i.e., what manipulations/rules should be possible?
    • What is the purpose of the model, i.e., what would it be used for from a larger perspective?
    • What are variation points in the case, i.e., divide up you case in core characteristics and extensions?
    • How should the model be used, i.e., are visual aspects important, is manual simulation allowed/required?
    • What are the challenges involved in the case, and if possible, suggestions on how to measure submissions with respect to these challenges?
Moreover, submitters are encouraged to provide a set of reference input/ouput documents (models/graphs) that can be used to evaluate the correctness of solutions to the case study.

Phase 2: Case solution submission

All those who like to participate in the contest are asked to choose one or more case studies, take their favourite graph transformation tool and submit their solutions. Each submission should cover the following issues: a short presentation of the chosen graph transformation tool, a description of the chosen case study variant if any, a presentation of the chosen solution, including a discussion of design decisions. More detailed instructions will be given in the case descriptions themselves.

Solutions were to be submitted by May 22, 2009. See the solutions page for which presentations were accepted for presentation. In addition, it is planned to have a special journal issue where submitters have a chance to improve and write up their solutions.

Your submission should consist of:

  1. The rules you used to model the case(s), plus other electronic resources (input/output models, installation scripts, ...), in such a form that we can reproduce your results by running the tool in question ourselves;
  2. An accompanying document in PDF format in which you briefly (no more than 5 pages) describe what you consider to be the high points of your solution (and if you are courageous, also the disadvantages)
  3. An appendix with a full listing of your solution (including details that may be hidden by the visual editor of the tool)
Please submit to the GraBaTs EasyChair.

Phase 3: Workshop and live contest

Besides the presentation and discussion of the solutions, the workshop will include for the first time a live contest session. During this session, participants will be handed out a case description which they will be asked to solve within the time available on Friday. Solutions will be compared and presented on Thursday, July 2, together with the submitted solutions to the published case studies. In this way we want to compare the usability of the tools for rapid development.

It may be noteworthy that the workshop is also open to MDE practitioners that want to learn more about graph transformation tools from a user perspective. In fact, we especially invite such participants to formulate their criteria for tool evaluation to the other participants!