Current Developments: Difference between revisions
imported>Leuschel |
imported>Mathieu mNo edit summary |
||
Line 20: | Line 20: | ||
==== Text Editor ==== | ==== Text Editor ==== | ||
[[Düsseldorf]] has a prototype text-based editor for Event-B (courtesy of Fabian Fritz), but which needs more work to fully integrate into Rodin. | |||
=== Plug-ins === | === Plug-ins === | ||
Line 66: | Line 67: | ||
* a 2D viewer to inspect the state space of the specification | * a 2D viewer to inspect the state space of the specification | ||
== Exploratory Tasks == | == Exploratory Tasks == |
Revision as of 19:36, 27 September 2008
This page sum up the known developments that are being done around or for the Rodin Platform. Please contributes informations about your own development to keep the community informed
Deploy Tasks
The following tasks were planned at some stage of the Deploy project.
Core Platform
New Mathematical Language
Rodin Index Manager
Systerel is in charge of this task.
- For more details on Rodin index design, see Rodin Index Design.
The purpose of the Rodin index manager is to store in a uniform way the entities that are declared in the database together with their occurrences. This central repository of declarations and occurrences will allow for fast implementations of various refactoring mechanisms (such as renaming) and support for searching models or browsing them.
Undo / Redo
Systerel is in charge of this task.
- For more details on Undo/Redo design, see Undo Redo Design.
TODO: describe current work in Undo Redo Design
TODO: add a short summary about current work for undo/redo here
Text Editor
Düsseldorf has a prototype text-based editor for Event-B (courtesy of Fabian Fritz), but which needs more work to fully integrate into Rodin.
Plug-ins
Requirement Management Plug-in
Michael at Düsseldorf is in charge of the Requirements Management Plug-in.
- See also: Requirements Management Plug-in and Requirements Tutorial
This plug-in allows:
- Requirements to be edited in a set of documents (independently from Rodin)
- Requirements to be viewed within Rodin
- Individual Requirements to be linked to individual Event-B-Entities
- A basic completion test to be performed
UML-B Plug-in
Southampton is in charge of UML-B plug-in.
- Support for synchronisation of transitions from different statemachines. This feature will allow two or more transitions in different statemachines to contribute to a single event. This feature is needed because a single event can alter several variables (in this case statemachines) simultaneously.
- Allow user to allocate the name of the 'implicit contextual instance' used in a class. Events and Transitions owned by a class are implicitly acting upon an instance of the class which has formerly been denoted by the reserved word 'self'. This modification allows the modeller to override 'self' (which is now the default name) with any other identifier. This feature is needed to avoid name clashes when synchronising transitions into a single event. It also allows events to be moved between different classes (or outside of all classes) during refinement without creating name clashes.
- Better support for state machine refinement in UML-B. This revision to UML-B allows a statemachine to be recognised as a refinement of another one and to be treated in an appropriate way during translation to Event-B. The states and transitions of a refined statemachine can be elaborated by adding more detailed hierarchical statemachines.
ProB Plug-in
Düsseldorf is in charge of ProB.
- For more details on ProB current developments, see ProB current developments.
Work already performed
We have now ported ProB to work directly on the Rodin AST. Animation is working and the user can now set a limited number of preferences. The model checking feature is now also accessible. It is also possible to create CSP and classical B specification files. These files can be edited with BE4 and animated/model checked with ProB. On the classical B side we have moved to a new, more robust parser (which is now capable of parsing some of the more complicated AtelierB specifications from Siemens).
On the developer side, we have moved to a continuous integration infrastructure using CruiseControl. Rodin is also building from CVS in that infrastructure.
Ongoing and future developments
We are currently developing a new, better user interface. We also plan to support multi-level animation with checking of the gluing invariant.
We have prototypes for several extensions working, but they need to be fully tested and integrated into the plugin:
- an inspector that allows the user to inspect complex predicates (such as invariants or guards) as well as expressions in a tree-like manner
- a graphical animator based on SWT that allows the user to design his/her own animations easily within the tool
- a 2D viewer to inspect the state space of the specification
Exploratory Tasks
One Single View
Maria is in charge of this exploratory work during is internship.
- For more details on Single View Design, see Single View Design.
The goal of this project is to present everything in a single view in Rodin. So the user won't have to switch perspectives.
Others
AnimB
Christophe devotes some of its spare time for this plug-in.
- For more details on AnimB Current Developments, see AnimB Current Developments.
The current developments around the AnimB plug-in encompass the following topics:
- Live animation update
- where the modification of the animated event-B model is instantaneously taken into account by the animator, without the need to restart the animation.
- Collecting history
- The history of the animation will be collected.