Difference between pages "Code Generation Activity" and "Current Developments"

From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Andy
 
imported>Mathieu
 
Line 1: Line 1:
Tasking Event-B is the extension of Event-B for defining concurrent systems sharing data, for details see the [[Tasking Event-B Overview]] page. For more information contact Andy Edmunds - University of Southampton - mailto:ae2@ecs.soton.ac.uk
+
{{TOCright}}
=== Sensing and Actuating for Tasking Event-B ===
+
This page sum up the known developments that are being done around or for the [[Rodin Platform]]. ''Please contributes informations about your own development to keep the community informed''
Sensing and actuating events, and an Environ Machine have been added to allow simulation of the environment and implementation using memory mapped IO.
 
  
A new case study has been produced that makes use of these new features, details available at http://wiki.event-b.org/index.php/Event-B_Examples
+
== Deploy Tasks ==
 +
The following tasks were planned at some stage of the [[Deploy]] project.
 +
=== Core Platform ===
 +
==== New Mathematical Language ====
 +
==== Rodin Index Manager ====
 +
[[Systerel]] is in charge of this task.
 +
{{details|Rodin Index Design|Rodin index design}}
  
The example/tutorial projects and a Bundled Windows version is available in the [http://deploy-eprints.ecs.soton.ac.uk/304/ e-prints archive], or on [https://codegenerationd.svn.sourceforge.net/svnroot/codegenerationd/Examples/HeatingController_Tutorial_v0.1.4/ SVN].
+
The purpose of the Rodin index manager is to store in a uniform way the entities that are declared in the database together with their occurrences. This central repository of declarations and occurrences will allow for fast implementations of various refactoring mechanisms (such as renaming) and support for searching models or browsing them.  
Sources for the Code Generator are available from https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp/branches/CodeGeneration/0.1.4 SVN].
 
  
=== The Code Generation Demonstrator for Rodin 2.1.x ===
+
==== Text Editor ====
 +
[[Düsseldorf]] has a prototype text-based editor for Event-B (courtesy of [[User:Fabian|Fabian]]). As of end of sempteber 2008, it still needs more work to fully integrate into Rodin.
  
Released 24 January 2011.
+
[[Newcastle]] has another text editor based on EMF.  Among other things, it defines an EMF model of Event-B machines and contexts. At some point, the editor code is to be split into two plugins - an EMF adapater to rodin and the editor itself. Source code is currently available from [http://iliasov.org/editor-source.zip].
  
The Rodin 2.1.x compatible code generation demonstrator plug-ins have been released into the Rodin Sourceforge repository at:
+
=== Plug-ins ===
 +
==== Requirement Management Plug-in ====
 +
[[User:Jastram|Michael]] at [[Düsseldorf]] is in charge of the [[:Category:Requirement Plugin|Requirements Management Plug-in]].
  
  https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp/trunk/CodeGeneration
+
{{See also|ReqsManagement|Requirements Tutorial|l1=Requirements Management Plug-in}}
  
The update-site is available through the Rodin update site in the ''Utilities'' category.
+
This plug-in allows:
 +
* Requirements to be edited in a set of documents (independently from Rodin)
 +
* Requirements to be viewed within Rodin
 +
* Individual Requirements to be linked to individual Event-B-Entities
 +
* A basic completion test to be performed
  
The code generation tutorial examples are available for download at:
+
==== UML-B Plug-in ====
 +
[[Southampton]] is in charge of [[UML-B]] plug-in.
  
  https://sourceforge.net/projects/codegenerationd/files/DemoFiles/
+
* Support for synchronisation of transitions from different statemachines. This feature will allow two or more transitions in different statemachines to contribute to a single event. This feature is needed because a single event can alter several variables (in this case statemachines) simultaneously.
  
The code generation plug-in relies on the Epsilon tool suite. Install Epsilon manually, since the automatic install utility does not seem to work for this feature. We currently use the Epsilon interim update site available at:
+
*Allow user to allocate the name of the 'implicit contextual instance' used in a class. Events and Transitions owned by a class are implicitly acting upon an instance of the class which has formerly been denoted by the reserved word 'self'. This modification allows the modeller to override 'self' (which is now the default name) with any other identifier. This feature is needed to avoid name clashes when synchronising transitions into a single event. It also allows events to be moved between different classes (or outside of all classes) during refinement without creating name clashes.
  
  http://download.eclipse.org/modeling/gmt/epsilon/interim/
+
* Better support for state machine refinement in UML-B. This revision to UML-B allows a statemachine to be recognised as a refinement of another one and to be treated in an appropriate way during translation to Event-B. The states and transitions of a refined statemachine can be elaborated by adding more detailed hierarchical statemachines.
  
Select 'the Epsilon Core (Incubation)' component, this is the only component that is required for Tasking Event-B.
+
==== ProB Plug-in ====
 +
[[Düsseldorf]] is in charge of [[ProB]].
 +
<!-- {{details|ProB current developments|ProB current developments}} -->
  
== Code Generation Status ==
+
===== Work already performed =====
=== Latest Developments ===
 
* Demonstrator plug-in feature version 0.1.0
 
** for Rodin 2.1.x version is available.
 
  
* The Code Generation feature consists of,
+
We have now ported ProB to work directly on the Rodin AST. Animation is working and the user can now set a limited number of preferences.
** a tasking Development Generator.
+
The model checking feature is now also accessible.
** a tasking Development Editor (Based on an EMF Tree Editor).
+
It is also possible to create CSP and classical B specification files. These files can be edited with BE4 and animated/model checked with ProB.
** a translator, from Tasking Development to Common Language Model (IL1).
+
On the classical B side we have moved to a new, more robust parser (which is now capable of parsing some of the more complicated AtelierB
** a translator, from the Tasking Development to Event-B model of the implementation.
+
specifications from Siemens).
** a pretty-printer for the Tasking Development.
 
** a pretty-printer for Common Language Model, which generates Ada Source Code.
 
  
* A tutorial is available [[Code Generation Tutorial]]
+
On the developer side, we have moved to a continuous integration infrastructure using CruiseControl. Rodin is also building from CVS in that infrastructure.
** Step 1 - Create the tasking development.
 
** Step 2 - Add annotations.
 
** Step 3 - Invoke translators.
 
  
=== Ongoing Work ===
+
===== Ongoing and future developments=====
  
* Full Rodin Integration
+
We are currently developing a new, better user interface.
* Sensed Variables
+
We also plan to support multi-level animation with checking of the gluing invariant.
* Branching in Shared Machines
 
  
=== Future Work ===
+
We have prototypes for several extensions working, but they need to be fully tested and integrated into the plugin:
* Support for Interrupts.
+
* an inspector that allows the user to inspect complex predicates (such as invariants or guards) as well as expressions in a tree-like manner
* Richer DataTypes.
+
* a graphical animator based on SWT that allows the user to design his/her own animations easily within the tool
* Accommodation of duplicate event names in tasking developments.
+
* a 2D viewer to inspect the state space of the specification
  
== Metamodels ==
+
==== B2Latex Plug-in ====
* In the plug-in we define several meta-models:
+
[[Southampton]] is in charge of [[B2Latex]].
** CompositeControl: for the control flow (algorithmic) constructs such as branch, loop and sequence etc. These constructs may be used in the specification of either  sequential or concurrent systems.
 
** Tasking Meta-model: defines the tasking model where we attach tasking specific details, such as task priority, task type. The tasking structures provide the ability to define single tasking or multi-tasking (concurrent) systems. We make use of the composite control plug-in to specify the flow of control.
 
** Common Language (IL1) Meta-model: defines an abstraction of common programming language constructs for use in translations to implementations.
 
  
== Translation Rules ==
+
Kriangsak Damchoom will update the plug-in to add [[Event Extension|extensions of events]].
* Tasking to IL1/Event-B translation rules [[http://wiki.event-b.org/images/Translation.pdf]]
 
  
== Release History ==
+
==== Parallel Composition Plug-in ====
=== The Code Generation Demonstrator for Rodin 1.3.x ===
+
[[Southampton]] is in charge of the [[Parallel Composition using Event-B]] .
  
 +
The intention of the plug-in is to allow the parallel composition of events using Event-B syntax. The composition uses a value-passing style (shared event composition), where parameters can be shared/merged.
  
First release: 30 November 2010.
+
This plug-in allows:
 +
* Selection of machines that will be part of the composition (''Includes'' Section)
 +
* Possible selection of an abstract machine (''Refines'' Section)
 +
* Possible inclusion of invariants that relate the included machines (''Invariant'' Section and use of the monotonicity )
 +
* Invariants of included machines are conjoined.
 +
* Selection of events that will be merged. The event(s) must come from different machines. At the moment, events with parameters with same name are merged. If it is a refinement composition, it is possible to choose the abstract event that is being refined.
 +
* Initialisation event is the parallel composition of all the included machines' initialisations.
 +
* For a composed event, the guards are conjoined and the all the actions are composed in parallel.
  
available from:
+
Currently, after the conclusion of the composition machine, a new machine can be generated, resulting from the properties defined on the composition file. This allows proofs to be generated as well as a visualisation of the composition machine file. In the future, the intention is to make the validation directly on the composition machine file directly where proofs would be generated ( and discharged) - the new machine generation would be optional. An event-b model for the validation/generation of proofs in currently being developed. Another functionality which should be quite useful for the composition (but not restricted to that) is '''renaming''':
  
https://sourceforge.net/projects/codegenerationd/files/
+
* while composing, two machines may have variables with the same name for instance (which is not allowed for this type of composition). In order to solve this problem, one would have to rename one of the variables in order to avoid the clash, which would mean change the original machine. A possible solution for that would be to rename the variable but just on composition machine file, keeping the original machine intact. A renaming framework designed and developed by Stefan Hallerstede and Sonja Holl exists currently although still on a testing phase. The framework was developed to be used in a general fashion (not constrained to event-b syntax). The idea is to extend the development of this framework and apply to Event-B syntax (current development).
  
The zip file contains a windows XP bundle, and a Windows V7 bundle. Alternatively, if you wish to build using an update-site, this is also included in the zip file, along with some notes on installation. However, note that the demonstrator tool is only compatible with Rodin 1.3.  
+
There is a prototype for the composition plug-in available, but only works for Rodin 0.8.2. A release for the Rodin 0.9 should be made available soon.
  
A simple shared buffer example is provided. This will form the basis of a tutorial (which is work in progress). The WindowsBundles directory contains a Rodin 1.3.1 platform with the Code Generation plug-ins, together with a patch plug-in. The patch plug-in is required to correct an inconsistency in the org.eventb.emf.persistence plug-in. For the bundles, simply extract the appropriate zip file into a directory and run the rodin.exe. The plug-ins are pre-installed - the only configuration necessary may be to switch workspace to ''<installPath>\rodin1.3bWin7\workspace''. When using the update-site the example projects, and the project forming the basis of a simple tutorial, are provided in the accompanying zip file. These should be imported manually.
+
==== Refactoring Framework Plug-in ====
 +
[[Southampton]] is in charge of the [[Refactoring Framework]].
  
Mac users - no bundled version available at present, but use the update site in the 'advanced' folder.  
+
The intention of the plug-in is to allow the renaming/refactoring of elements on a file (and possible related files). Although created to be used in a general way, the idea is to embed this framework on the Rodin platform, using Event-B syntax. This plug-in was initially designed and developed by Stefan Hallerstede and Sonja Holl.
  
'''A step-by-step [[Code Generation Tutorial]] is available'''
+
This plug-in allows:
 +
* Defining extensions that can be used to select related files.
 +
* Defining extensions that can be used to rename elements based on the type of file.
 +
* Renaming of elements on a file and possible occurrences on related files.
 +
* Generating of a report of possible problems (clashes) that can occur while renaming.
  
==== About the Initial Release ====
+
== Exploratory Tasks ==
The Code Generation (CG) Feature in the initial release is a demonstration tool; a proof of concept, rather than a prototype. The tool has no static checker and, therefore, there will be a heavy reliance on docs and dialogue to facilitate exploration of the tools and concepts.
+
=== One Single View ===
 +
[[Maria]] is in charge of this exploratory work during is internship.
 +
{{details|Single View Design|Single View Design}}
 +
The goal of this project is to present everything in a single view in Rodin. So the user won't have to switch perspectives.
  
==== Source Code ====
 
  
The sources are available from,
 
  
https://codegenerationd.svn.sourceforge.net/svnroot/codegenerationd
+
== Others ==
 
 
Note - I used Eclipse 3.5 Galileo, and you will need to install (or have sources from) Epsilon's interim update site. There is also dependency on Camille v2.0.0
 
  
 +
=== AnimB ===
 +
[[Christophe]] devotes some of its spare time for this plug-in.
 +
{{details|AnimB Current Developments|AnimB Current Developments}}
 +
The current developments around the [[AnimB]] plug-in encompass the following topics:
 +
;Live animation update
 +
:where the modification of the animated event-B model is instantaneously taken into account by the animator, without the need to restart the animation.
 +
;Collecting history
 +
:The history of the animation will be collected.
  
 +
=== Team-Based Development ===
  
 +
; Usage Scenarios
 +
: In order to understand the problem properly, [http://www.stups.uni-duesseldorf.de/ Düsseldorf] created a number of usage [[Scenarios for Team-based Development]].
 +
: A page as also been opened for [[Scenarios for Merging Proofs|merging proofs scenarios]].
 
[[Category:Work in progress]]
 
[[Category:Work in progress]]

Revision as of 20:21, 11 November 2008

This page sum up the known developments that are being done around or for the Rodin Platform. Please contributes informations about your own development to keep the community informed

Deploy Tasks

The following tasks were planned at some stage of the Deploy project.

Core Platform

New Mathematical Language

Rodin Index Manager

Systerel is in charge of this task.

For more details on Rodin index design, see Rodin Index Design.

The purpose of the Rodin index manager is to store in a uniform way the entities that are declared in the database together with their occurrences. This central repository of declarations and occurrences will allow for fast implementations of various refactoring mechanisms (such as renaming) and support for searching models or browsing them.

Text Editor

Düsseldorf has a prototype text-based editor for Event-B (courtesy of Fabian). As of end of sempteber 2008, it still needs more work to fully integrate into Rodin.

Newcastle has another text editor based on EMF. Among other things, it defines an EMF model of Event-B machines and contexts. At some point, the editor code is to be split into two plugins - an EMF adapater to rodin and the editor itself. Source code is currently available from [1].

Plug-ins

Requirement Management Plug-in

Michael at Düsseldorf is in charge of the Requirements Management Plug-in.

See also: Requirements Management Plug-in and Requirements Tutorial

This plug-in allows:

  • Requirements to be edited in a set of documents (independently from Rodin)
  • Requirements to be viewed within Rodin
  • Individual Requirements to be linked to individual Event-B-Entities
  • A basic completion test to be performed

UML-B Plug-in

Southampton is in charge of UML-B plug-in.

  • Support for synchronisation of transitions from different statemachines. This feature will allow two or more transitions in different statemachines to contribute to a single event. This feature is needed because a single event can alter several variables (in this case statemachines) simultaneously.
  • Allow user to allocate the name of the 'implicit contextual instance' used in a class. Events and Transitions owned by a class are implicitly acting upon an instance of the class which has formerly been denoted by the reserved word 'self'. This modification allows the modeller to override 'self' (which is now the default name) with any other identifier. This feature is needed to avoid name clashes when synchronising transitions into a single event. It also allows events to be moved between different classes (or outside of all classes) during refinement without creating name clashes.
  • Better support for state machine refinement in UML-B. This revision to UML-B allows a statemachine to be recognised as a refinement of another one and to be treated in an appropriate way during translation to Event-B. The states and transitions of a refined statemachine can be elaborated by adding more detailed hierarchical statemachines.

ProB Plug-in

Düsseldorf is in charge of ProB.

Work already performed

We have now ported ProB to work directly on the Rodin AST. Animation is working and the user can now set a limited number of preferences. The model checking feature is now also accessible. It is also possible to create CSP and classical B specification files. These files can be edited with BE4 and animated/model checked with ProB. On the classical B side we have moved to a new, more robust parser (which is now capable of parsing some of the more complicated AtelierB specifications from Siemens).

On the developer side, we have moved to a continuous integration infrastructure using CruiseControl. Rodin is also building from CVS in that infrastructure.

Ongoing and future developments

We are currently developing a new, better user interface. We also plan to support multi-level animation with checking of the gluing invariant.

We have prototypes for several extensions working, but they need to be fully tested and integrated into the plugin:

  • an inspector that allows the user to inspect complex predicates (such as invariants or guards) as well as expressions in a tree-like manner
  • a graphical animator based on SWT that allows the user to design his/her own animations easily within the tool
  • a 2D viewer to inspect the state space of the specification

B2Latex Plug-in

Southampton is in charge of B2Latex.

Kriangsak Damchoom will update the plug-in to add extensions of events.

Parallel Composition Plug-in

Southampton is in charge of the Parallel Composition using Event-B .

The intention of the plug-in is to allow the parallel composition of events using Event-B syntax. The composition uses a value-passing style (shared event composition), where parameters can be shared/merged.

This plug-in allows:

  • Selection of machines that will be part of the composition (Includes Section)
  • Possible selection of an abstract machine (Refines Section)
  • Possible inclusion of invariants that relate the included machines (Invariant Section and use of the monotonicity )
  • Invariants of included machines are conjoined.
  • Selection of events that will be merged. The event(s) must come from different machines. At the moment, events with parameters with same name are merged. If it is a refinement composition, it is possible to choose the abstract event that is being refined.
  • Initialisation event is the parallel composition of all the included machines' initialisations.
  • For a composed event, the guards are conjoined and the all the actions are composed in parallel.

Currently, after the conclusion of the composition machine, a new machine can be generated, resulting from the properties defined on the composition file. This allows proofs to be generated as well as a visualisation of the composition machine file. In the future, the intention is to make the validation directly on the composition machine file directly where proofs would be generated ( and discharged) - the new machine generation would be optional. An event-b model for the validation/generation of proofs in currently being developed. Another functionality which should be quite useful for the composition (but not restricted to that) is renaming:

  • while composing, two machines may have variables with the same name for instance (which is not allowed for this type of composition). In order to solve this problem, one would have to rename one of the variables in order to avoid the clash, which would mean change the original machine. A possible solution for that would be to rename the variable but just on composition machine file, keeping the original machine intact. A renaming framework designed and developed by Stefan Hallerstede and Sonja Holl exists currently although still on a testing phase. The framework was developed to be used in a general fashion (not constrained to event-b syntax). The idea is to extend the development of this framework and apply to Event-B syntax (current development).

There is a prototype for the composition plug-in available, but only works for Rodin 0.8.2. A release for the Rodin 0.9 should be made available soon.

Refactoring Framework Plug-in

Southampton is in charge of the Refactoring Framework.

The intention of the plug-in is to allow the renaming/refactoring of elements on a file (and possible related files). Although created to be used in a general way, the idea is to embed this framework on the Rodin platform, using Event-B syntax. This plug-in was initially designed and developed by Stefan Hallerstede and Sonja Holl.

This plug-in allows:

  • Defining extensions that can be used to select related files.
  • Defining extensions that can be used to rename elements based on the type of file.
  • Renaming of elements on a file and possible occurrences on related files.
  • Generating of a report of possible problems (clashes) that can occur while renaming.

Exploratory Tasks

One Single View

Maria is in charge of this exploratory work during is internship.

For more details on Single View Design, see Single View Design.

The goal of this project is to present everything in a single view in Rodin. So the user won't have to switch perspectives.


Others

AnimB

Christophe devotes some of its spare time for this plug-in.

For more details on AnimB Current Developments, see AnimB Current Developments.

The current developments around the AnimB plug-in encompass the following topics:

Live animation update
where the modification of the animated event-B model is instantaneously taken into account by the animator, without the need to restart the animation.
Collecting history
The history of the animation will be collected.

Team-Based Development

Usage Scenarios
In order to understand the problem properly, Düsseldorf created a number of usage Scenarios for Team-based Development.
A page as also been opened for merging proofs scenarios.