Difference between revisions of "User:Pascal/Collections/Deploy Deliverable D23"

From Event-B
Jump to navigationJump to search
imported>Pascal
imported>Pascal
Line 43: Line 43:
 
== Contents ==
 
== Contents ==
 
;Introduction
 
;Introduction
:[[D23 Introduction]]
+
:[[D23 Introduction]] (Laurent Voisin)
  
 
;General Platform Maintenance
 
;General Platform Maintenance
:[[D23 General Platform Maintenance]]
+
:[[D23 General Platform Maintenance]] (Carine Pascal)
  
 
;UML-B Improvements
 
;UML-B Improvements
:[[D23 UML-B]]
+
:[[D23 UML-B]] (Colin Snook)
  
 
;PRO-B Improvements
 
;PRO-B Improvements
:[[D23 PRO-B]]  
+
:[[D23 PRO-B]] (Jens Bendisposto / Michael Leuschel)
  
 
;Decomposition Support
 
;Decomposition Support
:[[D23 Decomposition]]
+
:[[D23 Decomposition]] (Carine Pascal / Renato Silva)
  
 
;Initial Definition of Language Support for Code Generation
 
;Initial Definition of Language Support for Code Generation
:[[D23 Code Generation]]
+
:[[D23 Code Generation]] (Michael Butler)
  
 
;Improvements on Provers
 
;Improvements on Provers
:[[D23 Improvements on Existing Provers]]
+
:[[D23 Improvements on Existing Provers]] (Nicolas Beauger)
:[[D23 Rule-based Prover]]
+
:[[D23 Rule-based Prover]] (Issam Maamria)
  
 
;Pattern Plug-in
 
;Pattern Plug-in
:[[D23 Pattern Plug-in]]
+
:[[D23 Pattern Plug-in]] (Thai Son Hoang)
  
 
;Flow Plug-in
 
;Flow Plug-in
:[[D23 Flow Plug-in]]
+
:[[D23 Flow Plug-in]] (Alexei Iliasov)
  
 
;Modularisation Plug-in
 
;Modularisation Plug-in
:[[D23 Modularisation Plug-in]]
+
:[[D23 Modularisation Plug-in]] (Alexei Iliasov)

Revision as of 17:51, 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) which will be delivered to the European Commission 29 January 2010.

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 2009-Jan 2010). The purpose is to give to the project reviewers some insight on what happened in WP9, 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. It takes into consideration the feedback we got for DEPLOY Deliverable D6 (Model Construction and Analysis Tool I). 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 developpers and documentation written for end-users.

Planning

This paragraph shall give a timeline and current status (as of 29 Jan 2010).

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".
  • Remember that the document is dated 29 Jan 2010, use past, present and future accordingly.

Contents

Introduction
D23 Introduction (Laurent Voisin)
General Platform Maintenance
D23 General Platform Maintenance (Carine Pascal)
UML-B Improvements
D23 UML-B (Colin Snook)
PRO-B Improvements
D23 PRO-B (Jens Bendisposto / Michael Leuschel)
Decomposition Support
D23 Decomposition (Carine Pascal / Renato Silva)
Initial Definition of Language Support for Code Generation
D23 Code Generation (Michael Butler)
Improvements on Provers
D23 Improvements on Existing Provers (Nicolas Beauger)
D23 Rule-based Prover (Issam Maamria)
Pattern Plug-in
D23 Pattern Plug-in (Thai Son Hoang)
Flow Plug-in
D23 Flow Plug-in (Alexei Iliasov)
Modularisation Plug-in
D23 Modularisation Plug-in (Alexei Iliasov)