Event-B - User contributions [en-gb]

UML-B

2020-09-30T22:12:32Z

Colin: /* Tutorials */ remove i

Return to [[Rodin Plug-ins]]

UML-B provides a 'UML-like' graphical front end for Event-B. It provides various diagrammatic modelling notations and editors for creating models which are then translated into Event-B for verification. [[UML-B]] works alongside Event-B allowing the modeller to model in normal Event-B but also contribute some aspects of the model via diagrams.

Our [https://www.uml-b.org UML-B] website contains more information about installing UML-B and getting started, as well as our current research and collaborations.

UML-B is a collection of diagrammatic editors for Event-B. The diagrams are used to elaborate the machine and its content with extra model features. The diagrams may either by contained within the machine they contribute to, or can be contained in a separate UML-B model file that is linked to the machine.

* [[Image:IUMLB.png]] [[Event-B Statemachines| State-machine diagrams]] a hierarchical state-machine diagram editor which can be used to impose sequential ordering to your events. An animator is also provided to visualise the progress of the state-machine.

* [[Image:IUMLB.png]] [[Event-B Classdiagrams| Class diagrams]] a class diagram editor which can be used to define data entities and their relationships and to lift behaviour based on data sets.

==Lectures==

* [[Media:iUML-BClassDiagramsLecture.pdf | UML-B Class-diagrams Lecture]] : Lecture slides on the use of UML-B Class-diagrams

* [[Media:iUML-BStatemachinesLecture.pdf | UML-B State-machines Lecture]] : Lecture slides on the use of UML-B State-machines.

==Tutorials==

* [[iUML-B Class-diagrams Tutorial | UML-B Class-diagrams Tutorial]] : A tutorial on the use of UML-B Class-diagrams.

* [[iUML-B State-machines Tutorial | UML-B State-machines Tutorial]] : A tutorial on the use of UML-B State-machines.

==Guidelines==

* [[UML-B - Modelling a control system]] : Some guidelines on modelling styles for a control system

[[Category:User documentation]]
[[Category:UML-B]]
[[Category:Plugin]]

UML-B - Modelling a control system

2020-09-30T22:10:03Z

Colin: renamed to remove i

This page is under development. Later it will be compiled into an illustrated guide using a running example developed in UML-B.

This page gives some guidelines for developing a control system using iUML-B. We aim to verify (i.e. prove) some safety properties of the system comprising the controller and the environment that it is controlling. We also aim to use visual animations of the system to validate with stakeholders the controller and the assumptions we make about the environment.

1. In order to prove system wide properties we need to model the system, not just the controller.

2. In order to run animations we need to model both the controller and the environment.

3. However, the environment model contains assumptions about the possible behaviours of the environment. We also need to test the behaviour of the controller for less well-behaved inputs.

4. Our first abstract models will be small abstract statemachines just enough to capture the most important safety properties of the system.

5. The initial refinements introduce the distinction between the controller and physical components of the environment in order to verify that their interaction maintains the safety of the abstract model.

6. At these early stages the interaction is modelled by direct access to the states of the other components (e.g. in transition guards).

7. We aim to build up the controller model via hierarchical nesting as far as possible. Ideally there should only be one statemachine representing the controller.

8. We build up the environment model with many state-machines, generally one per physical component in the environment.

9. We gradually replace the unrealistic direct access between controller and physical components with the actual I/O interface of the controller.

10. We model the I/O interface either as variables (of type BOOL, NAT, enumerated set) directly in the machine, or

11. where there are multiple instances of similar I/O channels, as iUML-B Classes with attributes (of type BOOL, NAT, enumerated set).

12. While developing refinements (in order to discharge proof obligations) we add invariants to states about a) states of other components and b) the value of outputs.

13. As the model is developed, we add invariants to the machine to give the equivalence between controller states and controller outputs.

14. We build different versions of environment models a) liberal models that can behave in unexpected ways to test the controllers response to fault scenarios, b) well-behaved models to test the controllers response to normal situations.

15. Note that well-behaved models of the environment (i.e. 14 b) document assumptions about the environment that we rely on for succesful control.

UML-B

2020-09-30T22:09:33Z

Colin: /* Guidelines */

Return to [[Rodin Plug-ins]]

UML-B provides a 'UML-like' graphical front end for Event-B. It provides various diagrammatic modelling notations and editors for creating models which are then translated into Event-B for verification. [[UML-B]] works alongside Event-B allowing the modeller to model in normal Event-B but also contribute some aspects of the model via diagrams.

Our [https://www.uml-b.org UML-B] website contains more information about installing UML-B and getting started, as well as our current research and collaborations.

UML-B is a collection of diagrammatic editors for Event-B. The diagrams are used to elaborate the machine and its content with extra model features. The diagrams may either by contained within the machine they contribute to, or can be contained in a separate UML-B model file that is linked to the machine.

* [[Image:IUMLB.png]] [[Event-B Statemachines| State-machine diagrams]] a hierarchical state-machine diagram editor which can be used to impose sequential ordering to your events. An animator is also provided to visualise the progress of the state-machine.

* [[Image:IUMLB.png]] [[Event-B Classdiagrams| Class diagrams]] a class diagram editor which can be used to define data entities and their relationships and to lift behaviour based on data sets.

==Lectures==

* [[Media:iUML-BClassDiagramsLecture.pdf | UML-B Class-diagrams Lecture]] : Lecture slides on the use of UML-B Class-diagrams

* [[Media:iUML-BStatemachinesLecture.pdf | UML-B State-machines Lecture]] : Lecture slides on the use of UML-B State-machines.

==Tutorials==

* [[iUML-B Class-diagrams Tutorial]] : A tutorial on the use of UML-B Class-diagrams.

* [[iUML-B State-machines Tutorial]] : A tutorial on the use of UML-B State-machines.

==Guidelines==

* [[UML-B - Modelling a control system]] : Some guidelines on modelling styles for a control system

[[Category:User documentation]]
[[Category:UML-B]]
[[Category:Plugin]]

IUML-B Modelling a control system

2020-09-30T22:08:33Z

Colin: remove i

Template:News

2020-09-30T22:03:33Z

Colin: add UML-B website

<noinclude>
[http://wiki.event-b.org/index.php?title=Template:News/Archives&action=edit Edit Archives]
== Displayed as follow on the Main Page ==
<div style="margin:0;width:43%;border:1px solid #AAAAAA;background:#FFFFFF">
</noinclude>
* 30/09/20: New [https://www.uml-b.org UML-B] website - getting started with UML-B - current research and collaborations
* 31/05/13: New [http://www.youtube.com/watch?v=fSWZWXx5ixc Event-B video] on the Event-B & Rodin youtube channel
* 28/03/13: New [https://www.youtube.com/EventBtv UML-B video] on the Event-B & Rodin youtube channel
<noinclude>
</div>
[[Category:Main page templates]]
</noinclude>

UML-B

2020-09-30T21:56:45Z

Colin:

Return to [[Rodin Plug-ins]]

UML-B provides a 'UML-like' graphical front end for Event-B. It provides various diagrammatic modelling notations and editors for creating models which are then translated into Event-B for verification. [[UML-B]] works alongside Event-B allowing the modeller to model in normal Event-B but also contribute some aspects of the model via diagrams.

Our [https://www.uml-b.org UML-B] website contains more information about installing UML-B and getting started, as well as our current research and collaborations.

UML-B is a collection of diagrammatic editors for Event-B. The diagrams are used to elaborate the machine and its content with extra model features. The diagrams may either by contained within the machine they contribute to, or can be contained in a separate UML-B model file that is linked to the machine.

* [[Image:IUMLB.png]] [[Event-B Statemachines| State-machine diagrams]] a hierarchical state-machine diagram editor which can be used to impose sequential ordering to your events. An animator is also provided to visualise the progress of the state-machine.

* [[Image:IUMLB.png]] [[Event-B Classdiagrams| Class diagrams]] a class diagram editor which can be used to define data entities and their relationships and to lift behaviour based on data sets.

==Lectures==

* [[Media:iUML-BClassDiagramsLecture.pdf | UML-B Class-diagrams Lecture]] : Lecture slides on the use of UML-B Class-diagrams

* [[Media:iUML-BStatemachinesLecture.pdf | UML-B State-machines Lecture]] : Lecture slides on the use of UML-B State-machines.

==Tutorials==

* [[iUML-B Class-diagrams Tutorial]] : A tutorial on the use of UML-B Class-diagrams.

* [[iUML-B State-machines Tutorial]] : A tutorial on the use of UML-B State-machines.

==Guidelines==

* [[iUML-B Modelling a control system]] : Some guidelines on modelling styles for a control system

[[Category:User documentation]]
[[Category:UML-B]]
[[Category:Plugin]]

UML-B

2020-09-30T21:55:42Z

Colin: remove some i

Return to [[Rodin Plug-ins]]

UML-B provides a 'UML-like' graphical front end for Event-B. It provides various diagrammatic modelling notations and editors for creating models which are then translated into Event-B for verification. [[UML-B]] works alongside Event-B allowing the modeller to model in normal Event-B but also contribute some aspects of the model via diagrams.

Our [https://www.uml-b.org UML-B] website contains more information about installing UML-B and getting started, as well as our current research and collaborations.

UML-B is a collection of diagrammatic editors for Event-B. The diagrams are used to elaborate the machine and its content with extra model features. The diagrams may either by contained within the machine they contribute to, or can be contained in a separate UML-B model file that is linked to the machine.

* [[Image:IUMLB.png]] [[Event-B Statemachines| State-machine diagrams]] a hierarchical state-machine diagram editor which can be used to impose sequential ordering to your events. An animator is also provided to visualise the progress of the state-machine.

* [[Image:IUMLB.png]] [[Event-B Classdiagrams| Class diagrams]] a class diagram editor which can be used to define data entities and their relationships and to lift behaviour based on data sets.

==Lectures==

* [[Media:iUML-BClassDiagramsLecture.pdf | UML-B Class-diagrams Lecture]] : Lecture slides on the use of UML-B Class-diagrams

* [[Media:iUML-BStatemachinesLecture.pdf | UML-B State-machines Lecture]] : Lecture slides on the use of UML-B State-machines.

==Tutorials==

* [[iUML-B Class-diagrams Tutorial]] : A tutorial on the use of iUML-B Class-diagrams.

* [[iUML-B State-machines Tutorial]] : A tutorial on the use of iUML-B State-machines.

==Guidelines==

* [[iUML-B Modelling a control system]] : Some guidelines on modelling styles for a control system

[[Category:User documentation]]
[[Category:UML-B]]
[[Category:Plugin]]

UML-B

2020-09-30T21:53:34Z

Colin: move content of iUML-B page to this one

Return to [[Rodin Plug-ins]]

UML-B provides a 'UML-like' graphical front end for Event-B. It provides various diagrammatic modelling notations and editors for creating models which are then translated into Event-B for verification. [[UML-B]] works alongside Event-B allowing the modeller to model in normal Event-B but also contribute some aspects of the model via diagrams.

Our [https://www.uml-b.org UML-B] website contains more information about installing UML-B and getting started, as well as our current research and collaborations.

UML-B is a collection of diagrammatic editors for Event-B. The diagrams are used to elaborate the machine and its content with extra model features. The diagrams may either by contained within the machine they contribute to, or can be contained in a separate UML-B model file that is linked to the machine.

* [[Image:IUMLB.png]] [[Event-B Statemachines| State-machine diagrams]] a hierarchical state-machine diagram editor which can be used to impose sequential ordering to your events. An animator is also provided to visualise the progress of the state-machine.

* [[Image:IUMLB.png]] [[Event-B Classdiagrams| Class diagrams]] a class diagram editor which can be used to define data entities and their relationships and to lift behaviour based on data sets.

==Lectures==

* [[Media:iUML-BClassDiagramsLecture.pdf | iUML-B Class-diagrams Lecture]] : Lecture slides on the use of iUML-B Class-diagrams

* [[Media:iUML-BStatemachinesLecture.pdf | iUML-B State-machines Lecture]] : Lecture slides on the use of iUML-B State-machines.

==Tutorials==

* [[iUML-B Class-diagrams Tutorial]] : A tutorial on the use of iUML-B Class-diagrams.

* [[iUML-B State-machines Tutorial]] : A tutorial on the use of iUML-B State-machines.

==Guidelines==

* [[iUML-B Modelling a control system]] : Some guidelines on modelling styles for a control system

[[Category:User documentation]]
[[Category:UML-B]]
[[Category:Plugin]]

UML-B

2020-09-30T21:46:27Z

Colin: revised to remove old UML-B and link to new website

Rodin Platform 3.5.0 External Plug-ins

2020-09-14T10:30:34Z

Colin: /* Rodin Update Site */ update project diagram status

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] || Automatic prover using SMT solvers
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || || Improves chance of automatic proof by selecting relevant hypotheses
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] || generates a Latex documentation of the Event-B
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || available || 3.x.x || 4 Nov 2018 || [mailto:umlb@soton.ac.uk umlb] || Tree-structured editor for Event-B EMF that handles extensions without modification. Mainly useful for Plug-in developers.
|-
| CODA || CODA Component Diagrams || 6.0.1 || available || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Component diagrams with timed channels. ('''Not compatible with latest UML-B.''' Will be up-issued on Soton update site.)
|-
| CODA || CODA Simulator for Component Diagrams || 3.0.1 || available || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Component based simulation. ('''Not compatible with latest UML-B.''' Will be up-issued on Soton update site.)
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || available || 3.x.x || 1st Feb. 2015 || [mailto:umlb@soton.ac.uk umlb] || Machine - Context relationship diagram. ('''Not compatible with latest UML-B.''' Will be up-issued on Soton update site.)
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:lvoisin@users.sourceforge.net Laurent] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:umlb@soton.ac.uk umlb] || For Java, Ada, and OpenMP C code
|-.x
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || not working || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] || Needs updating to be compatible with changes in Rodin 3.5
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk Asieh] ||
|-
| ||[[Records|Records]] || 2.0.0 || not checked || 2.x.x || 16th Oct. 2010 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use CamilleX instead
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:umlb@soton.ac.uk umlb] || No longer supported - use CamilleX instead. Provides a synchronised copy of Machines and Contexts for committing into a repository.
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:IUMLB_big.png|30px]] ||iUML-B plugins || || not checked || 3.x.x || || [mailto:umlb@soton.ac.uk umlb] || New versions are now available on the Soton Update Site.
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|UML-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 11 Sept 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B Class diagrams translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|UML-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B State-machines translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|UML-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Animate UML-B State-machines. Compatible with UML-B statemachines 4.x.x and ProB 3.0.x.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Scenario Checker|Scenario Checker]] || 0.0.0 || new release || 3.4.x || 31 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Validation tool for recording and replaying scenarios
|}

The following framework plug-ins are also provided on the Southampton Releases Update Site. These plugins are installed automatically when required and are not usually installed explicitly by users.
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF extensions]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|UML-B diagrams]] || 8.0.1 || new release || 3.2.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[ProB Support|ProB Support]] || 0.0.0 || new release || 3.4.x || 28 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|}

Rodin Platform 3.5.0 External Plug-ins

2020-09-14T09:41:21Z

Colin: /* Rodin Update Site */ fix icon for iUML-B and change status of Qualitativ probability

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] || Automatic prover using SMT solvers
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || || Improves chance of automatic proof by selecting relevant hypotheses
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] || generates a Latex documentation of the Event-B
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || available || 3.x.x || 4 Nov 2018 || [mailto:umlb@soton.ac.uk umlb] || Tree-structured editor for Event-B EMF that handles extensions without modification. Mainly useful for Plug-in developers.
|-
| CODA || CODA Component Diagrams || 6.0.1 || available || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Component diagrams with timed channels. (Not compatible with latest UML-B. Will be up-issued on Soton update site.)
|-
| CODA || CODA Simulator for Component Diagrams || 3.0.1 || available || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Component based simulation. (Not compatible with latest UML-B. Will be up-issued on Soton update site.)
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || not checked || 3.x.x || 1st Feb. 2015 || [mailto:umlb@soton.ac.uk umlb] || Machine - Context relationship diagram
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:umlb@soton.ac.uk umlb] || Provides a synchronised copy of Machines and Contexts for committing into a repository. It is recommended to also install the Rose editor, EMF compare 3.1.0 and a recent repository client (e.g. Egit 4.1.4).
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:lvoisin@users.sourceforge.net Laurent] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:umlb@soton.ac.uk umlb] || For Java, Ada, and OpenMP C code
|-.x
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || not working || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] || Needs updating to be compatible with changes in Rodin 3.5
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk Asieh] ||
|-
| ||[[Records|Records]] || 2.0.0 || not checked || 2.x.x || 16th Oct. 2010 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use CamilleX instead
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:IUMLB_big.png|30px]] ||iUML-B plugins || || not checked || 3.x.x || || [mailto:umlb@soton.ac.uk umlb] || New versions are now available on the Soton Update Site.
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|UML-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 11 Sept 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B Class diagrams translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|UML-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B State-machines translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|UML-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Animate UML-B State-machines. Compatible with UML-B statemachines 4.x.x and ProB 3.0.x.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Scenario Checker|Scenario Checker]] || 0.0.0 || new release || 3.4.x || 31 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Validation tool for recording and replaying scenarios
|}

The following framework plug-ins are also provided on the Southampton Releases Update Site. These plugins are installed automatically when required and are not usually installed explicitly by users.
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF extensions]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|UML-B diagrams]] || 8.0.1 || new release || 3.2.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[ProB Support|ProB Support]] || 0.0.0 || new release || 3.4.x || 28 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|}

Rodin Platform 3.5.0 External Plug-ins

2020-09-14T09:32:16Z

Colin: /* Rodin Update Site */ checked CODA

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] || Automatic prover using SMT solvers
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || || Improves chance of automatic proof by selecting relevant hypotheses
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] || generates a Latex documentation of the Event-B
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || available || 3.x.x || 4 Nov 2018 || [mailto:umlb@soton.ac.uk umlb] || Tree-structured editor for Event-B EMF that handles extensions without modification. Mainly useful for Plug-in developers.
|-
| CODA || CODA Component Diagrams || 6.0.1 || available || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Component diagrams with timed channels. (Not compatible with latest UML-B. Will be up-issued on Soton update site.)
|-
| CODA || CODA Simulator for Component Diagrams || 3.0.1 || available || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Component based simulation. (Not compatible with latest UML-B. Will be up-issued on Soton update site.)
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || not checked || 3.x.x || 1st Feb. 2015 || [mailto:umlb@soton.ac.uk umlb] || Machine - Context relationship diagram
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:umlb@soton.ac.uk umlb] || Provides a synchronised copy of Machines and Contexts for committing into a repository. It is recommended to also install the Rose editor, EMF compare 3.1.0 and a recent repository client (e.g. Egit 4.1.4).
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:lvoisin@users.sourceforge.net Laurent] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:umlb@soton.ac.uk umlb] || For Java, Ada, and OpenMP C code
|-.x
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || not checked || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk Asieh] ||
|-
| ||[[Records|Records]] || 2.0.0 || not checked || 2.x.x || 16th Oct. 2010 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use CamilleX instead
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:Umlb32.gif|30px]] ||iUML-B plugins || || not checked || 3.x.x || || [mailto:umlb@soton.ac.uk umlb] || New versions are now available on the Soton Update Site.
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|UML-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 11 Sept 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B Class diagrams translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|UML-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B State-machines translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|UML-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Animate UML-B State-machines. Compatible with UML-B statemachines 4.x.x and ProB 3.0.x.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Scenario Checker|Scenario Checker]] || 0.0.0 || new release || 3.4.x || 31 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Validation tool for recording and replaying scenarios
|}

The following framework plug-ins are also provided on the Southampton Releases Update Site. These plugins are installed automatically when required and are not usually installed explicitly by users.
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF extensions]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|UML-B diagrams]] || 8.0.1 || new release || 3.2.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[ProB Support|ProB Support]] || 0.0.0 || new release || 3.4.x || 28 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|}

Rodin Platform 3.5.0 External Plug-ins

2020-09-14T09:19:15Z

Colin: /* Rodin Update Site */ update some status and re-arrange

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] || Automatic prover using SMT solvers
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || || Improves chance of automatic proof by selecting relevant hypotheses
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] || generates a Latex documentation of the Event-B
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || available || 3.x.x || 4 Nov 2018 || [mailto:umlb@soton.ac.uk umlb] || Tree-structured editor for Event-B EMF that handles extensions without modification. Mainly useful for Plug-in developers.
|-
| CODA || CODA Component Diagrams || 6.0.1 || available || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Component diagrams with timed channels. (Not compatible with latest UML-B. Will be up-issued on Soton update site.)
|-
| CODA || CODA Simulator for Component Diagrams || 3.0.1 || not checked || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Not compatible with latest UML-B. To be re-issued on Soton update site
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || not checked || 3.x.x || 1st Feb. 2015 || [mailto:umlb@soton.ac.uk umlb] || Machine - Context relationship diagram
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:umlb@soton.ac.uk umlb] || Provides a synchronised copy of Machines and Contexts for committing into a repository. It is recommended to also install the Rose editor, EMF compare 3.1.0 and a recent repository client (e.g. Egit 4.1.4).
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:lvoisin@users.sourceforge.net Laurent] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:umlb@soton.ac.uk umlb] || For Java, Ada, and OpenMP C code
|-.x
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || available || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk Asieh] ||
|-
| ||[[Records|Records]] || 2.0.0 || not checked || 2.x.x || 16th Oct. 2010 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use CamilleX instead
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|UML-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 11 Sept 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B Class diagrams translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|UML-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B State-machines translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|UML-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Animate UML-B State-machines. Compatible with UML-B statemachines 4.x.x and ProB 3.0.x.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Scenario Checker|Scenario Checker]] || 0.0.0 || new release || 3.4.x || 31 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Validation tool for recording and replaying scenarios
|}

The following framework plug-ins are also provided on the Southampton Releases Update Site. These plugins are installed automatically when required and are not usually installed explicitly by users.
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF extensions]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|UML-B diagrams]] || 8.0.1 || new release || 3.2.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[ProB Support|ProB Support]] || 0.0.0 || new release || 3.4.x || 28 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|}

Rodin Platform 3.5.0 External Plug-ins

2020-09-11T17:22:38Z

Colin: /* Southampton Releases Update Site */ add scenario checker and prob support

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| CODA || CODA Component Diagrams || 6.0.1 || not checked || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Not compatible with latest UML-B. To be re-issued on Soton update site
|-
| CODA || CODA Simulator for Component Diagrams || 3.0.1 || not checked || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Not compatible with latest UML-B. To be re-issued on Soton update site
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || not checked || 3.x.x || 4 Nov 2018 || [mailto:umlb@soton.ac.uk umlb] || Mainly useful for Plug-in developers. Tree-structured editor for Event-B EMF that handles extensions without modification
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || not checked || 3.x.x || 1st Feb. 2015 || [mailto:umlb@soton.ac.uk umlb] || Machine - Context relationship diagram
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:umlb@soton.ac.uk umlb] || Provides a synchronised copy of Machines and Contexts for committing into a repository. It is recommended to also install the Rose editor, EMF compare 3.1.0 and a recent repository client (e.g. Egit 4.1.4).
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:lvoisin@users.sourceforge.net Laurent] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:umlb@soton.ac.uk umlb] || For Java, Ada, and OpenMP C code
|-.x
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || ||
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || available || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk Asieh] ||
|-
| ||[[Records|Records]] || 2.0.0 || not checked || 2.x.x || 16th Oct. 2010 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use CamilleX instead
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|UML-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 11 Sept 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B Class diagrams translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|UML-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B State-machines translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|UML-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Animate UML-B State-machines. Compatible with UML-B statemachines 4.x.x and ProB 3.0.x.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Scenario Checker|Scenario Checker]] || 0.0.0 || new release || 3.4.x || 31 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Validation tool for recording and replaying scenarios
|}

The following framework plug-ins are also provided on the Southampton Releases Update Site. These plugins are installed automatically when required and are not usually installed explicitly by users.
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF extensions]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|UML-B diagrams]] || 8.0.1 || new release || 3.2.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[ProB Support|ProB Support]] || 0.0.0 || new release || 3.4.x || 28 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|}

Rodin Platform 3.5.0 External Plug-ins

2020-09-11T17:16:06Z

Colin: /* Rodin Update Site */ update some emails etc

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| CODA || CODA Component Diagrams || 6.0.1 || not checked || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Not compatible with latest UML-B. To be re-issued on Soton update site
|-
| CODA || CODA Simulator for Component Diagrams || 3.0.1 || not checked || 3.x.x || ? || [mailto:umlb@soton.ac.uk umlb] || Not compatible with latest UML-B. To be re-issued on Soton update site
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || not checked || 3.x.x || 4 Nov 2018 || [mailto:umlb@soton.ac.uk umlb] || Mainly useful for Plug-in developers. Tree-structured editor for Event-B EMF that handles extensions without modification
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || not checked || 3.x.x || 1st Feb. 2015 || [mailto:umlb@soton.ac.uk umlb] || Machine - Context relationship diagram
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:umlb@soton.ac.uk umlb] || Provides a synchronised copy of Machines and Contexts for committing into a repository. It is recommended to also install the Rose editor, EMF compare 3.1.0 and a recent repository client (e.g. Egit 4.1.4).
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.x.x
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:lvoisin@users.sourceforge.net Laurent] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:umlb@soton.ac.uk umlb] || For Java, Ada, and OpenMP C code
|-.x
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || ||
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || available || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk Asieh] ||
|-
| ||[[Records|Records]] || 2.0.0 || not checked || 2.x.x || 16th Oct. 2010 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use CamilleX instead
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:umlb@soton.ac.uk umlb] || no longer supported - use new UML-B from Soton update site instead
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|UML-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 11 Sept 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B Class diagrams translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|UML-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B State-machines translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|UML-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Animate UML-B State-machines. Compatible with UML-B statemachines 4.x.x and ProB 3.0.x.
|}

The following framework plug-ins are also provided on the Southampton Releases Update Site. These plugins are installed automatically when required and are not usually installed explicitly by users.
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF extensions]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|UML-B diagrams]] || 8.0.1 || new release || 3.2.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|}

Rodin Platform 3.5.0 External Plug-ins

2020-09-11T17:01:01Z

Colin: /* Rodin Update Site */ update entries on rodin update site

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || not checked || 3.x.x || 4 Nov 2018 || [mailto:cfs@ecs.soton.ac.uk email] || Mainly useful for Plug-in developers. Tree-structured editor for Event-B EMF that handles extensions without modification
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || not checked || 3.x.x || 1st Feb. 2015 || [mailto:vs2@ecs.soton.ac.uk email] || Machine - Context relationship diagram
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:cfs@ecs.soton.ac.uk email] || Provides a synchronised copy of Machines and Contexts for committing into a repository. It is recommended to also install the Rose editor, EMF compare 3.1.0 and a recent repository client (e.g. Egit 4.1.4).
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:cfs@ecs.soton.ac.uk email] || Compatible with Rodin 3.x.x (checked by cfs 5/05/17)
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:cfs@ecs.soton.ac.uk email] || Compatible with Rodin 3.x.x (checked by cfs 4/05/17)
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:asf08r@ecs.soton.ac.uk email] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:asf08r@ecs.soton.ac.uk email] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:ae2@ecs.soton.ac.uk email] || For Java, Ada, and OpenMP C code
|-.x
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || ||
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || available || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk email] ||
|-
| ||[[Records|Records]] || 2.0.0 || not checked || 2.x.x || 16th Oct. 2010 || [mailto:cfs@ecs.soton.ac.uk email] || no longer supported - use CamilleX instead
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:cfs@ecs.soton.ac.uk email] || no longer supported - use new UML-B from Soton update site instead
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:vs2@ecs.soton.ac.uk email] || no longer supported - use new UML-B from Soton update site instead
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|UML-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 11 Sept 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B Class diagrams translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|UML-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B State-machines translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|UML-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Animate UML-B State-machines. Compatible with UML-B statemachines 4.x.x and ProB 3.0.x.
|}

The following framework plug-ins are also provided on the Southampton Releases Update Site. These plugins are installed automatically when required and are not usually installed explicitly by users.
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF extensions]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|UML-B diagrams]] || 8.0.1 || new release || 3.2.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|}

Rodin Platform 3.5.0 External Plug-ins

2020-09-11T16:37:04Z

Colin: /* Southampton Releases Update Site */ update versions, names and release dates

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || new release || 3.x.x || 4 Nov 2018 || [mailto:cfs@ecs.soton.ac.uk email] || Mainly useful for Plug-in developers. Tree-structured editor for Event-B EMF that handles extensions without modification
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || not checked || 3.x.x || 1st Feb. 2015 || [mailto:vs2@ecs.soton.ac.uk email] || Machine - Context relationship diagram
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:cfs@ecs.soton.ac.uk email] || Original UML-B modelling environment
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:vs2@ecs.soton.ac.uk email] || Compatible with UML-B 2.3 and ProB 3.0
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:cfs@ecs.soton.ac.uk email] || Provides a synchronised copy of Machines and Contexts for committing into a repository. It is recommended to also install the Rose editor, EMF compare 3.1.0 and a recent repository client (e.g. Egit 4.1.4).
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:cfs@ecs.soton.ac.uk email] || Compatible with Rodin 3.x.x (checked by cfs 5/05/17)
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:cfs@ecs.soton.ac.uk email] || Compatible with Rodin 3.x.x (checked by cfs 4/05/17)
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:asf08r@ecs.soton.ac.uk email] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:asf08r@ecs.soton.ac.uk email] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:ae2@ecs.soton.ac.uk email] || For Java, Ada, and OpenMP C code
|-.x
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || ||
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || available || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk email] ||
|-
| ||[[Records|Records]] || 2.0.0 || available || 2.x.x || 16th Oct. 2010 || [mailto:cfs@ecs.soton.ac.uk email] ||
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|UML-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 11 Sept 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B Class diagrams translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|UML-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || UML-B State-machines translate into Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|UML-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Animate UML-B State-machines. Compatible with UML-B statemachines 4.x.x and ProB 3.0.x.
|}

The following framework plug-ins are also provided on the Southampton Releases Update Site. These plugins are installed automatically when required and are not usually installed explicitly by users.
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF extensions]] || 6.1.0 || new release || 3.x.x || 4 July 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|UML-B diagrams]] || 8.0.1 || new release || 3.2.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|}

Rodin Platform 3.5.0 External Plug-ins

2020-09-11T16:15:41Z

Colin: /* Southampton Releases Update Site */ fix separate table for frameworks and fix versions and emails

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || new release || 3.x.x || 4 Nov 2018 || [mailto:cfs@ecs.soton.ac.uk email] || Mainly useful for Plug-in developers. Tree-structured editor for Event-B EMF that handles extensions without modification
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || not checked || 3.x.x || 1st Feb. 2015 || [mailto:vs2@ecs.soton.ac.uk email] || Machine - Context relationship diagram
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:cfs@ecs.soton.ac.uk email] || Original UML-B modelling environment
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:vs2@ecs.soton.ac.uk email] || Compatible with UML-B 2.3 and ProB 3.0
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:cfs@ecs.soton.ac.uk email] || Provides a synchronised copy of Machines and Contexts for committing into a repository. It is recommended to also install the Rose editor, EMF compare 3.1.0 and a recent repository client (e.g. Egit 4.1.4).
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:cfs@ecs.soton.ac.uk email] || Compatible with Rodin 3.x.x (checked by cfs 5/05/17)
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:cfs@ecs.soton.ac.uk email] || Compatible with Rodin 3.x.x (checked by cfs 4/05/17)
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:asf08r@ecs.soton.ac.uk email] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:asf08r@ecs.soton.ac.uk email] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:ae2@ecs.soton.ac.uk email] || For Java, Ada, and OpenMP C code
|-.x
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || ||
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || available || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk email] ||
|-
| ||[[Records|Records]] || 2.0.0 || available || 2.x.x || 16th Oct. 2010 || [mailto:cfs@ecs.soton.ac.uk email] ||
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|Event-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 11 Sept 2020 || [mailto:umlb@soton.ac.uk umlb] || Class diagrams contained in Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|Event-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || State-machines contained in Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|Event-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:umlb@soton.ac.uk umlb] || Compatible with Event-B statemachines 4.x.x and ProB 3.0.x.
|}

The following framework plug-ins are also provided on the Southampton Releases Update Site. These plugins are installed automatically when required and are not usually installed explicitly by users.
{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.0.0 || new release || 3.x.x || 4 Nov 2018 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF support for extensions]] || 6.0.0 || new release || 3.x.x || 17th Dec 2015 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF support for diagrams]] || 7.0.0 || new release || 3.2.x || 17th Dec 2015 || [mailto:umlb@soton.ac.uk umlb] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|}

Rodin Platform 3.5.0 External Plug-ins

2020-09-11T16:04:27Z

Colin: /* Southampton Releases Update Site */ add UML-B classdiagrams and frameworks

==== Rodin Update Site ====

Available from http://rodin-b-sharp.sourceforge.net/updates

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:Rose.gif|30px]]||[[Rose_(Structured)_Editor|Rose editor]] || 1.7.0 || new release || 3.x.x || 4 Nov 2018 || [mailto:cfs@ecs.soton.ac.uk email] || Mainly useful for Plug-in developers. Tree-structured editor for Event-B EMF that handles extensions without modification
|-
| [[Image:Project diagram icon s.png|30px]]||[[Project_Diagram|Project Diagram]]|| 1.0.1 || not checked || 3.x.x || 1st Feb. 2015 || [mailto:vs2@ecs.soton.ac.uk email] || Machine - Context relationship diagram
|-
| [[Image:Umlb32.gif|30px]] || [[UML-B|UML-B]] || 2.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:cfs@ecs.soton.ac.uk email] || Original UML-B modelling environment
|-
| [[Image:Umlb32.gif|30px]] ||[[UML-B_-_Statemachine_Animation|UML-B Statemachine Animation]] || 1.3.0 || not checked || 3.x.x || 18th Oct. 2014 || [mailto:vs2@ecs.soton.ac.uk email] || Compatible with UML-B 2.3 and ProB 3.0
|-
| ||[[EMF_Compare_Editor_installation|Teamwork]] || 1.2.0 || not checked || 3.2.x || 5th Sept. 2016 || [mailto:cfs@ecs.soton.ac.uk email] || Provides a synchronised copy of Machines and Contexts for committing into a repository. It is recommended to also install the Rose editor, EMF compare 3.1.0 and a recent repository client (e.g. Egit 4.1.4).
|-
| [[Image:Cmp_mch_obj.gif|20px]] ||[[Parallel_Composition_using_Event-B | Shared Event Composition]] || 1.7.1 || not checked || || 5th July 2017 || [mailto:cfs@ecs.soton.ac.uk email] || Compatible with Rodin 3.x.x (checked by cfs 5/05/17)
|-
| [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || not checked || || 4th July 2017 || [mailto:cfs@ecs.soton.ac.uk email] || Compatible with Rodin 3.x.x (checked by cfs 4/05/17)
|-
| ||[[Refactoring Framework | Refactory ]]|| 1.3.0 || not checked|| 3.x.x || 6th May 2014 || [mailto:asf08r@ecs.soton.ac.uk email] || Compatible with Rodin 3.0.x.
|-
| || [[Theory Plug-in| Theory Plug-in]] || 3.0.0 || not checked|| || 17th Dec 2014|| [mailto:asf08r@ecs.soton.ac.uk email] ||
|-.x
| || [[Code Generation Activity | Code Generation]] || 0.2.5 || not checked|| || 29th Aug. 2013|| [mailto:ae2@ecs.soton.ac.uk email] || For Java, Ada, and OpenMP C code
|-.x
|-
| || Relevance Filter || 1.1.1 || available || ?.x.x || || ||
|-
| || [[Isabelle for Rodin]] || || not checked || 2.x.x || || ||
|-
| || [[SMT_Plug-in | SMT Solvers ]] || 1.4.0 || available || || 15th March 2016|| [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Pattern | Pattern]] || 0.9.0 || not checked || 3.x.x || 13th March 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[Event-B Qualitative Probability User Guide | Qualitative Probability]] || 0.2.3 || available || 3.x.x || 9th October 2015 || [mailto:tshoang@users.sourceforge.net Thai Son Hoang] ||
|-
| || [[B2Latex | B2Latex export]] || 0.7.0 || available || 2.5.x || 27th May 2015 || [mailto:lvoisin@users.sourceforge.net Laurent Voisin] ||
|-
| || [[Generic Instantiation Plug-in User Guide | Generic Instantiation (Soton)]] || 1.0.1 || not checked || || 05th March 2013 || [mailto:asf08r@ecs.soton.ac.uk email] ||
|-
| ||[[Records|Records]] || 2.0.0 || available || 2.x.x || 16th Oct. 2010 || [mailto:cfs@ecs.soton.ac.uk email] ||
|}

==== Atelier B Update Site ====

Available from http://methode-b.com/update_site/atelierb_provers

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || Atelier B provers || 2.2.1 || available || 3.3.0 || 7 Aug 2017 || || Does not work with macOS Catalina!
|}

==== ProB Update Site ====

Available from http://www.stups.hhu.de/prob_updates_rodin3

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| || ProB || 3.0.10 || available || 3.5.0 || 4 Sep 2020 || || The ProB animator and model checker
|-
| || ProB (Dis)Prover || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || || The ProB counter-example finder and prover
|-
| || ProB Symbolic constants support || 3.0.9 || available || 3.5.0 || 4 Sep 2020 || ||
|}

==== Southampton Releases Update Site ====

Available from http://eventb-soton.github.io/updateSite/releases

{{SimpleHeader}}
|-
! scope=col | || Plug-in name || Version || Status || MCV* || Release Date || Contact || Additional info
|-
| [[Image:CamilleX.png|CmX]] || [[CamilleX|CamilleX]] || 2.0.0 || new release || 3.4.0 || 29 Jul 2020 || [mailto:T.S.Hoang@ecs.soton.ac.uk Thai Son Hoang] || CamilleX provides text editors for Event-B models and support modelling mechanisms such as machine inclusion.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Classdiagrams|Event-B Class Diagrams]] || 3.0.0 || new release || 3.x.x || 4 Nov 2018 || [mailto:cfs@ecs.soton.ac.uk email] || Class diagrams contained in Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] || [[Event-B_Statemachines|Event-B State-machines]] || 4.0.1 || new release || 3.x.x || 13 Aug 2020 || [mailto:cfs@ecs.soton.ac.uk Colin Snook] || State-machines contained in Event-B Machines.
|-
| [[Image:IUMLB_big.png|30px]] ||[[Event-B_Statemachines|Event-B State-machine Animation]] || 3.0.0 || new release || 3.x.x || 13 Aug 2020 || [mailto:cfs@ecs.soton.ac.uk Colin Snook] || Compatible with Event-B statemachines 4.x.x and ProB 3.0.x.
|}
| ||[[EMF_framework_for_Event-B|Event-B EMF framework]] || 6.0.0 || new release || 3.x.x || 4 Nov 2018 || [mailto:cfs@ecs.soton.ac.uk email] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF support for extensions]] || 6.0.0 || new release || 3.x.x || 17th Dec 2015 || [mailto:cfs@ecs.soton.ac.uk email] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-
| ||[[Generic_Event-B_EMF_extensions|Event-B EMF support for diagrams]] || 7.0.0 || new release || 3.2.x || 17th Dec 2015 || [mailto:cfs@ecs.soton.ac.uk email] || Provided for plug-in developers. End users should not need to install this framework. It will be installed automatically by other plug-ins as required.
|-

Rodin Platform 3.5.0 External Plug-ins

2020-09-11T16:02:43Z

Colin: /* Rodin Update Site */ remove soton plugins - classdiagrams and frameworks

Generic Event-B EMF extensions

2020-05-30T11:01:56Z

Colin: /* Contributing new EMF element types to the Navigator view */

==Modelling==

==Persistence==

Event-B EMF Models may be persisted in several ways:
# inside a Rodin file by extending Rodin and the Event-B EMF persistence with new Rodin elements and synchronisers to load and save. (This is how the Event-B EMF core plugin works, except that the Rodin elements for standard Event-B already existed).
# inside a Rodin file as a String attribute containing XMI, using the SerialisedExtensionSynchroniser. (This is how UML-B diagrams are saved inside Machines)
# in EMF format as an XMI file.
# in plain text using the XText framework.

Here we mainly focus on methods 2 and 3.
We are also developing method 4. as a text persistence, but this is described elsewhere.
We do not intend to use method 1 as we do not need Rodin to understand the model (because we translate into standard Machines and Context for verification).

For method 2, declare your root meta-class to use the ''SerialisedExtensionSynchroniser'' using the extension point ''org.eventb.emf.persistence.synchroniser'' e.g.
<extension
point="org.eventb.emf.persistence.synchroniser">
<emfPackage
name="Statemachines Package"
nsURI="http://soton.ac.uk/models/eventb/statemachines/2014">
<synchroniser
emf_class="Statemachine"
name="Statemachine"
rodin_id="ac.soton.eventb.emf.core.extension.persistence.serialisedExtension"
synchroniser_class="ac.soton.eventb.emf.core.extension.persistence.SerialisedExtensionSynchroniser">
</synchroniser>
</emfPackage>
</extension>

For method 3, due to the way the Event-B EMF framework implements references, it is important to save files using certain non-default styles.
To achieve this, declare the content type of your file as ''ac.soton.eventb.emf.core.extension.persistence.contentType'' using the extension point ''org.eclipse.core.contenttype.contentTypes'' e.g.
<extension
point="org.eclipse.core.contenttype.contentTypes">
<file-association
content-type="ac.soton.eventb.emf.core.extension.persistence.contentType"
file-extensions="umlb">
</file-association>
</extension>

==Navigator==

This section describes how to extend the Event-B Navigator to support Event-B EMF extensions.

===Contributing new EMF element types to the Navigator view===

The Event-B EMF extensions framework makes it easy to contribute new types of models to the Event-B navigator.
You just need to tell the framework some details about your models (as follows) and it does the rest.

If the EMF element types are contained in a new file type, declare the new file extension using the extension point:

ac.soton.eventb.emf.core.extension.navigator.emfFileExtensions

This tells the extensions plugin to adapt the emf contents of those files to be shown in the Navigator.

To ensure the EMF elements are labeled and imaged correctly in the Navigator, declare the EMF adapter factory to the framework using the extension point:

ac.soton.eventb.emf.core.extension.navigator.adapterFactories

(Note - the adapter factory is generated by the EMF genmodel in the edit plugin).

==Refinement==

[THIS SECTION NEEDS REVIEW AND UPDATE]

The Rodin platform provides an extension point for contributing behaviour to the 'Refine' action.
For Serialised Event-B EMF extensions, an abstract, reflective refinement contributor class is provided to simplify the task of making a refinement.

The class is:
ac.soton.eventb.emf.core.extension.navigator.refiner$AbstractExtensionRefiner which implements IRefinementParticipant.

The class should be extended by a client plug-in and the client's class should be registered as a Refinement Participant using the relevant Rodin extension point
The client class must implement the method getExtensionID() to return the relevant Extension ID string that identifies such extensions.
The client class may override populateReferenceMap(Map<EReference,Boolean>) to add the EReference Features that need to be dealt with, defining which ones are back references to the corresponding abstract element (put true in map) and which ones should reference the corresponding element in the copy (put false in map).
The client class may also override populateFilterByTypeList(List<EClass>) to add the EClass of any types of element that should not be copied into the refinement.

The generic refiner class works as follows:
* All serialised extensions of the given Extension ID in the Rodin resource are loaded
* Each one is deep cloned using the Ecore copier utility
* The contents of the clone extension are then searched for any elements of the EClasses in the client supplied list to be filtered. Such elements are deleted from the clone.
* The contents of the clone extension are then searched for elements that own one of the client supplied EReferences.
* For each reference, the reference is either set to reference the corresponding source abstract element or copied so that it corresponds to the abstract reference

==Diagrams==

==Generator==

[THIS SECTION NEEDS REVIEW AND UPDATE -
Note: The generator is now based on a more generic EMF translator: https://github.com/eventB-Soton/EMF_Translator
It is adapted to Event-B : https://github.com/eventB-Soton/EventB_Translator_Support
There is a documentation plugin in the EMF translator source code that describes the necessary extension points and how to contribute a specific translation.]

A framework to support the implementation of generators is provided. The framework is designed to support the generation of standard Event-B models from higher-level model extensions that are based on the Event-B EMF modelling extensions framework.

The Generator framework provides:

* A toolbar button to initiate the generation
* Generic code to remove previously generated elements
* Generic code to organise the incorporation of newly generated elements
* Utilities to aid the creation of new elements
* An abstract basis for client defined rules
* An extension point for clients to declare generators and generation rules

The client rules return generation descriptors (rather than modifying the target model directly). The framework takes care of updating the model (within the clients Transactional Editing Domain) provided the generation completes successfully. This ensures that the model is not left in an inconsistent state should the generation fail. The generation descriptors allow the client to specify where the new element should be contained and a priority which will be used to influence the placement of the new element within the containment ordering.

To define a particular generator a client should:

* Define an extension of org.eclipse.ui.handlers to enable the generate command when the activePartID is their Editor (see [[Defining a generator handler]])
* Define an extension of ac.soton.eventb.emf.diagrams.generator.rule to make the generator framework aware of your generator and its rule classes.
* Implement your rule classes

=== Generation Descriptors ===

Each rule should return a collection of one or more Generation Descriptors. Generation Descriptors have the following fields which are explained in this section.

* EventBElement parent;
* EStructuralFeature feature;
* Object value;
* Integer priority;
* Boolean editable;
* Boolean remove;

The feature of the parent will be changed in the following ways:

If remove is false:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be added to the containment in a position according to the priority
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be added to the reference in a position according to the priority
* 3) If the feature is an EAttribute and the value is of the correct type, the feature will be set to the value

Priority can be used to control the relative position of the generated elements
* 1 - must come first
* 10 - not important
* ---user entered items---
* 0 must come after user entered items
* -10 must come last

Editable - this affects read-only status of the generated element and whether or not it will be preserved or re-generated in a subsequent generation.
* false - the element is set as read-only (the user cannot change its attributes nor add/remove children), any existing copy of the element will be deleted and re-generated at each re-generation
* true - the element is not read-only and will not be deleted before re-generation. (N.B. It is the responsibility of the client rules to check whether this element already exists and only only generate a new one if it does not)

If remove is true:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be deleted from the containment
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be removed from the reference
* 3) If the feature is an EAttribute, the feature will be unset

=== Implementing Rule Classes ===

Rule classes must implement IRule. It is recommended the rule classes extend ac.soton.eventb.emf.diagrams.generator#AbstractRule which provides some concise constants for the commonly needed containments and defines some default behaviour (always enabled and dependencies ok). Note that the rule will only be attempted for the type of source element defined in the extension point. However, this could be defined as an abstract base class to allow the rule to operate on several types of element.

A rule has 4 methods:

* boolean enabled (final EventBElement sourceElement)
* boolean dependenciesOK(EventBElement sourceElement,List<GenerationDescriptor> generatedElements)
* boolean fireLate()
* List<GenerationDescriptor> fire(EventBElement sourceElement, List<GenerationDescriptor> generatedElements)

The enabled method can be used to restrict when it applies. More than one rule can be defined for the same kind of element allowing the generation to be decomposed in a maintainable way.

TheDependenciesOK method allows the method to be deferred since the success of rules may depend on what has already been generated. The dependenciesOK method is passed the list of GenerationDescriptors created so far.

The fireLate method forces the rule to be fired when all other rules have been fired. This is usually used when the rules behaviour depends on what other rules have done.

The fire method must return a list of GenerationDescriptors describing what should be generated. The Utility class, Make, provides a convenience method to help construct a GenerationDescriptor from the parent element, the containment feature, the new child and the priority indicator and if needed the editable setting.

Priority may be from 10 to -10, where 1 indicates first in the containment and -10 last in the containment. Elements in the containment that are not (currently) being generated are placed between priorities 10 and 0. Bear in mind that the relative position of different diagrams (extensions)is preserved within each priority band. Also the order of source elements within their containment is preserved within each priority band.

1 2 3 4 5 6 7 8 9 10 <other content> 0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10

For example, a basic type invariant that doesn't depend on other variables might be placed at position 1 whereas a theorem or invariant included purely for proof purposes might be placed at position -10.

A current limitation of the priority scheme is that there are a limited number of priorities. For example, this could be a problem if a rule needs to calculate positions of each element within a collection based on dependencies of the element instance.

In most cases the generated element should be set as read-only (the default). In this case the element will be deleted and re-generated on each invocation of the generator. The should not change any attributes of the element nor add to its children. In some case, however, it is necessary to generate an element whose contents may be modified by the user. To do this set the editable parameter of the Generation Descriptor. In this case the generated element will not be deleted when the generator is next invoked. The rule must take care not to return another Generation Descriptor if the element has already been generated. It should look for a suitable generated element (to use for adding further generated chldren etc.) and only generate a new one if it doesn't exist.

Where a tree structure is entirely generated within one rule firing (e.g. an event with guards and actions) it is more efficient to construct the entire event and return a single Generation Descriptor that adds that event. It is also possible to do this by returning separate Generation Descriptors to add the event and each guard and action individually.

A typical line from a rule class might look like this:
ret.add(Make.descriptor(machine,invariants,Make.invariant("myInvariantName", "myVar >0","my comment"),10));
where,
ret is the list to be returned and machine is the parent element containing the invariants to be added to.

Generic Event-B EMF extensions

2020-05-30T08:49:42Z

Colin: /* Persistence */

==Modelling==

==Persistence==

Event-B EMF Models may be persisted in several ways:
# inside a Rodin file by extending Rodin and the Event-B EMF persistence with new Rodin elements and synchronisers to load and save. (This is how the Event-B EMF core plugin works, except that the Rodin elements for standard Event-B already existed).
# inside a Rodin file as a String attribute containing XMI, using the SerialisedExtensionSynchroniser. (This is how UML-B diagrams are saved inside Machines)
# in EMF format as an XMI file.
# in plain text using the XText framework.

Here we mainly focus on methods 2 and 3.
We are also developing method 4. as a text persistence, but this is described elsewhere.
We do not intend to use method 1 as we do not need Rodin to understand the model (because we translate into standard Machines and Context for verification).

For method 2, declare your root meta-class to use the ''SerialisedExtensionSynchroniser'' using the extension point ''org.eventb.emf.persistence.synchroniser'' e.g.
<extension
point="org.eventb.emf.persistence.synchroniser">
<emfPackage
name="Statemachines Package"
nsURI="http://soton.ac.uk/models/eventb/statemachines/2014">
<synchroniser
emf_class="Statemachine"
name="Statemachine"
rodin_id="ac.soton.eventb.emf.core.extension.persistence.serialisedExtension"
synchroniser_class="ac.soton.eventb.emf.core.extension.persistence.SerialisedExtensionSynchroniser">
</synchroniser>
</emfPackage>
</extension>

For method 3, due to the way the Event-B EMF framework implements references, it is important to save files using certain non-default styles.
To achieve this, declare the content type of your file as ''ac.soton.eventb.emf.core.extension.persistence.contentType'' using the extension point ''org.eclipse.core.contenttype.contentTypes'' e.g.
<extension
point="org.eclipse.core.contenttype.contentTypes">
<file-association
content-type="ac.soton.eventb.emf.core.extension.persistence.contentType"
file-extensions="umlb">
</file-association>
</extension>

==Navigator==

This section describes how to extend the Event-B Navigator to support Event-B EMF extensions.

===Contributing new EMF element types to the Navigator view===

If the EMF element types are contained in a new file type, declare the new file extension using the extension point:

ac.soton.eventb.emf.core.extension.navigator.emfFileExtensions

This tells the extensions plugin to adapt the emf contents of those files to be shown in the Navigator.

To ensure the EMF elements are labeled and imaged correctly in the Navigator, declare the adapter factory using the extension point:

ac.soton.eventb.emf.core.extension.navigator.adapterFactories

(Note - use the adapter factory generated by the EMF genmodel in the edit plugin).

==Refinement==

[THIS SECTION NEEDS REVIEW AND UPDATE]

The Rodin platform provides an extension point for contributing behaviour to the 'Refine' action.
For Serialised Event-B EMF extensions, an abstract, reflective refinement contributor class is provided to simplify the task of making a refinement.

The class is:
ac.soton.eventb.emf.core.extension.navigator.refiner$AbstractExtensionRefiner which implements IRefinementParticipant.

The class should be extended by a client plug-in and the client's class should be registered as a Refinement Participant using the relevant Rodin extension point
The client class must implement the method getExtensionID() to return the relevant Extension ID string that identifies such extensions.
The client class may override populateReferenceMap(Map<EReference,Boolean>) to add the EReference Features that need to be dealt with, defining which ones are back references to the corresponding abstract element (put true in map) and which ones should reference the corresponding element in the copy (put false in map).
The client class may also override populateFilterByTypeList(List<EClass>) to add the EClass of any types of element that should not be copied into the refinement.

The generic refiner class works as follows:
* All serialised extensions of the given Extension ID in the Rodin resource are loaded
* Each one is deep cloned using the Ecore copier utility
* The contents of the clone extension are then searched for any elements of the EClasses in the client supplied list to be filtered. Such elements are deleted from the clone.
* The contents of the clone extension are then searched for elements that own one of the client supplied EReferences.
* For each reference, the reference is either set to reference the corresponding source abstract element or copied so that it corresponds to the abstract reference

==Diagrams==

==Generator==

[THIS SECTION NEEDS REVIEW AND UPDATE -
Note: The generator is now based on a more generic EMF translator: https://github.com/eventB-Soton/EMF_Translator
It is adapted to Event-B : https://github.com/eventB-Soton/EventB_Translator_Support
There is a documentation plugin in the EMF translator source code that describes the necessary extension points and how to contribute a specific translation.]

A framework to support the implementation of generators is provided. The framework is designed to support the generation of standard Event-B models from higher-level model extensions that are based on the Event-B EMF modelling extensions framework.

The Generator framework provides:

* A toolbar button to initiate the generation
* Generic code to remove previously generated elements
* Generic code to organise the incorporation of newly generated elements
* Utilities to aid the creation of new elements
* An abstract basis for client defined rules
* An extension point for clients to declare generators and generation rules

The client rules return generation descriptors (rather than modifying the target model directly). The framework takes care of updating the model (within the clients Transactional Editing Domain) provided the generation completes successfully. This ensures that the model is not left in an inconsistent state should the generation fail. The generation descriptors allow the client to specify where the new element should be contained and a priority which will be used to influence the placement of the new element within the containment ordering.

To define a particular generator a client should:

* Define an extension of org.eclipse.ui.handlers to enable the generate command when the activePartID is their Editor (see [[Defining a generator handler]])
* Define an extension of ac.soton.eventb.emf.diagrams.generator.rule to make the generator framework aware of your generator and its rule classes.
* Implement your rule classes

=== Generation Descriptors ===

Each rule should return a collection of one or more Generation Descriptors. Generation Descriptors have the following fields which are explained in this section.

* EventBElement parent;
* EStructuralFeature feature;
* Object value;
* Integer priority;
* Boolean editable;
* Boolean remove;

The feature of the parent will be changed in the following ways:

If remove is false:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be added to the containment in a position according to the priority
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be added to the reference in a position according to the priority
* 3) If the feature is an EAttribute and the value is of the correct type, the feature will be set to the value

Priority can be used to control the relative position of the generated elements
* 1 - must come first
* 10 - not important
* ---user entered items---
* 0 must come after user entered items
* -10 must come last

Editable - this affects read-only status of the generated element and whether or not it will be preserved or re-generated in a subsequent generation.
* false - the element is set as read-only (the user cannot change its attributes nor add/remove children), any existing copy of the element will be deleted and re-generated at each re-generation
* true - the element is not read-only and will not be deleted before re-generation. (N.B. It is the responsibility of the client rules to check whether this element already exists and only only generate a new one if it does not)

If remove is true:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be deleted from the containment
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be removed from the reference
* 3) If the feature is an EAttribute, the feature will be unset

=== Implementing Rule Classes ===

Rule classes must implement IRule. It is recommended the rule classes extend ac.soton.eventb.emf.diagrams.generator#AbstractRule which provides some concise constants for the commonly needed containments and defines some default behaviour (always enabled and dependencies ok). Note that the rule will only be attempted for the type of source element defined in the extension point. However, this could be defined as an abstract base class to allow the rule to operate on several types of element.

A rule has 4 methods:

* boolean enabled (final EventBElement sourceElement)
* boolean dependenciesOK(EventBElement sourceElement,List<GenerationDescriptor> generatedElements)
* boolean fireLate()
* List<GenerationDescriptor> fire(EventBElement sourceElement, List<GenerationDescriptor> generatedElements)

The enabled method can be used to restrict when it applies. More than one rule can be defined for the same kind of element allowing the generation to be decomposed in a maintainable way.

TheDependenciesOK method allows the method to be deferred since the success of rules may depend on what has already been generated. The dependenciesOK method is passed the list of GenerationDescriptors created so far.

The fireLate method forces the rule to be fired when all other rules have been fired. This is usually used when the rules behaviour depends on what other rules have done.

The fire method must return a list of GenerationDescriptors describing what should be generated. The Utility class, Make, provides a convenience method to help construct a GenerationDescriptor from the parent element, the containment feature, the new child and the priority indicator and if needed the editable setting.

Priority may be from 10 to -10, where 1 indicates first in the containment and -10 last in the containment. Elements in the containment that are not (currently) being generated are placed between priorities 10 and 0. Bear in mind that the relative position of different diagrams (extensions)is preserved within each priority band. Also the order of source elements within their containment is preserved within each priority band.

1 2 3 4 5 6 7 8 9 10 <other content> 0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10

For example, a basic type invariant that doesn't depend on other variables might be placed at position 1 whereas a theorem or invariant included purely for proof purposes might be placed at position -10.

A current limitation of the priority scheme is that there are a limited number of priorities. For example, this could be a problem if a rule needs to calculate positions of each element within a collection based on dependencies of the element instance.

In most cases the generated element should be set as read-only (the default). In this case the element will be deleted and re-generated on each invocation of the generator. The should not change any attributes of the element nor add to its children. In some case, however, it is necessary to generate an element whose contents may be modified by the user. To do this set the editable parameter of the Generation Descriptor. In this case the generated element will not be deleted when the generator is next invoked. The rule must take care not to return another Generation Descriptor if the element has already been generated. It should look for a suitable generated element (to use for adding further generated chldren etc.) and only generate a new one if it doesn't exist.

Where a tree structure is entirely generated within one rule firing (e.g. an event with guards and actions) it is more efficient to construct the entire event and return a single Generation Descriptor that adds that event. It is also possible to do this by returning separate Generation Descriptors to add the event and each guard and action individually.

A typical line from a rule class might look like this:
ret.add(Make.descriptor(machine,invariants,Make.invariant("myInvariantName", "myVar >0","my comment"),10));
where,
ret is the list to be returned and machine is the parent element containing the invariants to be added to.

Generic Event-B EMF extensions

2020-05-30T08:05:52Z

Colin: /* Contributing new EMF element types to the Navigator view */

==Modelling==

==Persistence==

==Navigator==

This section describes how to extend the Event-B Navigator to support Event-B EMF extensions.

===Contributing new EMF element types to the Navigator view===

If the EMF element types are contained in a new file type, declare the new file extension using the extension point:

ac.soton.eventb.emf.core.extension.navigator.emfFileExtensions

This tells the extensions plugin to adapt the emf contents of those files to be shown in the Navigator.

To ensure the EMF elements are labeled and imaged correctly in the Navigator, declare the adapter factory using the extension point:

ac.soton.eventb.emf.core.extension.navigator.adapterFactories

(Note - use the adapter factory generated by the EMF genmodel in the edit plugin).

==Refinement==

[THIS SECTION NEEDS REVIEW AND UPDATE]

The Rodin platform provides an extension point for contributing behaviour to the 'Refine' action.
For Serialised Event-B EMF extensions, an abstract, reflective refinement contributor class is provided to simplify the task of making a refinement.

The class is:
ac.soton.eventb.emf.core.extension.navigator.refiner$AbstractExtensionRefiner which implements IRefinementParticipant.

The class should be extended by a client plug-in and the client's class should be registered as a Refinement Participant using the relevant Rodin extension point
The client class must implement the method getExtensionID() to return the relevant Extension ID string that identifies such extensions.
The client class may override populateReferenceMap(Map<EReference,Boolean>) to add the EReference Features that need to be dealt with, defining which ones are back references to the corresponding abstract element (put true in map) and which ones should reference the corresponding element in the copy (put false in map).
The client class may also override populateFilterByTypeList(List<EClass>) to add the EClass of any types of element that should not be copied into the refinement.

The generic refiner class works as follows:
* All serialised extensions of the given Extension ID in the Rodin resource are loaded
* Each one is deep cloned using the Ecore copier utility
* The contents of the clone extension are then searched for any elements of the EClasses in the client supplied list to be filtered. Such elements are deleted from the clone.
* The contents of the clone extension are then searched for elements that own one of the client supplied EReferences.
* For each reference, the reference is either set to reference the corresponding source abstract element or copied so that it corresponds to the abstract reference

==Diagrams==

==Generator==

[THIS SECTION NEEDS REVIEW AND UPDATE -
Note: The generator is now based on a more generic EMF translator: https://github.com/eventB-Soton/EMF_Translator
It is adapted to Event-B : https://github.com/eventB-Soton/EventB_Translator_Support
There is a documentation plugin in the EMF translator source code that describes the necessary extension points and how to contribute a specific translation.]

A framework to support the implementation of generators is provided. The framework is designed to support the generation of standard Event-B models from higher-level model extensions that are based on the Event-B EMF modelling extensions framework.

The Generator framework provides:

* A toolbar button to initiate the generation
* Generic code to remove previously generated elements
* Generic code to organise the incorporation of newly generated elements
* Utilities to aid the creation of new elements
* An abstract basis for client defined rules
* An extension point for clients to declare generators and generation rules

The client rules return generation descriptors (rather than modifying the target model directly). The framework takes care of updating the model (within the clients Transactional Editing Domain) provided the generation completes successfully. This ensures that the model is not left in an inconsistent state should the generation fail. The generation descriptors allow the client to specify where the new element should be contained and a priority which will be used to influence the placement of the new element within the containment ordering.

To define a particular generator a client should:

* Define an extension of org.eclipse.ui.handlers to enable the generate command when the activePartID is their Editor (see [[Defining a generator handler]])
* Define an extension of ac.soton.eventb.emf.diagrams.generator.rule to make the generator framework aware of your generator and its rule classes.
* Implement your rule classes

=== Generation Descriptors ===

Each rule should return a collection of one or more Generation Descriptors. Generation Descriptors have the following fields which are explained in this section.

* EventBElement parent;
* EStructuralFeature feature;
* Object value;
* Integer priority;
* Boolean editable;
* Boolean remove;

The feature of the parent will be changed in the following ways:

If remove is false:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be added to the containment in a position according to the priority
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be added to the reference in a position according to the priority
* 3) If the feature is an EAttribute and the value is of the correct type, the feature will be set to the value

Priority can be used to control the relative position of the generated elements
* 1 - must come first
* 10 - not important
* ---user entered items---
* 0 must come after user entered items
* -10 must come last

Editable - this affects read-only status of the generated element and whether or not it will be preserved or re-generated in a subsequent generation.
* false - the element is set as read-only (the user cannot change its attributes nor add/remove children), any existing copy of the element will be deleted and re-generated at each re-generation
* true - the element is not read-only and will not be deleted before re-generation. (N.B. It is the responsibility of the client rules to check whether this element already exists and only only generate a new one if it does not)

If remove is true:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be deleted from the containment
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be removed from the reference
* 3) If the feature is an EAttribute, the feature will be unset

=== Implementing Rule Classes ===

Rule classes must implement IRule. It is recommended the rule classes extend ac.soton.eventb.emf.diagrams.generator#AbstractRule which provides some concise constants for the commonly needed containments and defines some default behaviour (always enabled and dependencies ok). Note that the rule will only be attempted for the type of source element defined in the extension point. However, this could be defined as an abstract base class to allow the rule to operate on several types of element.

A rule has 4 methods:

* boolean enabled (final EventBElement sourceElement)
* boolean dependenciesOK(EventBElement sourceElement,List<GenerationDescriptor> generatedElements)
* boolean fireLate()
* List<GenerationDescriptor> fire(EventBElement sourceElement, List<GenerationDescriptor> generatedElements)

The enabled method can be used to restrict when it applies. More than one rule can be defined for the same kind of element allowing the generation to be decomposed in a maintainable way.

TheDependenciesOK method allows the method to be deferred since the success of rules may depend on what has already been generated. The dependenciesOK method is passed the list of GenerationDescriptors created so far.

The fireLate method forces the rule to be fired when all other rules have been fired. This is usually used when the rules behaviour depends on what other rules have done.

The fire method must return a list of GenerationDescriptors describing what should be generated. The Utility class, Make, provides a convenience method to help construct a GenerationDescriptor from the parent element, the containment feature, the new child and the priority indicator and if needed the editable setting.

Priority may be from 10 to -10, where 1 indicates first in the containment and -10 last in the containment. Elements in the containment that are not (currently) being generated are placed between priorities 10 and 0. Bear in mind that the relative position of different diagrams (extensions)is preserved within each priority band. Also the order of source elements within their containment is preserved within each priority band.

1 2 3 4 5 6 7 8 9 10 <other content> 0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10

For example, a basic type invariant that doesn't depend on other variables might be placed at position 1 whereas a theorem or invariant included purely for proof purposes might be placed at position -10.

A current limitation of the priority scheme is that there are a limited number of priorities. For example, this could be a problem if a rule needs to calculate positions of each element within a collection based on dependencies of the element instance.

In most cases the generated element should be set as read-only (the default). In this case the element will be deleted and re-generated on each invocation of the generator. The should not change any attributes of the element nor add to its children. In some case, however, it is necessary to generate an element whose contents may be modified by the user. To do this set the editable parameter of the Generation Descriptor. In this case the generated element will not be deleted when the generator is next invoked. The rule must take care not to return another Generation Descriptor if the element has already been generated. It should look for a suitable generated element (to use for adding further generated chldren etc.) and only generate a new one if it doesn't exist.

Where a tree structure is entirely generated within one rule firing (e.g. an event with guards and actions) it is more efficient to construct the entire event and return a single Generation Descriptor that adds that event. It is also possible to do this by returning separate Generation Descriptors to add the event and each guard and action individually.

A typical line from a rule class might look like this:
ret.add(Make.descriptor(machine,invariants,Make.invariant("myInvariantName", "myVar >0","my comment"),10));
where,
ret is the list to be returned and machine is the parent element containing the invariants to be added to.

Generic Event-B EMF extensions

2020-05-30T07:58:55Z

Colin: /* Navigator */

==Modelling==

==Persistence==

==Navigator==

This section describes how to extend the Event-B Navigator to support Event-B EMF extensions.

===Contributing new EMF element types to the Navigator view===

If the EMF element types are contained in a new file type, declare the new file extension using the extension point:

ac.soton.eventb.emf.core.extension.navigator.emfFileExtensions

To ensure the EMF elements are shown correctly in the Navigator, declare the adapter factory using the extension point:

ac.soton.eventb.emf.core.extension.navigator.adapterFactories

(Note - the adapter factory is the one generated by the EMF genmodel in the edit plugin).

==Refinement==

[THIS SECTION NEEDS REVIEW AND UPDATE]

The Rodin platform provides an extension point for contributing behaviour to the 'Refine' action.
For Serialised Event-B EMF extensions, an abstract, reflective refinement contributor class is provided to simplify the task of making a refinement.

The class is:
ac.soton.eventb.emf.core.extension.navigator.refiner$AbstractExtensionRefiner which implements IRefinementParticipant.

The class should be extended by a client plug-in and the client's class should be registered as a Refinement Participant using the relevant Rodin extension point
The client class must implement the method getExtensionID() to return the relevant Extension ID string that identifies such extensions.
The client class may override populateReferenceMap(Map<EReference,Boolean>) to add the EReference Features that need to be dealt with, defining which ones are back references to the corresponding abstract element (put true in map) and which ones should reference the corresponding element in the copy (put false in map).
The client class may also override populateFilterByTypeList(List<EClass>) to add the EClass of any types of element that should not be copied into the refinement.

The generic refiner class works as follows:
* All serialised extensions of the given Extension ID in the Rodin resource are loaded
* Each one is deep cloned using the Ecore copier utility
* The contents of the clone extension are then searched for any elements of the EClasses in the client supplied list to be filtered. Such elements are deleted from the clone.
* The contents of the clone extension are then searched for elements that own one of the client supplied EReferences.
* For each reference, the reference is either set to reference the corresponding source abstract element or copied so that it corresponds to the abstract reference

==Diagrams==

==Generator==

[THIS SECTION NEEDS REVIEW AND UPDATE -
Note: The generator is now based on a more generic EMF translator: https://github.com/eventB-Soton/EMF_Translator
It is adapted to Event-B : https://github.com/eventB-Soton/EventB_Translator_Support
There is a documentation plugin in the EMF translator source code that describes the necessary extension points and how to contribute a specific translation.]

A framework to support the implementation of generators is provided. The framework is designed to support the generation of standard Event-B models from higher-level model extensions that are based on the Event-B EMF modelling extensions framework.

The Generator framework provides:

* A toolbar button to initiate the generation
* Generic code to remove previously generated elements
* Generic code to organise the incorporation of newly generated elements
* Utilities to aid the creation of new elements
* An abstract basis for client defined rules
* An extension point for clients to declare generators and generation rules

The client rules return generation descriptors (rather than modifying the target model directly). The framework takes care of updating the model (within the clients Transactional Editing Domain) provided the generation completes successfully. This ensures that the model is not left in an inconsistent state should the generation fail. The generation descriptors allow the client to specify where the new element should be contained and a priority which will be used to influence the placement of the new element within the containment ordering.

To define a particular generator a client should:

* Define an extension of org.eclipse.ui.handlers to enable the generate command when the activePartID is their Editor (see [[Defining a generator handler]])
* Define an extension of ac.soton.eventb.emf.diagrams.generator.rule to make the generator framework aware of your generator and its rule classes.
* Implement your rule classes

=== Generation Descriptors ===

Each rule should return a collection of one or more Generation Descriptors. Generation Descriptors have the following fields which are explained in this section.

* EventBElement parent;
* EStructuralFeature feature;
* Object value;
* Integer priority;
* Boolean editable;
* Boolean remove;

The feature of the parent will be changed in the following ways:

If remove is false:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be added to the containment in a position according to the priority
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be added to the reference in a position according to the priority
* 3) If the feature is an EAttribute and the value is of the correct type, the feature will be set to the value

Priority can be used to control the relative position of the generated elements
* 1 - must come first
* 10 - not important
* ---user entered items---
* 0 must come after user entered items
* -10 must come last

Editable - this affects read-only status of the generated element and whether or not it will be preserved or re-generated in a subsequent generation.
* false - the element is set as read-only (the user cannot change its attributes nor add/remove children), any existing copy of the element will be deleted and re-generated at each re-generation
* true - the element is not read-only and will not be deleted before re-generation. (N.B. It is the responsibility of the client rules to check whether this element already exists and only only generate a new one if it does not)

If remove is true:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be deleted from the containment
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be removed from the reference
* 3) If the feature is an EAttribute, the feature will be unset

=== Implementing Rule Classes ===

Rule classes must implement IRule. It is recommended the rule classes extend ac.soton.eventb.emf.diagrams.generator#AbstractRule which provides some concise constants for the commonly needed containments and defines some default behaviour (always enabled and dependencies ok). Note that the rule will only be attempted for the type of source element defined in the extension point. However, this could be defined as an abstract base class to allow the rule to operate on several types of element.

A rule has 4 methods:

* boolean enabled (final EventBElement sourceElement)
* boolean dependenciesOK(EventBElement sourceElement,List<GenerationDescriptor> generatedElements)
* boolean fireLate()
* List<GenerationDescriptor> fire(EventBElement sourceElement, List<GenerationDescriptor> generatedElements)

The enabled method can be used to restrict when it applies. More than one rule can be defined for the same kind of element allowing the generation to be decomposed in a maintainable way.

TheDependenciesOK method allows the method to be deferred since the success of rules may depend on what has already been generated. The dependenciesOK method is passed the list of GenerationDescriptors created so far.

The fireLate method forces the rule to be fired when all other rules have been fired. This is usually used when the rules behaviour depends on what other rules have done.

The fire method must return a list of GenerationDescriptors describing what should be generated. The Utility class, Make, provides a convenience method to help construct a GenerationDescriptor from the parent element, the containment feature, the new child and the priority indicator and if needed the editable setting.

Priority may be from 10 to -10, where 1 indicates first in the containment and -10 last in the containment. Elements in the containment that are not (currently) being generated are placed between priorities 10 and 0. Bear in mind that the relative position of different diagrams (extensions)is preserved within each priority band. Also the order of source elements within their containment is preserved within each priority band.

1 2 3 4 5 6 7 8 9 10 <other content> 0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10

For example, a basic type invariant that doesn't depend on other variables might be placed at position 1 whereas a theorem or invariant included purely for proof purposes might be placed at position -10.

A current limitation of the priority scheme is that there are a limited number of priorities. For example, this could be a problem if a rule needs to calculate positions of each element within a collection based on dependencies of the element instance.

In most cases the generated element should be set as read-only (the default). In this case the element will be deleted and re-generated on each invocation of the generator. The should not change any attributes of the element nor add to its children. In some case, however, it is necessary to generate an element whose contents may be modified by the user. To do this set the editable parameter of the Generation Descriptor. In this case the generated element will not be deleted when the generator is next invoked. The rule must take care not to return another Generation Descriptor if the element has already been generated. It should look for a suitable generated element (to use for adding further generated chldren etc.) and only generate a new one if it doesn't exist.

Where a tree structure is entirely generated within one rule firing (e.g. an event with guards and actions) it is more efficient to construct the entire event and return a single Generation Descriptor that adds that event. It is also possible to do this by returning separate Generation Descriptors to add the event and each guard and action individually.

A typical line from a rule class might look like this:
ret.add(Make.descriptor(machine,invariants,Make.invariant("myInvariantName", "myVar >0","my comment"),10));
where,
ret is the list to be returned and machine is the parent element containing the invariants to be added to.

Generic Event-B EMF extensions

2020-05-30T06:54:10Z

Colin: /* Generator */

==Modelling==

==Persistence==

==Navigator==

==Refinement==

[THIS SECTION NEEDS REVIEW AND UPDATE]

The Rodin platform provides an extension point for contributing behaviour to the 'Refine' action.
For Serialised Event-B EMF extensions, an abstract, reflective refinement contributor class is provided to simplify the task of making a refinement.

The class is:
ac.soton.eventb.emf.core.extension.navigator.refiner$AbstractExtensionRefiner which implements IRefinementParticipant.

The class should be extended by a client plug-in and the client's class should be registered as a Refinement Participant using the relevant Rodin extension point
The client class must implement the method getExtensionID() to return the relevant Extension ID string that identifies such extensions.
The client class may override populateReferenceMap(Map<EReference,Boolean>) to add the EReference Features that need to be dealt with, defining which ones are back references to the corresponding abstract element (put true in map) and which ones should reference the corresponding element in the copy (put false in map).
The client class may also override populateFilterByTypeList(List<EClass>) to add the EClass of any types of element that should not be copied into the refinement.

The generic refiner class works as follows:
* All serialised extensions of the given Extension ID in the Rodin resource are loaded
* Each one is deep cloned using the Ecore copier utility
* The contents of the clone extension are then searched for any elements of the EClasses in the client supplied list to be filtered. Such elements are deleted from the clone.
* The contents of the clone extension are then searched for elements that own one of the client supplied EReferences.
* For each reference, the reference is either set to reference the corresponding source abstract element or copied so that it corresponds to the abstract reference

==Diagrams==

==Generator==

[THIS SECTION NEEDS REVIEW AND UPDATE -
Note: The generator is now based on a more generic EMF translator: https://github.com/eventB-Soton/EMF_Translator
It is adapted to Event-B : https://github.com/eventB-Soton/EventB_Translator_Support
There is a documentation plugin in the EMF translator source code that describes the necessary extension points and how to contribute a specific translation.]

A framework to support the implementation of generators is provided. The framework is designed to support the generation of standard Event-B models from higher-level model extensions that are based on the Event-B EMF modelling extensions framework.

The Generator framework provides:

* A toolbar button to initiate the generation
* Generic code to remove previously generated elements
* Generic code to organise the incorporation of newly generated elements
* Utilities to aid the creation of new elements
* An abstract basis for client defined rules
* An extension point for clients to declare generators and generation rules

The client rules return generation descriptors (rather than modifying the target model directly). The framework takes care of updating the model (within the clients Transactional Editing Domain) provided the generation completes successfully. This ensures that the model is not left in an inconsistent state should the generation fail. The generation descriptors allow the client to specify where the new element should be contained and a priority which will be used to influence the placement of the new element within the containment ordering.

To define a particular generator a client should:

* Define an extension of org.eclipse.ui.handlers to enable the generate command when the activePartID is their Editor (see [[Defining a generator handler]])
* Define an extension of ac.soton.eventb.emf.diagrams.generator.rule to make the generator framework aware of your generator and its rule classes.
* Implement your rule classes

=== Generation Descriptors ===

Each rule should return a collection of one or more Generation Descriptors. Generation Descriptors have the following fields which are explained in this section.

* EventBElement parent;
* EStructuralFeature feature;
* Object value;
* Integer priority;
* Boolean editable;
* Boolean remove;

The feature of the parent will be changed in the following ways:

If remove is false:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be added to the containment in a position according to the priority
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be added to the reference in a position according to the priority
* 3) If the feature is an EAttribute and the value is of the correct type, the feature will be set to the value

Priority can be used to control the relative position of the generated elements
* 1 - must come first
* 10 - not important
* ---user entered items---
* 0 must come after user entered items
* -10 must come last

Editable - this affects read-only status of the generated element and whether or not it will be preserved or re-generated in a subsequent generation.
* false - the element is set as read-only (the user cannot change its attributes nor add/remove children), any existing copy of the element will be deleted and re-generated at each re-generation
* true - the element is not read-only and will not be deleted before re-generation. (N.B. It is the responsibility of the client rules to check whether this element already exists and only only generate a new one if it does not)

If remove is true:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be deleted from the containment
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be removed from the reference
* 3) If the feature is an EAttribute, the feature will be unset

=== Implementing Rule Classes ===

Rule classes must implement IRule. It is recommended the rule classes extend ac.soton.eventb.emf.diagrams.generator#AbstractRule which provides some concise constants for the commonly needed containments and defines some default behaviour (always enabled and dependencies ok). Note that the rule will only be attempted for the type of source element defined in the extension point. However, this could be defined as an abstract base class to allow the rule to operate on several types of element.

A rule has 4 methods:

* boolean enabled (final EventBElement sourceElement)
* boolean dependenciesOK(EventBElement sourceElement,List<GenerationDescriptor> generatedElements)
* boolean fireLate()
* List<GenerationDescriptor> fire(EventBElement sourceElement, List<GenerationDescriptor> generatedElements)

The enabled method can be used to restrict when it applies. More than one rule can be defined for the same kind of element allowing the generation to be decomposed in a maintainable way.

TheDependenciesOK method allows the method to be deferred since the success of rules may depend on what has already been generated. The dependenciesOK method is passed the list of GenerationDescriptors created so far.

The fireLate method forces the rule to be fired when all other rules have been fired. This is usually used when the rules behaviour depends on what other rules have done.

The fire method must return a list of GenerationDescriptors describing what should be generated. The Utility class, Make, provides a convenience method to help construct a GenerationDescriptor from the parent element, the containment feature, the new child and the priority indicator and if needed the editable setting.

Priority may be from 10 to -10, where 1 indicates first in the containment and -10 last in the containment. Elements in the containment that are not (currently) being generated are placed between priorities 10 and 0. Bear in mind that the relative position of different diagrams (extensions)is preserved within each priority band. Also the order of source elements within their containment is preserved within each priority band.

1 2 3 4 5 6 7 8 9 10 <other content> 0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10

For example, a basic type invariant that doesn't depend on other variables might be placed at position 1 whereas a theorem or invariant included purely for proof purposes might be placed at position -10.

A current limitation of the priority scheme is that there are a limited number of priorities. For example, this could be a problem if a rule needs to calculate positions of each element within a collection based on dependencies of the element instance.

In most cases the generated element should be set as read-only (the default). In this case the element will be deleted and re-generated on each invocation of the generator. The should not change any attributes of the element nor add to its children. In some case, however, it is necessary to generate an element whose contents may be modified by the user. To do this set the editable parameter of the Generation Descriptor. In this case the generated element will not be deleted when the generator is next invoked. The rule must take care not to return another Generation Descriptor if the element has already been generated. It should look for a suitable generated element (to use for adding further generated chldren etc.) and only generate a new one if it doesn't exist.

Where a tree structure is entirely generated within one rule firing (e.g. an event with guards and actions) it is more efficient to construct the entire event and return a single Generation Descriptor that adds that event. It is also possible to do this by returning separate Generation Descriptors to add the event and each guard and action individually.

A typical line from a rule class might look like this:
ret.add(Make.descriptor(machine,invariants,Make.invariant("myInvariantName", "myVar >0","my comment"),10));
where,
ret is the list to be returned and machine is the parent element containing the invariants to be added to.

Generic Event-B EMF extensions

2020-05-30T06:48:05Z

Colin: /* Refinement */

==Modelling==

==Persistence==

==Navigator==

==Refinement==

[THIS SECTION NEEDS REVIEW AND UPDATE]

The Rodin platform provides an extension point for contributing behaviour to the 'Refine' action.
For Serialised Event-B EMF extensions, an abstract, reflective refinement contributor class is provided to simplify the task of making a refinement.

The class is:
ac.soton.eventb.emf.core.extension.navigator.refiner$AbstractExtensionRefiner which implements IRefinementParticipant.

The class should be extended by a client plug-in and the client's class should be registered as a Refinement Participant using the relevant Rodin extension point
The client class must implement the method getExtensionID() to return the relevant Extension ID string that identifies such extensions.
The client class may override populateReferenceMap(Map<EReference,Boolean>) to add the EReference Features that need to be dealt with, defining which ones are back references to the corresponding abstract element (put true in map) and which ones should reference the corresponding element in the copy (put false in map).
The client class may also override populateFilterByTypeList(List<EClass>) to add the EClass of any types of element that should not be copied into the refinement.

The generic refiner class works as follows:
* All serialised extensions of the given Extension ID in the Rodin resource are loaded
* Each one is deep cloned using the Ecore copier utility
* The contents of the clone extension are then searched for any elements of the EClasses in the client supplied list to be filtered. Such elements are deleted from the clone.
* The contents of the clone extension are then searched for elements that own one of the client supplied EReferences.
* For each reference, the reference is either set to reference the corresponding source abstract element or copied so that it corresponds to the abstract reference

==Diagrams==

==Generator==

A framework to support the implementation of generators is provided. The framework is designed to support the generation of standard Event-B models from higher-level model extensions that are based on the Event-B EMF modelling extensions framework.

The Generator framework provides:

* A toolbar button to initiate the generation
* Generic code to remove previously generated elements
* Generic code to organise the incorporation of newly generated elements
* Utilities to aid the creation of new elements
* An abstract basis for client defined rules
* An extension point for clients to declare generators and generation rules

The client rules return generation descriptors (rather than modifying the target model directly). The framework takes care of updating the model (within the clients Transactional Editing Domain) provided the generation completes successfully. This ensures that the model is not left in an inconsistent state should the generation fail. The generation descriptors allow the client to specify where the new element should be contained and a priority which will be used to influence the placement of the new element within the containment ordering.

To define a particular generator a client should:

* Define an extension of org.eclipse.ui.handlers to enable the generate command when the activePartID is their Editor (see [[Defining a generator handler]])
* Define an extension of ac.soton.eventb.emf.diagrams.generator.rule to make the generator framework aware of your generator and its rule classes.
* Implement your rule classes

=== Generation Descriptors ===

Each rule should return a collection of one or more Generation Descriptors. Generation Descriptors have the following fields which are explained in this section.

* EventBElement parent;
* EStructuralFeature feature;
* Object value;
* Integer priority;
* Boolean editable;
* Boolean remove;

The feature of the parent will be changed in the following ways:

If remove is false:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be added to the containment in a position according to the priority
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be added to the reference in a position according to the priority
* 3) If the feature is an EAttribute and the value is of the correct type, the feature will be set to the value

Priority can be used to control the relative position of the generated elements
* 1 - must come first
* 10 - not important
* ---user entered items---
* 0 must come after user entered items
* -10 must come last

Editable - this affects read-only status of the generated element and whether or not it will be preserved or re-generated in a subsequent generation.
* false - the element is set as read-only (the user cannot change its attributes nor add/remove children), any existing copy of the element will be deleted and re-generated at each re-generation
* true - the element is not read-only and will not be deleted before re-generation. (N.B. It is the responsibility of the client rules to check whether this element already exists and only only generate a new one if it does not)

If remove is true:
* 1) If the feature is a containment and the value is an element of the correct kind, the value will be deleted from the containment
* 2) If the feature is a reference and the value is an element of the correct kind, the value will be removed from the reference
* 3) If the feature is an EAttribute, the feature will be unset

=== Implementing Rule Classes ===

Rule classes must implement IRule. It is recommended the rule classes extend ac.soton.eventb.emf.diagrams.generator#AbstractRule which provides some concise constants for the commonly needed containments and defines some default behaviour (always enabled and dependencies ok). Note that the rule will only be attempted for the type of source element defined in the extension point. However, this could be defined as an abstract base class to allow the rule to operate on several types of element.

A rule has 4 methods:

* boolean enabled (final EventBElement sourceElement)
* boolean dependenciesOK(EventBElement sourceElement,List<GenerationDescriptor> generatedElements)
* boolean fireLate()
* List<GenerationDescriptor> fire(EventBElement sourceElement, List<GenerationDescriptor> generatedElements)

The enabled method can be used to restrict when it applies. More than one rule can be defined for the same kind of element allowing the generation to be decomposed in a maintainable way.

TheDependenciesOK method allows the method to be deferred since the success of rules may depend on what has already been generated. The dependenciesOK method is passed the list of GenerationDescriptors created so far.

The fireLate method forces the rule to be fired when all other rules have been fired. This is usually used when the rules behaviour depends on what other rules have done.

The fire method must return a list of GenerationDescriptors describing what should be generated. The Utility class, Make, provides a convenience method to help construct a GenerationDescriptor from the parent element, the containment feature, the new child and the priority indicator and if needed the editable setting.

Priority may be from 10 to -10, where 1 indicates first in the containment and -10 last in the containment. Elements in the containment that are not (currently) being generated are placed between priorities 10 and 0. Bear in mind that the relative position of different diagrams (extensions)is preserved within each priority band. Also the order of source elements within their containment is preserved within each priority band.

1 2 3 4 5 6 7 8 9 10 <other content> 0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10

For example, a basic type invariant that doesn't depend on other variables might be placed at position 1 whereas a theorem or invariant included purely for proof purposes might be placed at position -10.

A current limitation of the priority scheme is that there are a limited number of priorities. For example, this could be a problem if a rule needs to calculate positions of each element within a collection based on dependencies of the element instance.

In most cases the generated element should be set as read-only (the default). In this case the element will be deleted and re-generated on each invocation of the generator. The should not change any attributes of the element nor add to its children. In some case, however, it is necessary to generate an element whose contents may be modified by the user. To do this set the editable parameter of the Generation Descriptor. In this case the generated element will not be deleted when the generator is next invoked. The rule must take care not to return another Generation Descriptor if the element has already been generated. It should look for a suitable generated element (to use for adding further generated chldren etc.) and only generate a new one if it doesn't exist.

Where a tree structure is entirely generated within one rule firing (e.g. an event with guards and actions) it is more efficient to construct the entire event and return a single Generation Descriptor that adds that event. It is also possible to do this by returning separate Generation Descriptors to add the event and each guard and action individually.

A typical line from a rule class might look like this:
ret.add(Make.descriptor(machine,invariants,Make.invariant("myInvariantName", "myVar >0","my comment"),10));
where,
ret is the list to be returned and machine is the parent element containing the invariants to be added to.

EMF framework for Event-B

2020-05-19T13:04:36Z

Colin: /* Structure Editor */

{{TOCright}}

This page describes the core facilities for loading Rodin Event-B models in EMF and the 'hooks' that are provided for making extensions. Further support for extending the Event-B modelling language is available here: [[Generic Event-B EMF extensions]].

A generic EMF to EMF translator is also available. This can be configured to generate Event-B EMF and is used for some more recent Event-B generators. It will eventually replace the generator that only targets Event-B.
The generic translator can be used between any source-target pair of EMF meta-models. It is described here: [[EMF to EMF model translator]].

===The Eclipse Modeling Framework===

The EMF project is a modeling framework and code generation facility for building tools and other applications based on a structured data model. From a model specification, EMF provides tools and runtime support to produce a set of Java classes for the model, along with a set of adapter classes that enable viewing and command-based editing of the model, and a basic editor.

===An EMF Meta-Model of Event-B===

The Event-B meta-model defines the structure of Event-B projects. The model is structured into three packages for clarity. The core package contains a structure of abstract meta-classes so that models can be treated generically as far as possible. The core package also contains mechanisms to handle extensions provided by other plug-ins and a meta-class to model entire projects. There are two sub-packages, contained with the core package, for Machine and Context. Note, that the ''EventB'' prefix is used to indicate that a meta-class is abstract (i.e. cannot be instantiated except via one of its subclasses).

====Abstract Basis====
The meta-model is built upon a structure of abstract meta-classes. (Abstract meta-classes are ones that cannot be directly instantiated. Their instances are always instances of one of their concrete sub-meta-classes). These abstract meta-classes are useful because they enable a feature to be defined once in the meta-model and be used, via inheritance, by many concrete meta-classes. Apart from making it easier to maintain the meta-model, this makes it possible to write code that is more generic, since it can work on features without knowing which concrete meta-class the instance it is working on belongs to. To easily distinguish abstract meta-classes from concrete ones, we prefix abstract meta-classes with ''EventB''. For abstract classes, we also follow the convention of including within the name, all the features that are inherited by that meta-class. For example, ''EventBNamedCommentedElement'' inherits from ''EventBCommentedElement'' and from ''EventBNamed''. The abstract meta-classes which are to be used to define concrete meta-classes are arranged in a hierarchy. Each feature is contained in a meta-class outside of this hierarchy (e.g. ''EventBNamed''). This provides a flexible choice of how to access model objects, either at a point in the hierarchy to generalise over parts of its structure or via the feature containers to generalise over all elements that may own that feature. (Although currently these are equivalent, this may not always be the case).

The root of all meta-classes in the Event-B EMF model is the abstract base class, ''EventBObject'' this provides some convenience methods to access containing or contained elements of a specified type and a method to obtain the URL of an element's package. ''EventBObject'' extends the EMF class, ''EObject'' and provides a collection of ''Annotations''. ''Annotations'' (which are similar to Ecore's ''EAnnotations'' ) give a flexible and efficient way to store information that is not part of the main model. For example this is used to store some information contained in the Rodin database, which must be preserved but is not of interest in the EMF modelling tools.

''EventBElement'' provides a common abstract base class for all EventBObjects that are elements of the model. This meta-class provides extensibility features that are described later.

''EventBCommentedElement'' provides the ability to comment elements. It inherits a string attribute, ''comment'' from ''EventBCommented''. (The use of a separate meta-class, outside the main inheritance hierarchy gives more flexibility for future modifications if other elements need to be commented. Hence if client code refers to comments via ''EventBCommented'' rather than ''EventBCommentedElement'' they will not be affected if, in the future, other elements inherit ''EventBCommented'').

Similarly, ''EventBNamedCommentedElement'' adds the ability to name elements by inheriting a string attribute, ''name'' from ''EventBNamed''. (Currently, a named but not commented element is not provided).

''EventBCommentedExpressionElement'' provides a string attribute, ''expression'' (inherited from ''EventBExpression''), for an Event-B mathematical expression. Note that our current need (Variant) is for expression elements to be commented but not named.

''EventBNamedCommentedComponentElement'' subtypes ''EventBNamedCommentedElement'' to provide a common basis for any components (Machines, Contexts etc.) that are contained in the Event-B Project.

''EventBNamedCommentedPredicateElement'' provides a string attribute, ''predicate'' (inherited from ''EventBPredicate''), for an Event-B mathematical predicate. Note that our current need is for all predicate elements to be commented and named.

''EventBNamedCommentedDerivedPredicateElement'' extends ''EventBNamedCommentedPredicateElement'' and provides a boolean attribute, ''theorem'' (inherited from ''EventBDerived'' to indicate that the predicate is a theorem that should be derived (from previous predicates in the same container).

''EventBNamedCommentedActionElement'' provides a string attribute, ''action'' (inherited from ''EventBAction''), for an Event-B mathematical substitution.

[[File:EMFcore1abstract.gif|EMF model abstract base elements]]

====Extensibility Mechanism====

The Extensibility mechanism caters for extensions (i.e. new elements and/or attributes) that have been defined in the Rodin database. When Rodin does not need to understand the extension, a mechanism is provided to persist the extension as a string attribute in a generic Rodin element. This saves having to define an equivalent Rodin database extension. The extension mechanism can also be used to store temporary volatile modelling data that will not be persisted. The extensions will only be persisted if valid Rodin identifiers are provided.

The extension data is contained by the abstract meta-class ''EventBElement'' and hence can be attached to any Event-B model element. Two mechanisms are provided, one for simple attributes (corresponding to Rodin attribute extensions) and one for extension elements (corresponding to Rodin element extensions).

Attribute extensions are contained in a collection ''attributes''. They utilise an intermediate ''StringToAttributeMapEntry'' class which triggers the EMF generator to provide the collection as a special kind of list that can be accessed also as a map. If persistence is required the map key, contained in the ''StringToAttributeMapEntry'' class, should be a valid Rodin extension id; and the map value should be an ''Attribute'' with ''type'' (an enumeration corresponding to the Rodin attribute types) and ''value'' fields (a java object allowing for different attribute types). This feature is used in the following way:
* if, at load time, a Rodin attribute is found that is not recognised as a known attribute of the current element type, the attribute will be stored in the generic ''attributes'' collection using its type identification as the key. Such unknown attributes will be restored at save time.
* all elements of an unknown extension element are treated in this way.
* if at save time, any extensions are found that do not have a valid Rodin extension identifier as their attribute map ''key'', these will be assumed to be volatile and will be discarded.

Element extensions are represented by a collection, ''extensions'', of a meta-class, ''AbstractExtension'', which has an ''extensionId''. This mechanism can be used in several ways.
A new meta-class can extend the core meta-class AbstractExtension so that it may be added to the 'extensions' containment of any EventBElement. This new meta-class may then be treated in one of the following ways.

* It may be viewed as an extension of the containing parent element so that it contributes new containments to an existing meta-class. To do this it should be given an EAnnotation with source org.eventb.emf.core.ExtendedMetaClasses and references to the extended parent classes should be added to this annotation. For synchronisation, the new extension meta-class should be configured to use the 'ExtensionSynchroniser' from the core's persistence plug-in. (No Rodin element identifier should be given). The children of this extension should specify a new synchroniser that extends 'AbstractExtensionChildSynchroniser' to ensure that loading the corresponding Rodin element constructs the intermediate Extension class.

[[Image:EMFMetaClassextensions.gif]]

* It may be viewed as a child element of the parent. In this case, it should be configured with a synchroniser that extends AbstractSynchroniser.

* If Rodin doesn't need to understand the contents of the extension, the extension element should be configured to use the SerialisedExtensionSynchroniser. In this case the extension will be persisted in EMF XMI format in a single attribute of the generic Rodin Element kind, SerialisedExtension. For example, this mechanism is used for making diagrammatic modelling extension.

The following generic fallback mechanisms are also supported:
* if a synchroniser has not been registered; at load time, unknown Rodin elements will be instantiated as generic ''Extension'' elements and their attributes will be contained in this element's ''attributes'' collection. (Note that the ''Extension'' element could contain further recognised or unrecognised elements, which would be added to it's ''extensions'' collection). At save time, these elements would be converted back to their corresponding Rodin elements using the ''extensionId'' and attribute map ''key'', which are also the Rodin extension identifiers.
* if at save time, any extensions are found that do not have a valid Rodin extension identifier as their ''extensionId'', these will be assumed to be volatile and will be discarded.
Extensions are proxy-resolving so that the possibility of extensions being in separate files is allowed. Of course, they may also be within the same resource.

[[Image:EMFcore2extensions.gif|EMF model, extension mechanism]]

Further support for [[Generic Event-B EMF extensions]] is available.

====Project====

Event-B projects are modelled in the Event-B EMF model. This provides support for tools that can display and/or manipulate the project contents. A ''Project'' contains a collection of components. ''Project'' extends ''EventBNamedCommentedElement''. This allows it to contain extensions and attributes as well as providing it with a name and comment. Since persistence works at the component level, the project containments are 'across-resource'. Hence EMF's support for proxy resolution in containments is utilised for the project level model. (By default, proxy resolution is only provided for reference relationships).

[[Image:EMFcore3project.gif|EMF model of an Event-B Project]]

====References between components ====

Event-B projects contain references between elements that are contained within different components. Serialisation (persistence) is performed on a per component basis and therefore, these references must work between resources. The default mechanism for this in EMF is for the reference to be represented by a proxy, initially, after loading the component. The proxy URI is resolved when the reference is first accessed. Resolving a proxy results in the referenced component being loaded so that its contents are accessible. We wish to support this established kind of behaviour for tools that need to work at a multi-component level.

However, we also wish to support tools that work on a single-component level that may involve editing the references. The user view of a reference is of a text string that contains the name identifier of the referenced element. The user may edit this identifier to a new name that may or may not exist. The edit may be made without attempting to resolve the proxy so that the validity of the reference is not tested. (When the component containing the reference is saved, the Rodin static checker will check that the reference exists and raise an error if it does not).

In order to support these dual access methods, we have implemented the following EMF features:

* The ''name'' attribute of ''EventBNamed'' has been designated as an '''ID'''. This setting enables EMF's facility for using '''Intrinsic IDs''' instead of the default method of indexing collections. As a result of this, proxies are constructed from the URI of the containing resource with the '''fragment''' part being the element name.
* The primary feature for a relationship is an EMF reference whose type is the meta-class of the referenced element (i.e. the normal reference relationship used in EMF models). All such references are multiplicity-many, even if only one reference is ever used.
* Resource URI's are constructed lazily when they are resolved. This means that a new reference can be added with just the name of the referenced element. A dummy URI is used to hold the fragment. When the proxy is resolved, the dummy fields are replaced with valid fields derived from knowledge about the structure of Event-B projects. (For example a refined machine must be in the same project as the referencing machine and must have file name given by the reference and extension "bum".
* In order to avoid resolving proxies unnecessarily, elements that can be referenced have been customised so that their getName() method returns the URI fragment if they are a proxy.
* A derived feature which is a list of the reference names is also provided in each referencing element. This has no storage and is constructed from the URI fragments and returned whenever it is requested (by calling getXXXNames() (where XXX is the name of the primary reference feature). The returned list of names is a notifying list so that it will notify the parent element if any changes are made to it. The notification for changes to these lists performs appropriate changes to the primary references feature. For example, adding a new name to the list will add a proxy to the primary reference feature that consists of a dummy URI with fragment equal to the new name.
* The persistence is customised to serialise the list of reference names and discard the list of proxies. (It may seem perverse, then, that the list of names is derived from the proxies. However, this is necessary since the proxies contain more information in memory when they have been resolved and therefore cannot be derived from just the list of names).
* For convenience a method has been added to EventBObject to return its URI. If the element is a proxy, the proxyURI is returned. Otherwise the URI of the component's resource is returned.

Note that the lazy construction of a URI relies on the root element name being used as the resource name. If the name of the root element is changed, it will change the resource name and break any references to it. (If the element name is changed in an editor that works at a higher level than the resource, the editor should update the references automatically)

====Machine package====

A ''Machine'' inherits from ''EventBNamedCommentedComponentElement'' (so that it can be used in the ''components'' collection of a ''Project''). ''Machines'', refine other machines , see contexts and may contain, variables, invariants, a single variant and events.

[[Image:EMFmachine1.gif|EMF model of a Machine]]

'''Events'''

An ''Event'' contains a refines relationships with other events. It also contains collections of parameters, guards, witnesses, and actions. The enumerated type, ''Convergence'', provides the values for the convergence property of an event.

[[Image:EMFevent1.gif|EMF model of an Event]]

====Context package====

A ''Context'' inherits from ''EventBNamedCommentedComponentElement''. Contexts, extend other contexts and contain sets, constants and axioms.

[[Image:EMFcontext1.gif|EMF model of a Context]]

===Persistence===
The Persistence plug-in ''org.eventb.emf.persistence'' overrides EMF's default XMI persistence so that models are serialised in the Rodin Database. The serialisation uses the Rodin API so that it is decoupled from the actual serialisation of the Rodin database. The Persistence API provides methods to open/create Rodin projects, load and unload components (from Rodin Database to cache), save changes, and register listeners to projects and components. An extension point is provided for offering synchronisers for new element kinds (extensions).

Persistence takes a rewriting approach. That is, it is more efficient to clear the contents of a model component (machine or context) and regenerate it than to calculate what has been changed and only save the changes. Rodin uses an internal element naming scheme so that tools can uniquely identify elements even if the user has incorrectly labelled two elements by the same name. (This is different form the name, label or identifier visible to the user). The persistence mechanism preserves and re-uses internal names of elements from before the model was loaded. Elements that have been created in EMF (and therefore don't have an internal name already) are given a unique name using EMF's UUID facility. Since the Rodin naming approach is very different from UUIDs there is very little chance of a UUID clashing with a Rodin generated name. However, if this does happen the persistence will detect it and rename one of the elements using a new UUID. In this case a warning is logged in the Plugin error log.

[[Image:EMFpersistence1UpdateNotification.png|EMF persistence]]

===Event-B Mathematical Language Extension===
Using [[#Extensibility Mechanism|the Extension mechanism]] an EMF extension for the Mathmetical Language of EventB will be created. This means expressions, predicates and substitutions will be available as EMF models too.

As the RodinDB only saves these constructs as plain strings, their EMF representation will be recreated every time a model is loaded. The existing RodinParser in combination with a conversion component will be used for this task.
To avoid unnecessary parsing the creation of these models will be postponed until the models are needed. For example, it will be up to the tool developers to decide when they need a fully resolved structure of predicates. API methods in the [[#Text Tools|Text Tools]] will ease parsing and model construction for tool developers.

===Text Tools===
As several tools based on the EventB meta-model will deal with a textual representation of it, a component called 'Text Tools' will be created. Text Tools will offer an API for basic tasks such as:
* Define a concrete syntax for the structure of machines and contexts
* Conversion from an EventB meta-model to text, i.e., pretty-print with configurable layout
* Parsing of text input which produces an EventB meta-model

'''Structural parsing'''

The Rodin core already provides a parser for expressions, predicates and substitutions. Therefore Text Tools will only provide a parser for the structural parts of the text representation of EventB machines and contexts. This parser will treat expressions, predicates and substitutions as plain strings that are stored in attributes in the meta-model.
As described in section [[#Event-B Mathematical Language Extension|Event-B Mathematical Language Extension]] the full mathematical language will be supported as an extension to the EventB meta-model. Tools that are interested in working on a fully parsed version of an expression, predicate or substitution will be able to use helper methods of the Text Tools API. These helper methods will make use of the existing Rodin parser and convert the resulting AST to the meta-model.

'''Fallback strategy'''

When the user is editing the textual representation of a machine or context the input may contain syntactic errors which prevent converting the parse result into an EMF model. As the user might wish to save the text representation in this syntactically incorrect state, Text Tools will provide a fallback strategy for this case. API methods will be provided to store the plain text into the RodinDB. This plain text will be used as a basis for editing next time the model is loaded via Text Tools.

'''Conflict resolution'''

When Text Tools loads an EventB meta-model from the Rodin Database it will detect any conflicts in the model. Conflicts will occur if other editors, that do not work via Text Tools, have changed the model in the RodinDB after Text Tools has stored a syntactically incorrect version as plain text. In this case the tool that is using Text Tools to load the model will be informed about the conflict and asked to resolve it. Strategies to solve these conflicts could be 'automatic overwriting based on time stamps' or using the editors described in the section [[#Compare/Merge Editor|Compare/Merge Editor]].

===Tools That Will Use the Framework===

The framework described above is not yet available. However, we already plan to use it in some tools.

====Compare/Merge Editor====
In several situations conflicts between different versions of an Event-B model can occur. Often the responsible tool will not be able to resolve these conflicts automatically and user interaction is required. A compare and merge editor for Event-B models will help users to solve these conflicts. This editor will be based on the [http://wiki.eclipse.org/index.php/EMF_Compare EMF Compare] sub-project. It will compare the two conflicting versions and present the differences to the user. This visualization of the model will resemble the [[#Structure Editor|Structure Editor]].

If one of the two versions of the machine/context contains an invalid structure that means it is only available as text, the EMF based Compare/Merge editor cannot be used. A textual Compare/Merge editor will be available as an alternative view (integrated with the EMF Compare/Merge editor). The second view will be based on the [[#Text Editor|Text Editor]].

Usage scenarios are, for example:
* Merging after a conflict between RodinDB and Text Editor (as described in [[#Text Tools|Text Tools]])
* Team-based development, for example, using SVN or CVS
* Comparison of an abstract and a refining machine, highlighting the differences

====Text Editor====
Requests by several users have shown that there is demand for a text editor for EventB models. Based on the EventB meta-model and the [http://www2.informatik.hu-berlin.de/sam/meta-tools/tef/index.html Text Editor Framework], a state-of-the-art text editor will be created.
The editor will make use of [[#Text Tools|Text Tools]] and will provide an extensible set of features, such as (syntactical and semantical) highlighting, code completion, quick navigation and outline view.

The text editor will be available in two forms. A first class Eclipse editor will offer editing of full machines and contexts. In addition a pop-up editor will be created that can be used by other tools to allow their users text editing of sub-components in machines and contexts. An example is the [[#Structure Editor|Structure Editor]], which will offer a pop-up text editor allowing the user to edit a single expression or a compound sub-component such as an event.

====Rose: Structure Editor====
EMF provides support to generate structured (e.g. tree, list, table based) editors for models. An adapted version of these editors will allow users to edit machine and context elements within a structure using menu-guided selections. To allow feature-rich editing of elements containing expressions, predicates and substitutions this editor will use the pop-up variant of the [[#Text Editor|Text Editor]].

====Project Diagram Editor====
A diagrammatic editor will be produced that shows the structure of an Event-B Project in terms of it's Machines and Contexts with their refines, sees and extends relationships. (This will replace the current UML-B package diagram). The Project Diagram editor will be produced using the Graphical Modelling Framework (GMF). It will allow machines and contexts to be created/deleted and their relationships changed. A feature to create a 'starting point' refinement of a machine, will be included.

====[[UML-B]]====
UML-B will be re-implemented as an extension to the Event-B meta-model. The UML-B meta-classes will extend and add to the meta-classes of Event-B. This will provide greater integration between the EMF based Event-B editors and the UML-B diagrammatic editors.

====Refinement Pattern Editor====
The EMF framework will be used to implement the text editor for the Event-B pattern plugin. The syntax of facets - Event-B model templates used to describe patterns - is an extension of the Event-B syntax.

====[[Parallel Composition using Event-B|Shared Event Composition Tool]]====
An editor for composing two machines based on shared events has been developed by Southampton. This tool will be re-implemented to utilise the Event-B EMF framework.

See [[Parallel Composition using Event-B]].

====[[Feature Composition Plug-in|Feature Composition Tool]]====
An editor for composing two machines based on feature selection has been developed by Southampton. The tool (which is already based on EMF) will be re-implemented to utilise the Event-B EMF framework.
See [[Feature Composition Plug-in]].

===Tasklist ===
The following pages contain a list of tasks for the development and use of the EMF framework:
* [[Tasklist for EventB meta model development|Tasklist]]

[[Category:Design proposal]]
.

Template:Main Page/Community

2020-05-19T12:57:11Z

Colin: add postponed Rodin workshop until 2021

<noinclude>
== Displayed as follow on the Main Page ==
<div style="margin:0;width:43%;border:1px solid #AAAAAA;background:#FFFFFF">
</noinclude>
[http://wiki.event-b.org/index.php/Rodin_Workshop_2020 Rodin 2020 (POSTPONED TO 2021) -- The 8th Rodin User and Developer Workshop on 26 May 2020 co-located with ABZ2020.]

[http://research.nii.ac.jp/eventb2016/ The Event-B Day at NII. November 21, 2016. NII, Tokyo, Japan.]

[http://wiki.event-b.org/index.php/Rodin_Workshop_2016 Rodin 2016 Workshop on 23-24 May 2016 co-located with ABZ2016.]

[http://www.cdcc.faw.jku.at/ABZ2016/ ABZ 2016: The 5th International ABZ Conference, for ASM, Alloy, B, TLA, VDM, Z May 23-27, 2016 Linz, Austria]

[http://research.nii.ac.jp/eventb2014/ The Event-B Day at NII. October 31, 2014. NII, Tokyo, Japan.]

[http://wiki.event-b.org/index.php/Rodin_Workshop_2014 Rodin 2014 Workshop on 2+3 June 2014 co-located with ABZ2014.]

[http://link.springer.com/book/10.1007/978-3-642-33170-1/page/1 The DEPLOY book was published by Springer in July 2013: Industrial deployment of system engineering methods providing high dependability and productivity, A. Romanovsky, M. Thomas (Eds). ISBN: 978-3-642-33169-5]

[http://2013.dsn.org/tutorial-a-romanovsky/ Tutorial: ''Correct-by-Construction Development of Dependable Systems'' at the 43rd Annual IEEE/IFIP International Conference on Dependable Systems and Networks. June 24, 2013. Budapest, Hungary]

[http://wiki.event-b.org/index.php/Rodin_Workshop_2013 Rodin 2013 Workshop on 10+11 June 2013.]

[http://www.rodintools.org/tutorial.html ICFEM 2012 Tutorial ''Correct-by-Construction Development of Dependable Systems''. Nov 12, 2012, Kyoto, Japan]

[http://research.nii.ac.jp/eventb2012/ ICFEM 2012 Workshop on the experience of and advances in developing dependable systems in Event-B. Nov 13, 2012, Kyoto, Japan]

[[Rodin Workshop 2012]] - Rodin 2012 Workshop


----

[[Mailing lists]] - Rodin related mailing lists.

[[Rodin Platform Releases]] - Track releases.

[[Bugs and Feature Requests]] - Report a bug or request a new feature.

[[Plug-in_Wishlist|Plug-in Wishlist]]

[http://www.fm4industry.org FAQ about the use and the impact of formal engineering methods in Industry]

----

''Do not hesitate to improve this wiki.'' You may find some help within the following pages:

[[Help:Contents|Wiki Help]] - Some technical documentation about this wiki.

[[EB:VP|Village Pump]] - Ask your questions and keep track of the main wiki events.

[[Special:Recentchanges|Recent Changes]] - Monitor the wiki activity.

[[Test area|Test Area]] - Wiki editing is simple. Try by yourself.
<noinclude>
</div>
[[Category:Main page templates|Community]]
</noinclude>