Current Developments: Difference between revisions
imported>Mathieu m red link / TOCright |
imported>Colin |
||
Line 15: | Line 15: | ||
[[Southampton]] is in charge of this plug-in. | [[Southampton]] is in charge of this 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. | ||
* Better support for state machine refinement in UML-B. This is a major addition to UML-B. It allows a statemachine to be recognised as a refinement of another and to be treated in an appropriate way during translation to Event-B. The states of a refined statemachine can be elaborated with contained hierarchical statemachines and transitions can be elaborated within these contained statemachines. | |||
*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 allows | |||
== Exploratory tasks == | == Exploratory tasks == |
Revision as of 12:57, 23 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.
Rodin Index
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.
UML-B plugin
Southampton is in charge of this 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.
- Better support for state machine refinement in UML-B. This is a major addition to UML-B. It allows a statemachine to be recognised as a refinement of another and to be treated in an appropriate way during translation to Event-B. The states of a refined statemachine can be elaborated with contained hierarchical statemachines and transitions can be elaborated within these contained statemachines.
- 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 allows
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.