Difference between revisions of "Current Developments"

From Event-B
Jump to navigationJump to search
imported>Mathieu
imported>Mathieu
m (better support for state machine refinement in UML-B + who is in charge)
Line 4: Line 4:
 
The following tasks were planned at some stage of the [[Deploy]] project.
 
The following tasks were planned at some stage of the [[Deploy]] project.
 
=== Rodin Index ===
 
=== Rodin Index ===
 +
[[Systerel]] is in charge of this task.
 
{{details|Rodin Index Design|Rodin index design}}
 
{{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.  
 
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.
 +
 +
* better support for state machine refinement in UML-B.
 +
 +
  
 
== Exploratory tasks ==
 
== Exploratory tasks ==
 
=== One single View ===
 
=== One single View ===
 +
[[Maria]] is in charge of this exploratory work during is internship.
 
{{details|Single View Design|Single View Design}}
 
{{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.
 
The goal of this project is to present everything in a single view in Rodin. So the user won't have to switch perspectives.
 +
  
  
Line 16: Line 29:
  
 
=== AnimB ===
 
=== AnimB ===
 +
[[Christophe]] devotes some of its spare time for this plug-in.
 
{{details|AnimB Current Developments|AnimB Current Developments}}
 
{{details|AnimB Current Developments|AnimB Current Developments}}
 
The current developments around the [[AnimB]] plug-in encompass the following topics:
 
The current developments around the [[AnimB]] plug-in encompass the following topics:
Line 22: Line 36:
 
;Collecting history
 
;Collecting history
 
:The history of the animation will be collected.
 
:The history of the animation will be collected.
 +
 +
  
 
[[Category:Work in progress]]
 
[[Category:Work in progress]]

Revision as of 12:28, 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.

  • better support for state machine refinement in UML-B.


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.