User:Pascal/Collections/Deploy Deliverable D23

Introduction

The purpose of this page is to give a common structure and guidelines to collaboratively build the ADVANCE Deliverable D3.2 (Methods and tools for model construction and proof I) which will be delivered to the European Commission at month 10 (31st July 2012). The deliverable will give to the project reviewers some insight on what happened in the work package 3, concerning its 3 main objectives:

1. to provide the methodological and tooling means for modelling Systems-of-Systems.
2. to provide expert formal proof support to the industrial partners;
3. to improve the usability and productivity of the Rodin platform to support larger-scale developments;

Schedule

• the template of the deliverable is released on 01-06-2012
• the contents are contributed by 22-06-2012
• the draft for internal review is sent on 29-06-2012
• the final deliverable is produced for 31-07-2012

Template

For each item covered in this document, a wiki page has been created (see Contents) to give a brief description of the work that was carried on during the first 10 months of the project (Oct 2011-July 2012). The contents of each page should not go deeply into technical details, but should rather look like an executive summary. All details (papers, detailed wiki pages, etc.) should be made available as pointers. Moreover, each contribution shall be quite short (ca. two printed pages).

Direct link with the DoW

To ease the reviewer's reading of the present deliverable, the structure of the document will follow the objectives mentioned in the DoW: D3.2) Methods and tools for model construction and proof I: This deliverable describes the maintenance actions carried through, together with a summary of progress on the improvement of automated proof and model checking. A list of the scalability enhancements achieved so far in the project, together with their expected impact on performance and capacity, is included and validated against the Tool Development Roadmap. Progress of the planned improvements to the existing automated proof tools is described, stating clearly what improvements have been delivered and how the development of longer-term improvements measures against the original plan. Appropriate documentation and tutorials are delivered to describe the methods that will ensure that these improvements can be best used to increase the proportion of automated proofs. Improvements to the ProB model checking tool and associated methods are also described. [month 10]

Overview

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

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 were addressed and what are the main benefits.

Choices / Decisions

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

This paragraph shall give pointers to the available wiki pages or related publications. This documentation may contain:

• Requirements.
• Pre-studies (states of the art, proposals, discussions).
• Technical details (specifications).
• Teaching materials (tutorials).
• User's guides.

A distinction shall be made on the one hand between these different categories, and on the other hand between documentation written for developers and documentation written for end-users.

Planning

This paragraph shall give an outlook on the current status and the plans for future work.

Formatting rules

In order to homogeneize the contributions and to ensure consistent spelling the following formatting rules shall be enforced:

• See §4 of How to Edit Your Input File for LLNCS formatting rules.
• ADVANCE and Rodin shall be typed this way.
• Contractions shall not be used (eg. write "does not" instead of "doesn't", "let us" instead of "let's", etc).
• British english spelling shall be retained.
• "plug-in" shall be preferred to "plugin".
• Remember that the document is dated 31st July 2012, use past, present and future accordingly.
• The dedicated category, [[Category:ADVANCE D3.2 Deliverable]], shall be specified for wiki pages.
• If you intend to use the same reference multiple times, please use the Cite extension [1] that has been installed recently.

By doing so, you will have to add the additional paragraph at the end of your page :

==References==
<references/>

Note that you can add references using the normal wikimedia links as well as using references nevertheless only the latter ones will appear in the references section on the wiki (e.g. all references will appear in the final PDF document whatever their type).

ADVANCE Deliverable

D3.2

Introduction (Laurent Voisin/Thomas Muller)

General Platform Maintenance

• Core Rodin platform (Thomas Muller)
• UML-B Improvements (Colin Snook, Vitaly Savicks)
• Code generation (Andy Edmunds)
• ProR (Michael Jastram/Lukas Ladenberger)
• Camille (Ingo Weigelt)

Improvement of automated proof

• Integrated provers (Laurent Voisin/Thomas Muller)
• SMT Provers (Laurent Voisin)

Language extension(Issam Maamria)

Model Checking(Michael Leuschel & al.)

Model Composition and Decomposition (Renato Silva)