Difference between pages "User:Nicolas/Collections/ADVANCE Deliverable D3.4" and "User:Pascal/Collections/Deploy Deliverable D23"

From Event-B
< User:Nicolas(Difference between pages)
Jump to navigationJump to search
imported>Nicolas
 
imported>Pascal
 
Line 1: Line 1:
 
== Introduction ==
 
== Introduction ==
−
The purpose of this page is to give a common structure and guidelines to collaboratively build the ADVANCE Deliverable D3.4 (Methods and tools for model construction and proof III) which will be delivered to the European Commission at month 38 (2014-10-31 {{TODO}}).
+
The purpose of this page is to give a base for the DEPLOY Deliverable D23 (Model Construction and Analysis Tool II).
−
The DOW reads:
 
−
<blockquote>
 
−
This deliverable provides a summary of the improvements made to the Rodin Platform throughout the project. It validates the delivery of improvements to both tools and methods for model construction and proof against the original plan. In addition, it reports on the development of formal design patterns that have arisen from the case studies of WP1 and WP2 and nature and availability of the supporting documentation and tutorials. It also reports on the composition / decomposition cookbook.
 
−
</blockquote>
 
  
−
== Schedule ==
+
The [http://bscw.cs.ncl.ac.uk/bscw/bscw.cgi/d103646/D23_Writing_Plan.pdf D23 Writing Plan] gives a table of contents for this document.
−
*the template of the deliverable is released on 2014-10-06
 
−
*the contents are contributed by 2014-10-22
 
−
*the draft for internal review is sent on 2014-10-24
 
−
*the final deliverable is produced for 2014-10-31
 
  
 
== Template ==
 
== Template ==
−
For each item covered in this document, a wiki page has been created (see [[#Contents | Contents]]) to give a brief description of the work that was carried on during third period of the project (Oct 2013-Nov 2014). 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.
+
For each item covered in this document, a wiki page shall be created (see [[#Contents | Contents]]) to provide a description of work and describe the role of the WP9 partners during the passed year.  
−
'''Moreover, each contribution shall be quite short (ca. two printed pages).'''
 
  
 +
The purpose of the template is to provide a common structure for all of these pages. It takes into consideration the review feedback for the DEPLOY Deliverable D6 (Model Construction and Analysis Tool I).
  
 
=== Overview ===
 
=== Overview ===
Line 21: Line 13:
 
* What are the common denominations?
 
* What are the common denominations?
 
* Is it a new feature or an improvement?  
 
* Is it a new feature or an improvement?  
−
* What is the main purpose?
+
* What are the main purposes?
−
* Who was in charge?  
+
* Who is in charge of the tasks?  
−
* Who was involved?
+
* Who is involved among the academic and industrial partners? Who is involved as developer? Who is involved as user?
  
−
=== Motivations / Decisions ===
+
=== 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.
+
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.
−
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.
+
 
 +
=== 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 ===
 
=== Available Documentation ===
Line 36: Line 30:
 
* Teaching materials (tutorials).
 
* Teaching materials (tutorials).
 
* User's guides.  
 
* 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.
+
A distinction shall be made on the one hand between these different categories, and on the other hand between documentation written for developpers and documentation written for end-users.
  
−
=== Conclusion ===
+
=== Planning ===
−
This paragraph shall give a brief summary about what has been achieved in the topic, and an overview of potential continuations.
+
This paragraph shall give a timeline.
−
See also the [[Tool Development Roadmap]].
+
More precisely, it shall give the current status of the new features (specification, still under development, available prototype, available since release <math>M.m</math>), their current version, describe the tasks which have already been completed and announce planned further work and deadlines (release versions of the Rodin platform).
 +
 
 +
=== Corrective and Evolutive Maintenance ===
 +
This paragraph describes how bugs and feature requests are addressed.
  
 
== Formatting rules ==
 
== Formatting rules ==
 
In order to homogeneize the contributions and to ensure consistent spelling the following formatting rules shall be enforced:
 
In order to homogeneize the contributions and to ensure consistent spelling the following formatting rules shall be enforced:
 
* See §4 of [http://wiki.event-b.org/images/Llncsdoc.pdf How to Edit Your Input File] for LLNCS formatting rules.
 
* See §4 of [http://wiki.event-b.org/images/Llncsdoc.pdf 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).
 
* 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.
 
* British english spelling shall be retained.
 
* "plug-in" shall be preferred to "plugin".
 
* "plug-in" shall be preferred to "plugin".
−
* Remember that the document is dated {{TODO}}, use past, present and future accordingly.
 
−
* The dedicated category, <nowiki>[[Category:ADVANCE D3.4 Deliverable]]</nowiki>, shall be specified for wiki pages.
 
−
* If you intend to use the same reference multiple times, please use the Cite extension [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php].
 
−
: By doing so, you will have to add the additional paragraph at the end of your page :
 
−
==References==
 
−
<nowiki><references/></nowiki>
 
−
: 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).
 
  
 
== Contents ==
 
== Contents ==
−
=== D3.4 ===
+
;Introduction
 +
:[[D23 Introduction]]
 +
 
 +
;General platform maintenance
 +
:[[D23 General platform maintenance]]
 +
 
 +
;UML-B improvements
 +
:[[D23 UML-B]]
 +
 
 +
;Model checking improvements, and more generally PRO-B improvements
 +
:[[D23 PRO-B]]
  
−
:[[User:Nicolas/Collections/ADVANCE D3.4 Introduction|Introduction]] (Laurent Voisin/Nicolas Beauger)
+
;Decomposition support
 +
:[[D23 Decomposition]]
  
−
:[[User:Nicolas/Collections/ADVANCE D3.4 General Platform Maintenance|General Platform Maintenance]]  
+
;Initial definition of language support for code generation
−
:* Core Rodin platform (Laurent Voisin/Nicolas Beauger)
+
:[[D23 Code Generation]]
−
:* UML-B Improvements (Colin Snook, Vitaly Savicks)
 
−
:* ProR (Michael Jastram/Lukas Ladenberger)
 
−
:* Camille (Ingo Weigelt)
 
  
−
:[[User:Nicolas/Collections/ADVANCE D3.4 Improvement of automated proof|Improvement of automated proof]]  
+
;Improvements on provers
−
:* Integrated provers (Laurent Voisin/Nicolas Beauger)
+
:[[D23 Improvements on Existing Provers]]
−
:* SMT Provers (Laurent Voisin)
+
:[[D23 Rule-based Prover]]
  
−
:[[User:Nicolas/Collections/ADVANCE D3.4 Model Checking|Model Checking]] (Michael Leuschel & al.)
+
;Pattern Plug-in
 +
:[[D23 Pattern Plug-in]]
  
−
:[[User:Nicolas/Collections/ADVANCE D3.4 Language extension|Language extension]] (Asieh Salehi)
+
;Flow Plug-in
 +
:[[D23 Flow Plug-in]]
  
−
:[[User:Nicolas/Collections/ADVANCE D3.4 Model Composition and Decomposition|Model Composition and Decomposition]] (Asieh Salehi)
+
;Modularisation Plug-in
 +
:[[D23 Modularisation Plug-in]]

Revision as of 16:40, 2 November 2009

Introduction

The purpose of this page is to give a base for the DEPLOY Deliverable D23 (Model Construction and Analysis Tool II).

The D23 Writing Plan gives a table of contents for this document.

Template

For each item covered in this document, a wiki page shall be created (see Contents) to provide a description of work and describe the role of the WP9 partners during the passed year.

The purpose of the template is to provide a common structure for all of these pages. It takes into consideration the review feedback for the DEPLOY Deliverable D6 (Model Construction and Analysis Tool I).

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 are the main purposes?
  • Who is in charge of the tasks?
  • Who is involved among the academic and industrial partners? Who is involved as developer? Who is involved as user?

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

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 developpers and documentation written for end-users.

Planning

This paragraph shall give a timeline. More precisely, it shall give the current status of the new features (specification, still under development, available prototype, available since release M.m), their current version, describe the tasks which have already been completed and announce planned further work and deadlines (release versions of the Rodin platform).

Corrective and Evolutive Maintenance

This paragraph describes how bugs and feature requests are addressed.

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.
  • 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".

Contents

Introduction
D23 Introduction
General platform maintenance
D23 General platform maintenance
UML-B improvements
D23 UML-B
Model checking improvements, and more generally PRO-B improvements
D23 PRO-B
Decomposition support
D23 Decomposition
Initial definition of language support for code generation
D23 Code Generation
Improvements on provers
D23 Improvements on Existing Provers
D23 Rule-based Prover
Pattern Plug-in
D23 Pattern Plug-in
Flow Plug-in
D23 Flow Plug-in
Modularisation Plug-in
D23 Modularisation Plug-in
Retrieved from ‘https://wiki.event-b.org/index.php?title=User:Nicolas/Collections/ADVANCE_Deliverable_D3.4&oldid=11009’