Difference between revisions of "User:Tommy/Collections/Deploy Deliverable D32"

From Event-B
Jump to navigationJump to search
imported>Tommy
imported>Leuschel
 
(7 intermediate revisions by 4 users not shown)
Line 37: Line 37:
 
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.
 +
* DEPLOY 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.
Line 42: Line 43:
 
* Remember that the document is dated 28 Jan 2011, use past, present and future accordingly.
 
* Remember that the document is dated 28 Jan 2011, use past, present and future accordingly.
 
* The dedicated category, <nowiki>[[Category:D32 Deliverable]]</nowiki>, shall be specified for wiki pages.
 
* The dedicated category, <nowiki>[[Category:D32 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] that has been installed recently.
 +
: 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).
  
 
== Deploy Deliverable ==
 
== Deploy Deliverable ==
Line 48: Line 54:
 
:[[D32 Introduction|Introduction]] (Laurent Voisin)
 
:[[D32 Introduction|Introduction]] (Laurent Voisin)
  
==== General Platform Maintenance ====
+
:[[D32 General Platform Maintenance|General Platform Maintenance]]  
:[[D32 Platform Maintenance and Enhancements|Platform Maintenance and Enhancements]] (Thomas Muller)
+
:* Generalities (Thomas Muller)
:[[D32 Refactoring Plug-in|Refactoring Plug-in]] (Renato Silva)
+
:* Refactoring (Renato Silva)
  
==== Mathematical Extensions ====
+
:[[D32 Mathematical Extensions|Mathematical Extensions]]  
:[[D32 Mathematical Extensions|Mathematical Extensions]] (Nicolas Beauger, Issam Maamria, Colin Snook)
+
:* Core (Nicolas Beauger)
:[[D32 Records Plug-in|Records]] (Colin Snook)
+
:* Theory Plug-in (Issam Maamria)
 +
:* Records (Colin Snook)
  
==== Provers ====
 
 
:[[D32 Provers|Provers]]
 
:[[D32 Provers|Provers]]
:*relevance filter (Matthias Schmaltz)
+
:* Relevance filter (Matthias Schmaltz)
:*work on soundness (Matthias Schmaltz)
+
:* Work on soundness (Matthias Schmaltz)
:*improve WD for simpler POs (Systerel)
+
:* Improve WD for simpler POs (Laurent Voisin)
  
==== UML-B ====
+
:[[D32 UML-B|UML-B Improvements]] (Colin Snook, Vitaly Savicks)
:[[D32 UML-B|UML-B Improvements and new features]] (Colin Snook, Vitaly Savicks)
 
:* new features
 
:* state-machine animation
 
  
==== Code generation ====
 
 
:[[D32 Code generation|Code generation]] (Andy Edmunds)
 
:[[D32 Code generation|Code generation]] (Andy Edmunds)
  
==== Teamwork / Scalability ====
 
 
:[[D32 Teamwork|Teamwork]]
 
:[[D32 Teamwork|Teamwork]]
:*Storing Models in SVN (Colin Snook)
+
:* Storing Models in SVN (Colin Snook)
:*Model Decomposition(Renato Silva)
+
:* Model Decomposition (Renato Silva)
:*flows plug-in, modularisation plug-in (Alexei Iliasov)
+
:* Modularisation Plug-in (Alexei Iliasov)
 +
:[[D32 Scalability|Scalability]]
 +
:* Flows Plug-in (Alexei Iliasov)
 +
:* Group refinement (Alexei Iliasov)
 +
:* Modes (Alexei Iliasov)
 +
:* Qualitative Reasoning (Thai Son Hoang)
  
:[[D32 Qualitative Reasoning|Qualitative reasoning]] (Thai Son Hoang)
+
:[[D32 Model Animation|Model Animation]] (Michael Leuschel & al.)
  
==== Model Animation ====
+
:* Siemens Data Validation
:[[D32 Model Animation|Model Animation]] (Michael Leuschel & al.)
+
:* Multi-level Animation
 +
:* Constraint-Based Deadlock Checking
 +
:* BMotionStudio and Industrial Models
 +
:* Evaluation of the ProB Constraint Solver
 +
:* Various other improvements
  
==== Model-based testing ====
 
 
:[[D32 Model-based testing| Model-based testing]]
 
:[[D32 Model-based testing| Model-based testing]]
:*Existing 
prototype 
description (Michael Leuschel & al.)
+
 
:*SDmonstrator 
tool
 (Michael Leuschel & al.)
+
:* Generalities (Michael Leuschel & al.)
:*Search-based 
software 
engineering
 technologies
 (Alin Stefanescu)
+
:* Case studies (Alin Stefanescu)
  
 
[[Category:D32 Deliverable]]
 
[[Category:D32 Deliverable]]
 
[[Category:Books]]
 
[[Category:Books]]

Latest revision as of 14:52, 30 November 2010

Template:Saved book

Introduction

The purpose of this page is to give a base for the DEPLOY Deliverable D32 (Model Construction tools & Analysis III) which will be delivered to the European Commission (28 January 2011).

Template

For each item covered in this document, a wiki page shall be created (see Contents) to give a brief description of the work that was carried on during the second year of the project (Feb 2010-Jan 2011). The purpose is to give to the project reviewers some insight on what happened in the WP9 package, but without going deeply into technical details. It should look more like an executive summary. All details (papers, detailed wiki pages, etc.) should be made available as pointers.

This template provides a common structure for all of these pages. Each contribution shall be quite short (ca. two printed pages).

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 are 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 a timeline and current status (as of 28 Jan 2011).

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.
  • DEPLOY 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 28 Jan 2011, use past, present and future accordingly.
  • The dedicated category, [[Category:D32 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).

Deploy Deliverable

D32

Introduction (Laurent Voisin)
General Platform Maintenance
  • Generalities (Thomas Muller)
  • Refactoring (Renato Silva)
Mathematical Extensions
  • Core (Nicolas Beauger)
  • Theory Plug-in (Issam Maamria)
  • Records (Colin Snook)
Provers
  • Relevance filter (Matthias Schmaltz)
  • Work on soundness (Matthias Schmaltz)
  • Improve WD for simpler POs (Laurent Voisin)
UML-B Improvements (Colin Snook, Vitaly Savicks)
Code generation (Andy Edmunds)
Teamwork
  • Storing Models in SVN (Colin Snook)
  • Model Decomposition (Renato Silva)
  • Modularisation Plug-in (Alexei Iliasov)
Scalability
  • Flows Plug-in (Alexei Iliasov)
  • Group refinement (Alexei Iliasov)
  • Modes (Alexei Iliasov)
  • Qualitative Reasoning (Thai Son Hoang)
Model Animation (Michael Leuschel & al.)
  • Siemens Data Validation
  • Multi-level Animation
  • Constraint-Based Deadlock Checking
  • BMotionStudio and Industrial Models
  • Evaluation of the ProB Constraint Solver
  • Various other improvements
Model-based testing
  • Generalities (Michael Leuschel & al.)
  • Case studies (Alin Stefanescu)