imported>Colin |
|
| Line 1: |
Line 1: |
| − | {{TOCright}}
| |
| − | 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.
| |
| − | === Rodin Index ===
| |
| − | [[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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | === UML-B plugin ===
| |
| − | [[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.
| |
| − |
| |
| − | == 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.
| |
| − |
| |
| − |
| |
| − |
| |
| − | [[Category:Work in progress]]
| |
