ADVANCE Deliverable D3.3
The purpose of this page is to give a common structure and guidelines to collaboratively build the ADVANCE Deliverable D3.3 (Methods and tools for model construction and proof II) which will be delivered to the European Commission at month 24 (2013-09-30). The deliverable will give to the project reviewers some insight on what happened in the work package 3, concerning its 3 main objectives:
- to provide the methodological and tooling means for modelling Systems-of-Systems.
- to provide expert formal proof support to the industrial partners;
- to improve the usability and productivity of the Rodin platform to support larger-scale developments;
- the template of the deliverable is released on 2013-07-16
- the contents are contributed by 2013-08-23
- the draft for internal review is sent on 2013-08-30
- the final deliverable is produced for 2013-09-30
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 second period of the project (Sept 2012-Sept 2013). 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).
To ease the reviewer's reading of the present deliverable, the structure of the document will follow the objectives mentioned in the DoW:
D3.3) Methods and tools for model construction and proof II: This deliverable describes the maintenance actions carried through, together with an update on the progress of automated proof and model checking against plan. Extensions and enhancements to the method documentation and tutorials are also supplied. It also presents the achievements made in the area of the mathematical language and other planned Event-B language extensions and report on the progress of composition / decomposition enhancements against plan. [month 24]
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 / Decisions
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. This paragraph shall also 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.
This paragraph shall give pointers to the available wiki pages or related publications. This documentation may contain:
- 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.
This paragraph shall give an outlook on the current status and the plans for future work. See also the Tool Development Roadmap.
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 2013-09-30, use past, present and future accordingly.
- The dedicated category, [[Category:ADVANCE D3.3 Deliverable]], shall be specified for wiki pages.
- If you intend to use the same reference multiple times, please use the Cite extension .
- By doing so, you will have to add the additional paragraph at the end of your page :
- 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).
- Introduction (Laurent Voisin/Nicolas Beauger)
- General Platform Maintenance
- Core Rodin platform (Laurent Voisin/Nicolas Beauger)
- UML-B Improvements (Colin Snook, Vitaly Savicks)
- ProR (Michael Jastram/Lukas Ladenberger)
- Camille (Ingo Weigelt)
- Improvement of automated proof
- Integrated provers (Laurent Voisin/Nicolas Beauger)
- SMT Provers (Laurent Voisin)
- Model Checking (Michael Leuschel & al.)
- Language extension (Asieh Salehi)
- Model Composition and Decomposition (Asieh Salehi)