AGTIVE 2007 raven

AGTIVE 2007 Tool Contest Overview

For the contest we have selected three cases of different size and nature, and with different challenges. You can participate in the contest by submitting your solution to one or more of the cases to the organisers:

Submission of Solutions

Your submission should consist of
  1. The rules you used to model the case(s), plus other electronic resources, 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)
The session at the AGTIVE workshop will take place in the afternoon of Friday, October 12 (please take this into account when planning your trip). It will consist of demonstrations by participants in the contest. Depending on the number of submissions, we may have to make a selection. In order to instil a sense of competition, we will ask the audience to rate submissions based on their demonstration.
You will see that some of the case descriptions contain statistics and results achieved by the submitters. We also STRONGLY encourage submissions that stay BELOW these marks! Be aware that those who submitted a case may have worked a long time on its solution already, and used it as a benchmark to improve their own tools. Tool improvement is what we seek, and this challenge is a means to achieve it. To paraphrase a famous saying:

It's better to have competed and lost, then never to have competed at all.

Organization of the Contest Session at AGTIVE 2007

All submitted  solutions have been collected on a password protected web page.  All participants of this contest session are supposed to read the solution reports of at least one case beforehand. If you like to participate and to read the reports beforehand, you have to register for AGTIVE 2007 first. Thereafter, please contact the organizers to get the access information for the solutions web page.

Contest Session on Friday , October 12th 2007, 14.00 h - 17.30h

14.00 - 15.30 h  Opening and split up in three groups according to the three case studies,
                           short. presentations of solutions, comparsion and discussion of solutions
15.30 - 16.00 h  Coffee break
16.00 - 17.30 h   Reconvened session, presentation of discussion results from each group,
                           general discussion, closing

1. Ludo

Ludo is a game known in Dutch as "Mens-erger-je-niet" and in German as "Mensch-ärgere-Dich-nicht". We have two descriptions of the case
Both versions of the case involve giving rules to simulate the game, with a slightly different emphasis. We leave it to partitipants to select from these descriptions the features that they prefer to model.

Tool challenges:

2. UML-to-CSP

This case is a typical example of a, not too small, model-to-model transformation. A fairly extensive description can be found here:

Tool challenges:

3. Sierpinsky triangles

This case is a pure performance benchmark, involving the construction of all triangles up to a certain number of iterations. Both time and space performance are involved. The rules themselves are quite simple. The case is described here:

Tool challenges: