User:Tommy/Collections/Deploy Deliverable D45

Introduction

The purpose of this page is to give a base for the final DEPLOY Deliverable D45 (Model Construction tools & Analysis IV) which will be delivered to the European Commission (27 April 2012).

Template

For each section covered in this document, a wiki page has been created and shall be completed (see Contents). Each of them should give a brief description of the work that was carried on during the last year of the project (Feb 2011-April 2012 [Extension included]) within the WP9 package, without going deeply into technical details.

Goal: give to the project reviewers some insight which should look like an executive summary on a given WP9 topic.

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 page shall be quite short (ca. 4-5 printed pages as the D45 contains 7 sections).
Each section is decomposed into 5 paragraphs. For each topic, a subparagraph should be written.

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.

Status

This paragraph shall give the current status of the work being done for a given topic (as of 27 Apr 2012).

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 27 Apr 2012, use past, present and future accordingly.
• The dedicated category, [[Category:D45 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 since the D32.

By doing so, you will have to add the additional paragraph (below) at the end of the page you complete:

==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).

Contents

D45

Introduction (Laurent Voisin)

General Platform Maintenance

• Platform maintenance (Thomas Muller)

• Mathematical extensions / Theory Plug-in (Issam Maamria)

• Plug-in Incompatibilities (All partners)

• Modularisation (Alexei Illiasov)

• Decomposition (Renato Silva)

• Team-based Development (Colin Snook, Vitaly Savicks)

• UML-B (Colin Snook, Vitaly Savicks)

• ProR (Michael Jastram)

• BMotion Studio (Lukas Ladenberger)

Scalability

• Improved performance (Laurent Voisin, Nicolas Beauger, Thomas Muller)

• Design Pattern Management / Generic Instantiation (Thai Son Hoang)

• Edition (Thomas Muller, Ingo Weigelt)

Prover Enhancement

• New rewriting and inference rules (Laurent Voisin)

• Advanced Preferences for Auto-tactics (Nicolas Beauger)

• Isabelle Plug-in (Matthias Schmaltz)

• ProB Disprover (Daniel Plagge, Jens Bendiposto)

• SMT Solver Integration (Laurent Voisin)

Code Generation (Andy Edmunds)

Model-based testing (Michael Leuschel, Alin Stefanescu)

Model Checking (Michael Leuschel)