imported>Fabian |
imported>Pascal |
| Line 1: |
Line 1: |
| − | {{TOCright}}
| + | = Overview = |
| − | 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''
| + | The purpose of the platform corrective and evolutive maintenance is to address bugs and feature requests. |
| | | | |
| − | == Deploy Tasks ==
| + | The main evolutions of the Rodin platform are driven by the description of work for the Rodin project and the requirements expressed by industrial WP1 to WP5 partners or by consultants during the lifecycle of the project. |
| − | The following tasks were planned at some stage of the [[Deploy]] project. | |
| − | === Core Platform ===
| |
| − | ==== New Mathematical Language ====
| |
| − | ==== Rodin Index Manager ====
| |
| − | [[Systerel]] is in charge of this task.
| |
| − | {{details|Rodin Index Design|Rodin index design}}
| |
| | | | |
| − | The 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.
| + | Beyond that, any user registered on SourceForge may record any encountered bug on the Rodin platform or request a new feature, using the dedicated [[#Available documentation | trackers]]. Depending on the category, the bug / feature is assigned to the WP9 partner who is in charge of its treatment: |
| | + | {{SimpleHeader}} |
| | + | |- |
| | + | ! scope=col | Category || Partner |
| | + | |- |
| | + | |AnimB || Christophe METAYER |
| | + | |- |
| | + | |B2LaTeX || University of Southampton |
| | + | |- |
| | + | |Decomposition || Systerel |
| | + | |- |
| | + | |Event-B core || Systerel |
| | + | |- |
| | + | |Event-B interface || Systerel |
| | + | |- |
| | + | |Event-B POG || Systerel |
| | + | |- |
| | + | |Event-B provers || Systerel |
| | + | |- |
| | + | |Event-B static checker || Systerel |
| | + | |- |
| | + | |PRO-B || Dusseldorf |
| | + | |- |
| | + | |Renaming || University of Southampton |
| | + | |- |
| | + | |Requirements || Dusseldorf |
| | + | |- |
| | + | |Rodin platform || Systerel |
| | + | |- |
| | + | |Text editor || Dusseldorf |
| | + | |- |
| | + | |U2B || Southampton |
| | + | |} |
| | | | |
| − | ==== Undo / Redo for editors ==== | + | = Motivations = |
| − | {{see also|Undo Redo Design|l1=Undo/Redo design}} | + | {{TODO}} |
| | + | This paragraph shall express the motivation for each tool extension and improvement. More precisely, it shall first indicate the state before the work, the encountered difficulties, and shall highlight the requirements (eg. those of industrial partners). Then, it shall summarize how these requirements are addressed and what are the main benefits. |
| | | | |
| − | [[Systerel]] is in charge of this task.
| + | = Choices / Decisions = |
| | + | {{TODO}} |
| | + | This paragraph shall summarize the decisions (eg. design decisions) and justify them. Thus, it may present the studied solutions, through their main advantages and inconvenients, to legitimate the final choices. |
| | | | |
| − | The goal of this task is to implement an undo/redo feature for editing actions.
| + | Release Policy |
| | | | |
| − | This feature is now coded in CVS and working. It however still needs some improvement or refactoring.
| + | = Available Documentation = |
| | + | The following pages give useful information about the Rodin platform releases: |
| | + | * Release notes. |
| | + | : See [http://wiki.event-b.org/index.php/Rodin_Platform_Releases http://wiki.event-b.org/index.php/Rodin_Platform_Releases]. |
| | + | : More details are provided in the notes distributed with each release (eg. [http://sourceforge.net/project/shownotes.php?release_id=693928 http://sourceforge.net/project/shownotes.php?release_id=693928]). |
| | + | * Bugs. |
| | + | : See [http://sourceforge.net/tracker/?atid=651669&group_id=108850 http://sourceforge.net/tracker/?group_id=108850&atid=651669]. |
| | + | * Feature requests. |
| | + | : See [http://sourceforge.net/tracker/?group_id=108850&atid=651672 http://sourceforge.net/tracker/?group_id=108850&atid=651672]. |
| | | | |
| − | ==== Text Editor ==== | + | = Planning = |
| − | [[Düsseldorf]] has a prototype text-based editor for Event-B (courtesy of [[User:Fabian|Fabian]]). As of end of sempteber 2008, it still needs more work to fully integrate into Rodin.
| + | The ''Rodin Platform Releases'' wiki page lists in particular the upcoming releases and give the scheduled release dates. |
| | | | |
| − | [[Newcastle]] has another text editor based on EMF. Among other things, it defines an EMF model of Event-B machines and contexts. At some point, the editor code is to be split into two plugins - an EMF adapater to rodin and the editor itself. Source code is currently available from [http://iliasov.org/editor-source.zip].
| |
| | | | |
| − | === Plug-ins ===
| + | [[Category:D23 Deliverable]] |
| − | ==== Requirement Management Plug-in ====
| |
| − | [[User:Jastram|Michael]] at [[Düsseldorf]] is in charge of the [[:Category:Requirement Plugin|Requirements Management Plug-in]].
| |
| − | | |
| − | {{See also|ReqsManagement|Requirements Tutorial|l1=Requirements Management Plug-in}}
| |
| − | | |
| − | 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]].
| |
| − | <!-- {{details|ProB current developments|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
| |
| − | | |
| − | ==== B2Latex Plug-in ====
| |
| − | [[Southampton]] is in charge of [[B2Latex]].
| |
| − | | |
| − | Kriangsak Damchoom will update the plug-in to add [[Event Extension|extensions of events]].
| |
| − | | |
| − | == Exploratory Tasks ==
| |
| − | === One Single View ===
| |
| − | [[Maria]] is in charge of this exploratory work during is internship.
| |
| − | {{details|Single View Design|Single View Design}}
| |
| − | The goal of this project is to present everything in a single view in Rodin. So the user won't have to switch perspectives.
| |
| − | | |
| − | | |
| − | | |
| − | == Others ==
| |
| − | | |
| − | === AnimB ===
| |
| − | [[Christophe]] devotes some of its spare time for this plug-in.
| |
| − | {{details|AnimB Current Developments|AnimB Current Developments}}
| |
| − | The current developments around the [[AnimB]] plug-in encompass the following topics:
| |
| − | ;Live animation update
| |
| − | :where the modification of the animated event-B model is instantaneously taken into account by the animator, without the need to restart the animation.
| |
| − | ;Collecting history
| |
| − | :The history of the animation will be collected.
| |
| − | | |
| − | === Team-Based Development ===
| |
| − | | |
| − | ; Usage Scenarios
| |
| − | : In order to understand the problem properly, [http://www.stups.uni-duesseldorf.de/ Düsseldorf] created a number of usage [[Scenarios for Team-based Development]].
| |
| − | : A page as also been opened for [[Scenarios for Merging Proofs|merging proofs scenarios]].
| |
| − | [[Category:Work in progress]] | |
Overview
The purpose of the platform corrective and evolutive maintenance is to address bugs and feature requests.
The main evolutions of the Rodin platform are driven by the description of work for the Rodin project and the requirements expressed by industrial WP1 to WP5 partners or by consultants during the lifecycle of the project.
Beyond that, any user registered on SourceForge may record any encountered bug on the Rodin platform or request a new feature, using the dedicated trackers. Depending on the category, the bug / feature is assigned to the WP9 partner who is in charge of its treatment:
| Category |
Partner
|
| AnimB |
Christophe METAYER
|
| B2LaTeX |
University of Southampton
|
| Decomposition |
Systerel
|
| Event-B core |
Systerel
|
| Event-B interface |
Systerel
|
| Event-B POG |
Systerel
|
| Event-B provers |
Systerel
|
| Event-B static checker |
Systerel
|
| PRO-B |
Dusseldorf
|
| Renaming |
University of Southampton
|
| Requirements |
Dusseldorf
|
| Rodin platform |
Systerel
|
| Text editor |
Dusseldorf
|
| U2B |
Southampton
|
Motivations
TODO
This paragraph shall express the motivation for each tool extension and improvement. More precisely, it shall first indicate the state before the work, the encountered difficulties, and shall highlight the requirements (eg. those of industrial partners). Then, it shall summarize how these requirements are addressed and what are the main benefits.
Choices / Decisions
TODO
This paragraph shall summarize the decisions (eg. design decisions) and justify them. Thus, it may present the studied solutions, through their main advantages and inconvenients, to legitimate the final choices.
Release Policy
Available Documentation
The following pages give useful information about the Rodin platform releases:
- See http://wiki.event-b.org/index.php/Rodin_Platform_Releases.
- More details are provided in the notes distributed with each release (eg. http://sourceforge.net/project/shownotes.php?release_id=693928).
- See http://sourceforge.net/tracker/?group_id=108850&atid=651669.
- See http://sourceforge.net/tracker/?group_id=108850&atid=651672.
Planning
The Rodin Platform Releases wiki page lists in particular the upcoming releases and give the scheduled release dates.
