Difference between pages "Current Developments" and "D23 General Platform Maintenance"

From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Mathieu
 
imported>Pascal
 
Line 1: Line 1:
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''
+
= Overview =
 +
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.
 
=== Rodin Index ===
 
{{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.  
 
  
== Exploratory tasks ==
+
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:
=== One single View ===
+
{{SimpleHeader}}
{{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.
+
! 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
 +
|}
  
 +
{{TODO}}
 +
This first paragraph shall identify the involved partners and give an overview of the contribution. In particular, it shall provide answers to the following questions:
  
== Others ==
+
*What are the common denominations?
 +
*Is it a new feature or an improvement?
 +
*What is the main purpose?
 +
*Who was in charge?
 +
*Who was involved?
  
=== AnimB ===
+
= Motivations =
{{details|AnimB Current Developments|AnimB Current Developments}}
+
{{TODO}}  
The current developments around the [[AnimB]] plug-in encompass the following topics:
+
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.  
;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]]
+
= 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.
 +
 
 +
= 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].
 +
 
 +
= Planning =
 +
The ''Rodin Platform Releases'' wiki page lists in particular the upcoming releases and give the scheduled release dates.

Revision as of 17:47, 10 November 2009

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

TODO This first paragraph shall identify the involved partners and give an overview of the contribution. In particular, it shall provide answers to the following questions:

  • What are the common denominations?
  • Is it a new feature or an improvement?
  • What is the main purpose?
  • Who was in charge?
  • Who was involved?

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.

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.
More details are provided in the notes distributed with each release (eg. http://sourceforge.net/project/shownotes.php?release_id=693928).
  • Bugs.
See http://sourceforge.net/tracker/?group_id=108850&atid=651669.
  • Feature requests.
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.