D45 General Platform Maintenance: Difference between revisions

From Event-B
Jump to navigationJump to search
imported>Tommy
imported>Tommy
Line 31: Line 31:


== Platform maintenance ==
== Platform maintenance ==
The DEPLOY partners raised issues that appeared mandatory to address by the end of the project.
The DEPLOY partners raised issues that appeared mandatory to address by the end of the project. The tasks to address these issues have been listed and grouped according to their priority.
These issues concern the following tasks:
 
{{SimpleHeader}}
{{SimpleHeader}}
|-
|-
! scope=col | Origin || Maintenance Task
! scope=col | Group 1 (highest priority) || Responsible
|-
|-
| DoW / WP1-4 partners || Increase prover efficiency and integrity
|Performance <br /> - Core (large models, etc.) <br /> - GUI (incl. prover UI, edition, etc.) || Systerel
|-
|-
| WP1-4 partners|| Allow better edition
|Prover Performances <br /> - New rewriting rules / inference rules <br /> - Automatic tactics (preferences, import/export, timeout,etc.) || Systerel
|-
|-
| WP1-4 partners|| Increase platform stability
|ProB Disprover (incl. counter examples to deadlock freedom POs) || Düsseldorf
|-
|-
| WP1-4 partners|| Increase platform performance
|Stability (crash, corruption, etc.)  || Systerel
|-
|-
| WP1-4 partners|| Allow to search in goal window <ref>https://sourceforge.net/tracker/?func=detail&atid=651672&aid=3092835&group_id=108850</ref>
|Editors || Systerel/Düsseldorf
|-
|-
| WP1-4 partners|| Allow preferences for the automatic tactics <ref>http://sourceforge.net/tracker/index.php?func=detail&aid=1581775&group_id=108850&atid=651672</ref>
|}
 
{{SimpleHeader}}
|-
! scope=col | Group 2 || Responsible
|-
| Prover Performances <br /> - SMT provers integration <br /> - connection with Isabelle  <br /> - Mathematical extensions <br /> - ProB || <br />Systerel <br /> ETH Zurich <br /> Southampton/Systerel <br /> Düsseldorf
|-
|Scalability <br /> - Decomposition <br /> - Modularisation plug-in <br /> - Team-based development || <br /> Southampton <br /> Newcastle <br /> Southampton
|-
|Plug-in incompatibilities || Newcastle
|-
|Model-based testing || Pitesti/Düsseldorf
|-
|ProR || Düsseldorf
|}
 
{{SimpleHeader}}
|-
! scope=col | Group 3 || Responsible
|-
|Scalability <br /> - Generic instantiation <br /> - UML-B maintenance <br /> || <br />Southampton <br />ETH Zurich/Southampton
|-
|Code Generation || Southampton
|}
 
{{SimpleHeader}}
|-
! scope=col | Group 4 || Responsible
|-
|-
| End Users || Displaying the inherited elements
Prover Integrity ||
Integrity of Code Generation ||
|}
|}
This item will be partially be addressed thanks to Isabelle/SMT integration. But export of full proofs is beyond the scope of DEPLOY.


== Mathematical extensions / Theory Plug-in ==
== Mathematical extensions / Theory Plug-in ==

Revision as of 16:09, 15 November 2011

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

Platform maintenance

The DEPLOY partners raised issues that appeared mandatory to address by the end of the project. The tasks to address these issues have been listed and grouped according to their priority.


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, import/export, timeout,etc.)
Systerel
ProB Disprover (incl. counter examples to deadlock freedom 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


Prover Integrity || Integrity of Code Generation ||
Group 4 Responsible

This item will be partially be addressed thanks to Isabelle/SMT integration. But export of full proofs is beyond the scope of DEPLOY.

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

TODO To be completed by Thomas Muller

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:
  • Release notes[2].
  • Bugs[3].
  • Feature requests[4].
  • 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