D32 Introduction

The DEPLOY's D32 deliverable is composed of:

• the Rodin core platform and plug-ins (i.e. the DEPLOY tools),
• this document.

The Rodin platform can be downloaded from SourceForge site ([1]). The Event-B wiki ([2]) hosts the documentation of the tool.

This document gives an insight into the work achieved throughout the WP9 Tooling research and development work package, during the third year of the DEPLOY project (Feb 2010-Jan 2011), and depicts the WP9 partner's objectives for the coming and last year of the project.

Among the aims that WP9 partners reached, it might be worth to cite :

• Improved scalability and teamwork ability of the Rodin platform to support industrial deployments, through GUI refactorings and new features, SVN model storage, decomposition, modularisation, flows support, as well as qualitative probabilistic reasoning and others,
• Mathematical extensions can now be used in Rodin. The core of the Rodin platform has been modified and the Theory plug-in has been developed to allow the definition of basic predicates, new operators or new algebraic types.
• Prover performance increased through the addition of a relevance filtering plug-in which raised the number of automatically discharged proof obligations. Moreover, work has been done to establish the soundness of provers and improve the well-definition proof obligation generation,
• Model animation has been improved, now supports multi-level animation and has been applied in WP1-4 partner's case studies,
• Model testing was guided by the needs of WP1-4 partners and several approaches have been investigated,
• Structured types can now be directly defined and used in Rodin through the Records plug-in,
• UML is thighter integrated in Rodin, through new features implementation or even the state-machine animation,
• Code generation, to enable complete support for development, from high-level Event-B models down to executable implementations. An demonstrator tool has been developed.

The various parts making up this document are the following: general platform maintenance, mathematical extensions, provers, UML-B improvements, code generation, teamwork, scalability, model animation, and model-based testing.

Note that each of these parts is describing the improvements made, and is structured as follows:

• Overview. The involved partners are identified and an overview of the contribution is given.
• Motivations. The motivations for each tool extension and improvement are expressed.
• Choices / decisions. The decisions (e.g. design decisions) are justified.
• Available documentation. Some pointers to the Event-B wiki or related publications are listed.
• Planning. A timeline and the current status (as of 28 Jan 2011) is given.