Difference between pages "ADVANCE D3.2 General Platform Maintenance" and "Code Generation Activity"

From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Ladenberger
 
imported>Andy
 
Line 1: Line 1:
== Core Rodin platform (Thomas Muller) ==
+
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
 +
=== Code Generation Feature - Version 0.2.0 ===
 +
This section is undergoing maintenance. We are planning to release a new version of the code generator in the next few days.
 +
The main changes are:
 +
* The new code generators have been completely re-written. The translators are now implemented in Java, i.e. there is no longer a dependence on the Epsilon tool set. This was undertaken for code maintenance reasons.
 +
* Tasking Event-B is now integrated with the Event-B explorer.
 +
* The Rose Editor is used for editing the Tasking Event-B, and
 +
* a TaskBody text-based editor is provided, in Rose, for specifying the flow control. This feature has been added to address some of the usability issues.
 +
* The EMF tree editor in Rose is only used minimally, and we plan further enhancements to reduce this.
 +
* Composed machines are used to store event 'synchronizations'. This reduces the amount of typing in the TaskBody editor, since we no longer need to specify both local and remote (synchronizing) events.
 +
* The code generation approach is now extensible; new target language constructs can be added using the Eclipse extension mechanism.
 +
* The translation, of the mathematical language of target languages, is specified in the Theory plug-in.
 +
* Translated code is deposited in a directory in the appropriate files. An Ada project file is generated for use with AdaCore's GPS workbench. Eventually this could be enabled/disabled in a preferences dialog box.
  
=== Overview ===
+
=== Sensing and Actuating for Tasking Event-B ===
{{TODO|Fill this paragraph.}}
+
Version 0.1.5. Sensing and actuating events, and an Environ Machine have been added to allow simulation of the environment and implementation using memory mapped IO.
  
=== Motivations / Decisions ===
+
* The new v0.1.5 feature is available from the Rodin Update Site, it resides in the Utilities Category.
{{TODO|Fill this paragraph.}}
 
  
=== Available Documentation ===
+
* As in previous releases, the code generation plug-in relies on the Epsilon tool suite. Add the following Epsilon interim update site to the list of available update sites in the Eclipse menu ''help/install new software'': http://download.eclipse.org/modeling/gmt/epsilon/interim/
{{TODO|Fill this paragraph.}}
 
  
=== Planning ===
+
* Select 'the Epsilon Core (Incubation)' component, this is the only component that is required for Tasking Event-B.
{{TODO|Fill this paragraph.}}
 
  
 +
A new [http://wiki.event-b.org/index.php?title=Tasking_Event-B_Tutorial Code Generation Tutorial] has been produced, that makes use of these new features. There is an explanation of the heating controller, upon which it is based, [http://wiki.event-b.org/index.php/Development_of_a_Heating_Controller_System here].
  
 +
The example/tutorial projects, and also and a Bundled Windows 7 version, are available in the [http://deploy-eprints.ecs.soton.ac.uk/304/ Deploy E-Prints archive] or [https://codegenerationd.svn.sourceforge.net/svnroot/codegenerationd/Examples/HeatingController_Tutorial_v0.1.4/ Examples SVN site].
  
== UML-B Improvements (Colin Snook, Vitaly Savicks) ==
+
=== The Code Generation Demonstrator for Rodin 2.1.x ===
  
=== Overview ===
+
Released 24 January 2011.
{{TODO|Fill this paragraph.}}
 
  
=== Motivations / Decisions ===
+
The Rodin 2.1.x compatible code generation demonstrator plug-ins have been released into the Rodin Sourceforge repository at:
{{TODO|Fill this paragraph.}}
 
  
=== Available Documentation ===
+
  https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp/trunk/CodeGeneration
{{TODO|Fill this paragraph.}}
 
  
=== Planning ===
+
The update-site is available through the Rodin update site in the ''Utilities'' category.
{{TODO|Fill this paragraph.}}
 
  
== Code generation (Andy Edmunds) ==
+
The code generation tutorial examples are available for download at:
  
=== Overview ===
+
  https://sourceforge.net/projects/codegenerationd/files/DemoFiles/
{{TODO|Fill this paragraph.}}
 
  
=== Motivations / Decisions ===
+
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:
{{TODO|Fill this paragraph.}}
 
  
=== Available Documentation ===
+
  http://download.eclipse.org/modeling/gmt/epsilon/interim/
{{TODO|Fill this paragraph.}}
 
  
=== Planning ===
+
Select 'the Epsilon Core (Incubation)' component, this is the only component that is required for Tasking Event-B.
{{TODO|Fill this paragraph.}}
 
  
 +
== Code Generation Status ==
 +
=== Latest Developments ===
 +
* Demonstrator plug-in feature version 0.1.0
 +
** for Rodin 2.1.x version is available.
  
 +
* The Code Generation feature consists of,
 +
** a tasking Development Generator.
 +
** a tasking Development Editor (Based on an EMF Tree Editor).
 +
** a translator, from Tasking Development to Common Language Model (IL1).
 +
** a translator, from the Tasking Development to Event-B model of the implementation.
 +
** a pretty-printer for the Tasking Development.
 +
** a pretty-printer for Common Language Model, which generates Ada Source Code.
  
== ProR (Michael Jastram/Lukas Ladenberger) ==
+
* A tutorial is available [[Code Generation Tutorial]]
 +
** Step 1 - Create the tasking development.
 +
** Step 2 - Add annotations.
 +
** Step 3 - Invoke translators.
  
=== Overview ===
+
=== Ongoing Work ===
  
{{TODO|Fill this paragraph.}}
+
* Full Rodin Integration
 +
* Sensed Variables
 +
* Branching in Shared Machines
  
* A Method for Tracing Requirements into Specifications
+
=== Future Work ===
* ProR/Rodin Integration plugin
+
* Support for Interrupts.
 +
* Richer DataTypes.
 +
* Accommodation of duplicate event names in tasking developments.
  
=== Motivations / Decisions ===
+
== Metamodels ==
 +
* In the plug-in we define several meta-models:
 +
** 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.
  
{{TODO|Fill this paragraph.}}
+
== Translation Rules ==
 +
* Tasking to IL1/Event-B translation rules [[http://wiki.event-b.org/images/Translation.pdf]]
  
The motivation of the Rodin/ProR integration plugin was to bring two complimentary fields of research, requirements engineering and formal modelling, closer together. Especially, the traceability within a system description is a challenging problem of requirements engineering. In particular, formal models of the system are often based on informal requirements, but creating and maintaining the traceability between the two can be challenging. In <ref name="req1ref">http://www.stups.uni-duesseldorf.de/w/Special:Publication/HalJasLad2012</ref>, we presented an incremental approach for producing a system description from an initial set of requirements. The foundation of the approach is a classification of requirements into artefacts W (domain properties), R (requirements) and S (specification). In addition, the approach uses designated phenomena as the vocabulary employed by the artefacts. The central idea is that adequacy of the system description must be justified, meaning that W ∧ S ⇒ R. The approach establishes a traceability, and the resulting system description may consist of formal and informal artefacts. We created tool support for this approach by integrating Rodin and ProR. We designed it with the goal to support the approach described in <ref name="req1ref"/>, and to ease the integration of natural language requirements and Event-B.
+
== Release History ==
 +
=== The Code Generation Demonstrator for Rodin 1.3.x ===
  
=== Available Documentation ===
 
  
{{TODO|Fill this paragraph.}}
+
First release: 30 November 2010.
  
* A Method and Tool for Tracing Requirements into Specifications: <ref name="req1ref"/> The paper has been submitted to Science of Computer Programming.
+
available from:
* Requirements Traceability between Textual Requirements and Formal Models Using ProR: <ref>http://www.stups.uni-duesseldorf.de/w/Special:Publication/LadenbergerJastram_iFMABZ2012</ref> The paper has been accepted for iFM'2012.
 
  
* Tutorial for the Rodin/ProR integration can be found here: <ref>http://wiki.event-b.org/index.php/ProR</ref>.
+
https://sourceforge.net/projects/codegenerationd/files/
* The User Guide containing an additional Tutorial for ProR can be found here: <ref>http://wiki.eclipse.org/RMF/User_Guide</ref>.
 
  
=== Planning ===
+
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.
  
{{TODO|Fill this paragraph.}}
+
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.
  
There are still some limitations on the ProR/Rodin integration plugin, however. While all required data structures exist, the plugin would benefit from more sophisticated reporting. In particular, <ref name="req1ref"/> lists a number of properties of a correct system description. While the presence of these properties does not guarantee correctness, their absence indicates a problem. Reporting on the state of these properties would be valuable.  
+
Mac users - no bundled version available at present, but use the update site in the 'advanced' folder.  
  
Furthermore, the plugin does not support classifying phenomena. In a next step we will work on a concept for classifying and maintaining phenomena with ProR.
+
'''A step-by-step [[Code Generation Tutorial]] is available'''
  
== References ==
+
==== About the Initial Release ====
<references/>
+
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.
  
== Camille (Ingo Weigelt) ==
+
==== Source Code ====
  
=== Overview ===
+
The sources are available from,
{{TODO|Fill this paragraph.}}
 
  
=== Motivations / Decisions ===
+
https://codegenerationd.svn.sourceforge.net/svnroot/codegenerationd
{{TODO|Fill this paragraph.}}
 
  
=== Available Documentation ===
+
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
{{TODO|Fill this paragraph.}}
 
  
=== Planning ===
 
{{TODO|Fill this paragraph.}}
 
  
== References ==
 
<references/>
 
  
[[Category:ADVANCE D3.2 Deliverable]]
+
[[Category:Work in progress]]

Revision as of 15:51, 24 November 2011

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

Code Generation Feature - Version 0.2.0

This section is undergoing maintenance. We are planning to release a new version of the code generator in the next few days. The main changes are:

  • The new code generators have been completely re-written. The translators are now implemented in Java, i.e. there is no longer a dependence on the Epsilon tool set. This was undertaken for code maintenance reasons.
  • Tasking Event-B is now integrated with the Event-B explorer.
  • The Rose Editor is used for editing the Tasking Event-B, and
  • a TaskBody text-based editor is provided, in Rose, for specifying the flow control. This feature has been added to address some of the usability issues.
  • The EMF tree editor in Rose is only used minimally, and we plan further enhancements to reduce this.
  • Composed machines are used to store event 'synchronizations'. This reduces the amount of typing in the TaskBody editor, since we no longer need to specify both local and remote (synchronizing) events.
  • The code generation approach is now extensible; new target language constructs can be added using the Eclipse extension mechanism.
  • The translation, of the mathematical language of target languages, is specified in the Theory plug-in.
  • Translated code is deposited in a directory in the appropriate files. An Ada project file is generated for use with AdaCore's GPS workbench. Eventually this could be enabled/disabled in a preferences dialog box.

Sensing and Actuating for Tasking Event-B

Version 0.1.5. Sensing and actuating events, and an Environ Machine have been added to allow simulation of the environment and implementation using memory mapped IO.

  • The new v0.1.5 feature is available from the Rodin Update Site, it resides in the Utilities Category.
  • Select 'the Epsilon Core (Incubation)' component, this is the only component that is required for Tasking Event-B.

A new Code Generation Tutorial has been produced, that makes use of these new features. There is an explanation of the heating controller, upon which it is based, here.

The example/tutorial projects, and also and a Bundled Windows 7 version, are available in the Deploy E-Prints archive or Examples SVN site.

The Code Generation Demonstrator for Rodin 2.1.x

Released 24 January 2011.

The Rodin 2.1.x compatible code generation demonstrator plug-ins have been released into the Rodin Sourceforge repository at:

 https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp/trunk/CodeGeneration 

The update-site is available through the Rodin update site in the Utilities category.

The code generation tutorial examples are available for download at:

 https://sourceforge.net/projects/codegenerationd/files/DemoFiles/

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:

 http://download.eclipse.org/modeling/gmt/epsilon/interim/

Select 'the Epsilon Core (Incubation)' component, this is the only component that is required for Tasking Event-B.

Code Generation Status

Latest Developments

  • Demonstrator plug-in feature version 0.1.0
    • for Rodin 2.1.x version is available.
  • The Code Generation feature consists of,
    • a tasking Development Generator.
    • a tasking Development Editor (Based on an EMF Tree Editor).
    • a translator, from Tasking Development to Common Language Model (IL1).
    • a translator, from the Tasking Development to Event-B model of the implementation.
    • 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
    • Step 1 - Create the tasking development.
    • Step 2 - Add annotations.
    • Step 3 - Invoke translators.

Ongoing Work

  • Full Rodin Integration
  • Sensed Variables
  • Branching in Shared Machines

Future Work

  • Support for Interrupts.
  • Richer DataTypes.
  • Accommodation of duplicate event names in tasking developments.

Metamodels

  • In the plug-in we define several meta-models:
    • 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

  • Tasking to IL1/Event-B translation rules [[1]]

Release History

The Code Generation Demonstrator for Rodin 1.3.x

First release: 30 November 2010.

available from:

https://sourceforge.net/projects/codegenerationd/files/

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.

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.

Mac users - no bundled version available at present, but use the update site in the 'advanced' folder.

A step-by-step Code Generation Tutorial is available

About the Initial Release

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.

Source Code

The sources are available from,

https://codegenerationd.svn.sourceforge.net/svnroot/codegenerationd

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