D45 General Platform Maintenance
Overview
The Rodin platform versions concerned by this deliverable are:
- 2.1(08.02.2011),
- 2.2(01.06.2011),
- 2.2.2(01.08.2011),
- 2.3(04.10.2011),
- 2.4(31.01.2011),
- 2.5(30.04.2011).
This year, the maintenance carried on fixing identified bugs, although an emphasis has been put on correcting usability issues. Indeed, during the meeting in Nice, the WP9 members agreed to refocus on the needed tasks to address some specific bugs and issues reported by DEPLOY partners, and wished resolved by the end of DEPLOY. Thus, no new features were implemented but those appearing in the description of work. The tasks to be performed by the WP9 members were then scheduled, prioritized and regularly updated during the WP9 bi-weekly meetings. The following paragraphs will give an overview of the the work that has been performed concerning maintenance on the existing platform components (i.e. core platform and plug-ins).
See the Release Notes[1] and the SourceForge[1] databases (bugs and feature requests) for details about the previous and upcoming releases of the Rodin platform.
- Core platform maintenance (Thomas Muller)
According to the previously mentionned refocus, the maintenance tasks performed on the core plateform basically aimed to overcome Rodin scalability weaknesses, and the continuous need of seamless proving experience. The performance was enhanced by core implementation and user interface refactorings. The proving usability was enhanced by the possibility to customize, combine, and parameterize tactics and the addition of new inference and rewriting rules.
- TODO An overview of the contribution about Mathematical extensions / Theory Plug-in (Issam Maamria)
- TODO An overview of the contribution about Plug-in Incompatibilities (All partners)
- TODO An overview of the contribution about Modularisation (Alexei Illiasov)
- TODO An overview of the contribution about Decomposition (Renato Silva)
- TODO An overview of the contribution about Team-based Development (Colin Snook, Vitaly Savicks)
- TODO An overview of the contribution about UML-B (Colin Snook, Vitaly Savicks)
- TODO An overview of the contribution about ProR (Michael Jastram)
Motivations
The DEPLOY partners raised issues that appeared mandatory to address by the end of the project. The tasks to solve these issues have been listed and grouped according to their priority. This grouping appears below. The group 1 has the highest priority, the group 2 has an intermediate priority,and the group 3 has the lowest priority. The group 4 concerns topics that could not be ressourced during the lifetime of DEPLOY. Prover Integrity item although not being directly covered, has been partially addressed thanks to Isabelle and SMT integration. Unfortunately, the originally planned export of full proofs and integrity check is beyond the scope of DEPLOY.
| Group 1 (highest priority) | Responsible |
|---|---|
| Performance - Core (large models, etc.) - GUI (incl. prover UI, edition, etc.) |
Systerel |
| Prover Performances - New rewriting rules / inference rules - Automatic tactics (preferences, timeout, etc.) |
Systerel |
| ProB Disprover (incl. counter examples to DLF POs) | Düsseldorf |
| Stability (crash, corruption, etc.) | Systerel |
| Editors | Systerel/Düsseldorf |
| Group 2 | Responsible |
|---|---|
| Prover Performances - SMT provers integration - connection with Isabelle - Mathematical extensions - ProB |
Systerel ETH Zurich Southampton/Systerel Düsseldorf |
| Scalability - Decomposition - Modularisation plug-in - Team-based development |
Southampton Newcastle Southampton |
| Plug-in incompatibilities | Newcastle |
| Model-based testing | Pitesti/Düsseldorf |
| ProR | Düsseldorf |
| Group 3 | Responsible |
|---|---|
| Scalability - Generic instantiation - UML-B maintenance |
Southampton ETH Zurich/Southampton |
| Code Generation | Southampton |
| Group 4 |
|---|
| Prover Integrity |
| Integrity of Code Generation |
Platform maintenance
The platform maintenance, as it can be deduced from the above tables in section Motivations, concerned stability and performance improvement. The prover performance improvement, and the addition of a textual structured editor will be discussed and detailed in separate chapters.
Mathematical extensions / Theory Plug-in
TODO To be completed by Issam Maamria
Plug-in Incompatibilities
TODO To be completed by all partners
Modularisation
TODO To be completed by Alexei Illiasov
Decomposition
TODO To be completed by Renato Silva
Team-based Development
TODO To be completed by Colin Snook, Vitaly Savicks
UML-B
TODO To be completed by Colin Snook, Vitaly Savicks
ProR
TODO To be completed by Michael Jastram
Choices / Decisions
Platform maintenance
SYSTEREL lead a two phase investigation to have a better idea of the work to be done to improve the performance. Each phase being followed by some refactoring of the code. Out of the early investigation, a cause and effect relationship has been found between perfomance loss and the various reported bugs, such as "platform hanging" bugs or even "no more handle" bugs related to the high consumption of graphical elements on Windows platforms. Indeed, it appeared that solving the performance issues sometimes solved induced bugs as well.
Later, a deeper investigation was performed, to indentify and tackle the remaining performance issues. Profiling and code review were the two techniques used. The profiling strategy allowed to get a better localisation of the performance loss in both UI and core code while the code review helped to understand the intrinsic misuses or drawbacks of particular components and/or architectures.
Mathematical extensions / Theory Plug-in
TODO To be completed by Issam Maamria
Plug-in Incompatibilities
TODO To be completed by all partners
Modularisation
TODO To be completed by Alexei Illiasov
Decomposition
TODO To be completed by Renato Silva
Team-based Development
TODO To be completed by Colin Snook, Vitaly Savicks
UML-B
TODO To be completed by Colin Snook, Vitaly Savicks
ProR
TODO To be completed by Michael Jastram
Available Documentation
- Core platform:
- The following pages give useful information about the Rodin platform releases:
- TODO Links for Mathematical extensions / Theory Plug-in
- TODO Links for Plug-in Incompatibilities
- TODO Links for Modularisation
- TODO Links for Decomposition
- TODO Links for Team-based Development
- TODO Links for UML-B
- TODO Links for ProR
Status
Platform maintenance
By the end of the project, there are :
- xx bugs reported and open. All with a priority lower or equal to 5.
- xx feature requests expressed and still open.
Mathematical extensions / Theory Plug-in
TODO To be completed by Issam Maamria
Plug-in Incompatibilities
TODO To be completed by all partners
Modularisation
TODO To be completed by Alexei Illiasov
Decomposition
TODO To be completed by Renato Silva
Team-based Development
TODO To be completed by Colin Snook, Vitaly Savicks
UML-B
TODO To be completed by Colin Snook, Vitaly Savicks
ProR
TODO To be completed by Michael Jastram
References
- ↑ 1.0 1.1 http://wiki.event-b.org/index.php/D32_General_Platform_Maintenance#Available_Documentation Cite error: Invalid
<ref>tag; name "documentation" defined multiple times with different content - ↑ http://wiki.event-b.org/index.php/Rodin_Platform_Releases
- ↑ https://sourceforge.net/tracker/?group_id=108850&atid=651669
- ↑ https://sourceforge.net/tracker/?group_id=108850&atid=651672
