Difference between revisions of "ADVANCE D3.2 Introduction"

From Event-B
Jump to navigationJump to search
imported>Tommy
m
imported>Tommy
m
Line 1: Line 1:
 
The ADVANCE D3.2 deliverable is composed of the present document and the Rodin toolset. The considered Rodin toolset consits of the Rodin core platform and the plug-ins created or maintained in the frame of the ADVANCE project. Indeed, there are contributed plug-ins available for the Rodin core platform which are not maintained within the ADVANCE project, therefore should not be taken into account within this deliverable.
 
The ADVANCE D3.2 deliverable is composed of the present document and the Rodin toolset. The considered Rodin toolset consits of the Rodin core platform and the plug-ins created or maintained in the frame of the ADVANCE project. Indeed, there are contributed plug-ins available for the Rodin core platform which are not maintained within the ADVANCE project, therefore should not be taken into account within this deliverable.
  
The Rodin platform can be downloaded from the SourceForge site<ref>http://sourceforge.net/projects/rodin-b-sharp/files/Core_Rodin_Platform/</ref>. Moreover, the platform includes a collaborative documentation that is collected from two maintained locations :  
+
The Rodin platform can be downloaded from the SourceForge site<ref>http://sourceforge.net/projects/rodin-b-sharp/files/Core_Rodin_Platform</ref>. Moreover, the platform includes a collaborative documentation that is collected from two maintained locations :  
 
* the Event-B wiki<ref name="EventB_wiki">http://wiki.event-b.org</ref>,
 
* the Event-B wiki<ref name="EventB_wiki">http://wiki.event-b.org</ref>,
 
* the Rodin Handbook<ref name="Rodin_handbook_Page">http://handbook.event-b.org</ref>.
 
* the Rodin Handbook<ref name="Rodin_handbook_Page">http://handbook.event-b.org</ref>.
Line 8: Line 8:
 
The present document intends to give a significant overview of the work achieved within the WP3 ''Tooling research and development'' work package, during the first ten months of the ADVANCE project (Oct 2011 - Jul 2011), and aims to let the reader get a glimpse of the WP3 member's contribution plans and objectives.
 
The present document intends to give a significant overview of the work achieved within the WP3 ''Tooling research and development'' work package, during the first ten months of the ADVANCE project (Oct 2011 - Jul 2011), and aims to let the reader get a glimpse of the WP3 member's contribution plans and objectives.
  
It is worth to remind that the ADVANCE project time frame overlaped with... blablabla {{TODO: Continue after lunch}}
+
It is worth reminding that the ADVANCE project time frame overlaped with the end of the EU FP7 DEPLOY project<ref>http://www.deploy-project.eu</ref>. Therefore, the WP3 members that where also members of DEPLOY committed to ...
 +
 
 +
Among the aims that DE partners reached in the past year, it is worth citing :
 +
• Increasing usability and  of the toolset was the main targets regarding scalability.
 +
They have been obtained through major core and UI refactorings.
 +
• A Model-Based Testing plug-in whose development was guided by the needs of WP1-4
 +
partners has been released and documented.
 +
• Increasing prover performance through the addition of several rewriting or inference rules, as
 +
well as two plug-ins, the Export to Isabelle and SMT Solvers which both help to raise the
 +
number of automatically discharged proof obligations.
 +
• An enhanced proving experience, and proving ability with the introduction of user
 +
customizable and parametrizable tactic profiles.
  
Among the aims that WP9 partners reached in the past year, it is worth citing :
 
 
* Improved scalability and teamwork ability of the Rodin platform to support industrial deployments, through GUI refactoring and new features, Subversion model storage, decomposition, modularisation, flow support, as well as qualitative probabilistic reasoning and others,
 
* Improved scalability and teamwork ability of the Rodin platform to support industrial deployments, through GUI refactoring and new features, Subversion model storage, decomposition, modularisation, flow support, as well as qualitative probabilistic reasoning and others,
 
* Mathematical extensions are now supported in Rodin. The core of the Rodin platform has been modified and the Theory plug-in has been developed to allow the definition of new basic predicates, new operators and new algebraic types,
 
* Mathematical extensions are now supported in Rodin. The core of the Rodin platform has been modified and the Theory plug-in has been developed to allow the definition of new basic predicates, new operators and new algebraic types,

Revision as of 10:33, 21 June 2012

The ADVANCE D3.2 deliverable is composed of the present document and the Rodin toolset. The considered Rodin toolset consits of the Rodin core platform and the plug-ins created or maintained in the frame of the ADVANCE project. Indeed, there are contributed plug-ins available for the Rodin core platform which are not maintained within the ADVANCE project, therefore should not be taken into account within this deliverable.

The Rodin platform can be downloaded from the SourceForge site[1]. Moreover, the platform includes a collaborative documentation that is collected from two maintained locations :

  • the Event-B wiki[2],
  • the Rodin Handbook[3].

These locations can be consulted from outside the Rodin tool.

The present document intends to give a significant overview of the work achieved within the WP3 Tooling research and development work package, during the first ten months of the ADVANCE project (Oct 2011 - Jul 2011), and aims to let the reader get a glimpse of the WP3 member's contribution plans and objectives.

It is worth reminding that the ADVANCE project time frame overlaped with the end of the EU FP7 DEPLOY project[4]. Therefore, the WP3 members that where also members of DEPLOY committed to ...

Among the aims that DE partners reached in the past year, it is worth citing : • Increasing usability and of the toolset was the main targets regarding scalability. They have been obtained through major core and UI refactorings. • A Model-Based Testing plug-in whose development was guided by the needs of WP1-4 partners has been released and documented. • Increasing prover performance through the addition of several rewriting or inference rules, as well as two plug-ins, the Export to Isabelle and SMT Solvers which both help to raise the number of automatically discharged proof obligations. • An enhanced proving experience, and proving ability with the introduction of user customizable and parametrizable tactic profiles.

  • Improved scalability and teamwork ability of the Rodin platform to support industrial deployments, through GUI refactoring and new features, Subversion model storage, decomposition, modularisation, flow support, as well as qualitative probabilistic reasoning and others,
  • Mathematical extensions are now supported in Rodin. The core of the Rodin platform has been modified and the Theory plug-in has been developed to allow the definition of new basic predicates, new operators and new algebraic types,
  • Prover performance has increased through the addition of a relevance filtering plug-in which raises the number of automatically discharged proof obligations. Moreover, work has been done to establish the soundness of provers and improve the generation of well-definedness proof obligations,
  • Model animation has been improved: it now supports multi-level animation and has been applied in WP1-4 deployment workpackages,
  • 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 more tightly integrated in Rodin, through new features implementation or state-machine animation,
  • Code generation, to enable complete support for development, from high-level Event-B models down to executable implementations. A 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.


References