Rodin Workshop 2009

From Event-B
Jump to navigationJump to search

Rodin User and Developer Workshop July 15-17 2009

While much of the continued development and use of Rodin takes place within the DEPLOY Project, there is a growing group of users and plug-in developers outside of DEPLOY. In July 2009, DEPLOY organised a workshop at the University of Southampton to bring together existing and potential users and developers of the Rodin toolset and to foster a broader community of Rodin users and developers. For Rodin users the workshop provided an opportunity to share tool experiences and to gain an understanding of on-going tool developments. For plug-in developers the workshop provided an opportunity to showcase their tools and to achieve better coordination of tool development effort. Moving towards an open source development project will mean that features that cannot be resourced from within the project can be developed outside the project. It will also help to guarantee the longer-term future of the Rodin platform. This report contains the abstracts of the presentations at the workshop on 16 and 17 July 2009. The workshop was preceded by a tutorial for Rodin Plug-in developers on 15 July.

We would like to acknowledge the support of the School of Electronics and Computer Science at the University of Southampton (especially the organisational work of Maggie Bond), the DEPLOY project and additional government funding.


Michael Butler, University of Southampton

Stefan Hallerstede, Heinrich-Heine-Universität Düsseldorf

Laurent Voisin, Systerel

Report containing the abstracts is available here

Slides from presentations

Wednesday 15 July

Laurent Voisin and Stefan Hallerstede, Rodin Plug-in Development Tutorial

Thursday 16 July

  • Ilya Lopatkin, Towards the SAL plugin for the Rodin platform

Friday 17 July

  • Fredrik Degerlund and Richard Grönblom, A Framework for Code Generation and Scheduling of Event-B Models
  • Eduardo Mazza, A tool for specifying and validating software responsibility
  • James Sharp, Using CSP Refusal Specifications to Ensure Event-B Refinement