Difference between pages "The Proving Perspective (Rodin User Manual)" and "User:Tommy/Collections/ADVANCE Delivrable D3.2"

From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Frederic
 
imported>Tommy
 
Line 1: Line 1:
−
{{Navigation|Previous= [[The_Proof_Obligation_Explorer_(Rodin_User_Manual)|The Proof Obligation Explorer]]|Next= [[The_Mathematical_Language_(Rodin_User_Manual)|The Mathematical Language]]|Up= [[index_(Rodin_User_Manual)|User_Manual_index]]}}
+
{{saved_book}}
−
{{TOCright}}
 
  
−
The Proving Perspective is made of a number of windows: the proof tree, the goal, the selected hypotheses, the proof control, the proof information, and the searched hypotheses. In subsequent sections, we study these windows, but before that let us see how one can load a proof.
+
== Introduction ==
 +
The purpose of this page is to give a common structure and guidelines to collaboratively build the ADVANCE Deliverable D3.2 (Methods and tools for model construction and proof I) which will be delivered to the European Commission at month 10 (31st July 2012).
 +
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;
  
−
== Loading a Proof ==
+
== Schedule ==
 +
*the template of the deliverable is released on 01-06-2012
 +
*the contents are contributed by 22-06-2012
 +
*the draft for internal review is sent on 29-06-2012
 +
*the final deliverable is produced for 31-07-2012
  
−
In order to load a proof, enter the Proof Obligation window, select the project, select and expand the component, finally select the proof obligation: the corresponding proof will be loaded. As a consequence:
+
== 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 the first 10 months of the project (Oct 2011-July 2012). 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).'''
  
−
* the proof tree is loaded in the Proof Tree window. As we shall see in section [[The_Proving_Perspective_(Rodin_User_Manual)#The_Proof_Tree|6.2]], each node of the proof tree is associated with a sequent.
+
== Direct link with the DoW ==
−
* In case the proof tree has some "pending" nodes (whose sequents are not discharged yet) then the sequent corresponding to the first pending node is decomposed: its goal is loaded in the Goal window (section [[The_Proving_Perspective_(Rodin_User_Manual)#Goal and Selected Hypotheses|6.3]]), whereas parts of its hypotheses (the "selected" ones) are loaded in the Selected Hypotheses window (section [[The_Proving_Perspective_(Rodin_User_Manual)#Goal and Selected Hypotheses|6.3]]).
+
To ease the reviewer's reading of the present deliverable, the structure of the document will follow the objectives mentioned in the DoW:
−
* In case the proof tree has no pending node, then the sequent of the root node is loaded as explained previously.
+
''
 +
D3.2) Methods and tools for model construction and proof I: This deliverable describes the maintenance actions
 +
carried through, together with a summary of progress on the improvement of automated proof and model
 +
checking. A list of the scalability enhancements achieved so far in the project, together with their expected
 +
impact on performance and capacity, is included and validated against the Tool Development Roadmap.
 +
Progress of the planned improvements to the existing automated proof tools is described, stating clearly what
 +
improvements have been delivered and how the development of longer-term improvements measures against
 +
the original plan. Appropriate documentation and tutorials are delivered to describe the methods that will ensure
 +
that these improvements can be best used to increase the proportion of automated proofs. Improvements to the
 +
ProB model checking tool and associated methods are also described. [month 10]''
  
−
== The Proof Tree ==
+
=== 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?
  
−
=== Description of the Proof Tree ===
+
=== 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.
  
−
The proof tree can be seen in the corresponding window as shown in the following screen shot:
+
=== 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.
  
−
[[Image:um-0095.png|center]]
+
=== 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.
  
−
Each line in the proof tree corresponds to a node which is a sequent. A line is right shifted when the corresponding node is a direct descendant of the node of the previous line. Here is an illustration of the previous tree:
+
=== Planning ===
 +
This paragraph shall give an outlook on the current status and the plans for future work.
  
−
[[Image:Tree.png|center]]
+
== Formatting rules ==
 +
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.
 +
* 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 31st July 2012, use past, present and future accordingly.
 +
* The dedicated category, <nowiki>[[Category:ADVANCE D3.2 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).
  
−
Each node is labelled with a comment explaining how it can be discharged. By selecting a node in the proof tree, the corresponding sequent is decomposed and loaded in the Goal and Selected Hypotheses windows as explained in section [[The_Proving_Perspective_(Rodin_User_Manual)#Loading a Proof|6.1]].
+
== ADVANCE Deliverable ==
 +
=== D3.2 ===
  
−
=== Decoration ===
+
:[[ADVANCE D3.2 Introduction|Introduction]] (Laurent Voisin/Thomas Muller)
  
−
The leaves of the tree are decorated with three kinds of logos:
+
:[[ADVANCE D3.2 General Platform Maintenance|General Platform Maintenance]]
 +
:* Core Rodin platform (Thomas Muller)
 +
:* UML-B Improvements (Colin Snook, Vitaly Savicks)
 +
:* Code generation (Andy Edmunds)
 +
:* ProR (Michael Jastram/Lukas Ladenberger)
 +
:* Camille (Ingo Weigelt)
  
−
* a green logo with a "<math>\surd </math>" in it means that this leaf is discharged,
+
:[[ADVANCE D3.2 Improvement of automated proof|Improvement of automated proof]]
−
* a red logo with a "?" in it means that this leaf is not discharged,
+
:* Integrated provers (Laurent Voisin/Thomas Muller)
−
* a blue logo with a "R" in it means that this leaf has been reviewed.
+
:* SMT Provers (Laurent Voisin)
  
−
Internal nodes in the proof tree are decorated in the same (but lighter) way. Note that a "reviewed" leaf is one that is not discharged yet by the prover. Instead, it has been "seen" by the user who decided to have it discharged later. Marking nodes as "reviewed" is very convenient in order to perform an interactive proof in a gradual fashion. In order to discharge a "reviewed" node, select it and prune the tree at that node (section [[The_Proving_Perspective_(Rodin_User_Manual)#Pruning|6.2.5]]): the node will become "red" again (undischarged) and you can now try to discharge it.
+
:[[ADVANCE D3.2 Language extension|Language extension]] (Issam Maamria)
  
−
=== Navigation within the Proof Tree ===
+
:[[ADVANCE D3.2 Model Checking|Model Checking]] (Michael Leuschel & al.)
  
−
On top of the proof tree window one can see three buttons:
+
:[[ADVANCE D3.2 Model Composition and Decomposition|Model Composition and Decomposition]] (Renato Silva)
  
−
* the "G" buttons allows you to see the goal of the sequent corresponding to the node
+
[[Category:ADVANCE D3.2 Deliverable]]
−
* the "+" button allows you to fully expand the proof tree
+
[[Category:Books]]
−
* the "-" allows you to fully collapse the tree: only the root stays visible.
 
−
 
 
−
=== Hiding ===
 
−
 
 
−
The little triangle next to each node in the proof tree allows you to expand or collapse the subtree starting at that node.
 
−
 
 
−
=== Pruning ===
 
−
 
 
−
The proof tree can be pruned from a node: it means that the subtree starting at that node is eliminated. The node in question becomes a leaf and is red decorated. This allows you to resume the proof from that node. After selecting a sequent in the proof tree, pruning can be performed in two ways:
 
−
 
 
−
* by right-clicking and then selecting "Prune",
 
−
* by pressing the "Scissors" button in the proof control window (section [[The_Proving_Perspective_(Rodin_User_Manual)#The Proof Control Window|6.4]]).
 
−
 
 
−
Note that after pruning, the post-tactic (section [[The_Proving_Perspective_(Rodin_User_Manual)#The Automatic Post-tactic|6.8]]) is not applied to the new current sequent: if needed you have to press the "post-tactic" button in the Proof Control window (section [[The_Proving_Perspective_(Rodin_User_Manual)#The Proof Control Window|6.4]]). This happens in particular when you want to redo a proof from the beginning: you prune the proof tree from the root node and then you have to press the "post-tactic" button in order to be in exactly the same situation as the one delivered automatically initially.
 
−
 
 
−
When you want to redo a proof from a certain node, it might be advisable to do it after copying the tree so that in case your new proof fails you can still resume the previous situation by pasting the copied version (see next section).
 
−
 
 
−
=== Copy/Paste ===
 
−
 
 
−
By selecting a node in the proof tree and then clicking on the right key of the mouse, you can copy the part of the proof tree starting at that sequent: it can later be pasted in the same way. This allows you to reuse part of a proof tree in the same (or even another) proof.
 
−
 
 
−
== Goal and Selected Hypotheses ==
 
−
 
 
−
The "Goal" and "Selected Hypotheses" windows display the current sequent you have to prove at a given moment in the proof. Here is an example:
 
−
 
 
−
[[Image:um-0098.png|center]]
 
−
 
 
−
A selected hypothesis can be deselected by first clicking in the box situated next to it (you can click on several boxes) and then by pressing the red (-) button at the top of the selected hypothesis window:
 
−
 
 
−
[[Image:um-0099.png|center]]
 
−
 
 
−
Here is the result:
 
−
 
 
−
[[Image:um-0100.png|center]]
 
−
 
 
−
Notice that the deselected hypotheses are not lost: you can get them back by means of the Searched Hypotheses window (section [[The_Proving_Perspective_(Rodin_User_Manual)#srchhyp|6.7]]).
 
−
 
 
−
The three other buttons next to the red (-) button allow you to do the reverse operation, namely keeping some hypotheses. The (ct) button next to the goal allows you to do a proof by contradiction: pressing it makes the negation of the goal being a selected hypothesis whereas the goal becomes "false". The (ct) button next to a selected hypothesis allows you to do another kind of proof by contradiction: pressing it makes the negation of the hypothesis the goal whereas the negated goal becomes an hypothesis.
 
−
 
 
−
== Rewrite rules ==
 
−
 
 
−
Rewrite rules are applied either automatically (A) or manually (M).
 
−
 
 
−
A rule may be applied:
 
−
* Automatically (A), when post tactics are enabled. These rules are equivalence simplification laws.
 
−
* Manually (M), through an interactive command. These rules gathers non equivalence laws, definition laws, distributivity laws and derived laws.
 
−
 
 
−
Rewrite rules are applied from left to right either in the goal or in the selected hypotheses, when their ''side condition'' hold.
 
−
 
 
−
Each rule is named after the following elements:
 
−
 
 
−
* The law category: simplification law (SIMP), definition law (DEF), distributivity law (DISTRI), or else derived law (DERIV).
 
−
* Particularity on terminal elements of the left part of the rule (optional): special element (SPECIAL) such as the empty-set, type expression (TYPE), same element occurring more then once (MULTI), literal (LIT). A type expression is either a basic type (<math>\intg, \Bool</math>, any carrier set), or <math>\pow</math>(type expression), or type expression<math>\cprod</math>type expression.
 
−
* One or more elements describing from top to down the left part of the rule, eg. predicate AND, expression BUNION.
 
−
* Detail to localize those elements (optional): left (L), right (R).
 
−
 
 
−
Rewrite rules having an equivalence operator in their left part may also describe other rules. eg: the rule:
 
−
 
 
−
<math>  \True  = \False  \;\;\defi\;\;  \bfalse </math>
 
−
 
 
−
should also produce the rule:
 
−
 
 
−
<math>  \False  = \True  \;\;\defi\;\;  \bfalse </math>
 
−
 
 
−
 
 
−
For associative operators in connection with distributive laws as in:
 
−
 
 
−
<center><math> P \land (Q \lor \ldots \lor R) </math></center>
 
−
 
 
−
it has been decided to put the "button" on the first associative/commutative operator (here <math>\lor </math>). Pressing that button will generate a menu: the first option of this menu will be to distribute all associative/commutative operators, the second option will be to distribute only the first associative/commutative operator. In the following presentation, to simplify matters, we write associative/commutative operators with two parameters only, but it must always be understood implicitly that we have a sequence of them. For instance, we shall never write <math> Q \lor \ldots \lor R </math> but <math> Q \lor R </math> instead. Rules are sorted according to their purpose.
 
−
 
 
−
 
 
−
Rewrite rules are split into:
 
−
 
 
−
* [[Set Rewrite Rules]]
 
−
* [[Relation Rewrite Rules]]
 
−
* [[Arithmetic Rewrite Rules]]
 
−
 
 
−
They are also available in a single large page [[All Rewrite Rules]].
 
−
 
 
−
== Inference Rules ==
 
−
 
 
−
Inference rules are applied either automatically (A) or manually (M).
 
−
 
 
−
 
 
−
Inference rules applied automatically are applied at the end of each proof step. They have the following possible effects:
 
−
 
 
−
* they discharge the goal,
 
−
* they simplify the goal and add a selected hypothesis,
 
−
* they simplify the goal by decomposing it into several simpler goals,
 
−
* they simplify a selected hypothesis,
 
−
* they simplify a selected hypothesis by decomposing it into several simpler selected hypotheses.
 
−
 
 
−
<br />
 
−
 
 
−
Inference rules applied manually are used to perform an interactive proof. They can be invoked by pressing "buttons" which corresponds to emphasized (red) operators in the goal or the hypotheses. A menu is proposed when there are several options.
 
−
 
 
−
<br />
 
−
 
 
−
See [[Inference Rules]]
 
−
 
 
−
== The Proof Control Window ==
 
−
 
 
−
The Proof Control window contains the buttons which you can use to perform an interactive proof. Next is a screen shot where you can see successively from top to bottom:
 
−
 
 
−
* some selected hypotheses,
 
−
* the goal,
 
−
* the "Proof Control" window,
 
−
* a small editing area within which you can enter parameters used by some buttons of the Proof Control window
 
−
* the smiley (section [[The_Proving_Perspective_(Rodin_User_Manual)#The Simley|6.5]])
 
−
 
 
−
[[Image:um-0101.png|center]]
 
−
 
 
−
The Proof Control window offers a number of buttons which we succinctly describe from left to right:
 
−
 
 
−
* (p0): the prover PP attempts to prove the goal (other cases in the list)
 
−
* (R) review: the user forces the current sequent to be discharged, it is marked as being reviewed (it’s logo is blue-colored)
 
−
* (dc) proof by cases: the goal is proved first under the predicate written in the editing area and then under its negation,
 
−
* (ah) lemma: the predicate in the editing area is proved and then added as a new selected hypothesis,
 
−
* (ae) abstract expression: the expression in the editing area is given a fresh name,
 
−
* the auto-prover attempts to discharge the goal. The auto-prover is the one which is applied automatically on all proof obligations (as generated automatically by the proof obligation generator after a "save") without any intervention of the user. With this button, you can call yourself the auto-prover within an interactive proof.
 
−
* the post-tactic is executed (see section [[The_Proving_Perspective_(Rodin_User_Manual)#The Automatic Post-tactic|6.8]]),
 
−
* lasso: load in the Selected Hypotheses window those unseen hypotheses containing identifiers which are common with identifiers in the goal and selected hypotheses,
 
−
* backtrack form the current node (i.e., prune its parent),
 
−
* scissors: prune the proof tree from the node selected in the proof tree,
 
−
* show (in the Search Hypotheses window) hypotheses containing the character string as in the editing area,
 
−
* show the Cache Hypotheses window,
 
−
* load the previous non-discharged proof obligation,
 
−
* load the next undischarged proof obligation,
 
−
* (i) show information corresponding to the current proof obligation in the corresponding window. This information correspond to the elements that took directly part in the proof obligation generation (events, invariant, etc.),
 
−
* goto the next pending node of the current proof tree,
 
−
* load the next reviewed node of the current proof tree.
 
−
 
 
−
== The Smiley ==
 
−
 
 
−
The smiley can take three different colors: (1) red, meaning that the proof tree contains one or more non-discharged sequents, (2) blue, meaning that all non-discharged sequents of the proof tree have been reviewed, (3) green, meaning that all sequents of the proof tree are discharged.
 
−
 
 
−
== The Operator "Buttons" ==
 
−
 
 
−
In the goal and in the selected, searched, or cache hypotheses some operators are colored in red. It means that they are "buttons" you can press. When doing so, the meaning (sometimes several) is shown in a menu where you can select various options. The operation performed by these options is described in sections [[The_Proving_Perspective_(Rodin_User_Manual)#Interactive Rewrite Rules|6.9.1]] and [[The_Proving_Perspective_(Rodin_User_Manual)#Interactive Inference Rules|6.9.2]].
 
−
 
 
−
== The Search Hypotheses Window ==
 
−
 
 
−
A window is provided which contains the hypotheses having a character string in common with the one in the editing area. For example, if we search for hypotheses involving the character string "cr", then after pressing the "search hypothesis" button in the proof control window, we obtain the following:
 
−
 
 
−
[[Image:um-0102.png|center]]
 
−
 
 
−
Such hypotheses can be moved to the "Selected Hypotheses" window (button (+)) or removed from the "Search Hypotheses" window (button (-)). As for the selected hypotheses, other buttons situated next to the previous ones, allow you to move or remove all hypotheses. By pressing the (ct) button the negation of the corresponding hypothesis becomes the new goal.
 
−
 
 
−
== The Automatic Post-tactic ==
 
−
 
 
−
In this section, we present the various rewrite or inference rules which are applied automatically as a systematic post-tactic after each proof step. Note that the post-tactic can be disabled by using the "'''P'''<math>\! \! \! \! /</math>" button situated on the right of the proof control window.
 
−
 
 
−
The post-tactic is made of two different rules: rewrite rules, which are applied on any sub-formula of the goal or selected hypotheses (section [[The_Proving_Perspective_(Rodin_User_Manual)#Rewrite Rules|6.8.1]]) and inference rules which are applied on the current sequent (section [[The_Proving_Perspective_(Rodin_User_Manual)#Automatic Inference Rules|6.8.2]]).
 
−
 
 
−
 
 
−
 
 
−
 
 
−
 
 
−
=== Preferences for the Post-tactic ===
 
−
 
 
−
The post-tactic can be configured by means of a preference page which can be obtained as follows: press the "Window" button on the top tooolbar. On the coming menu, press the "Preferences" button. On the coming menu, press the "Event-B" menue, then the "Sequent Prover’, and finally the "Post-Tactic" button. This yilds the following window:
 
−
 
 
−
[[Image:um-0147.png|center]]
 
−
 
 
−
In the left part you can see the ordered sequence of individual tactics composing the post-tactic, whereas the right part contains further tactics you can incorporate in the left part. By selecting a tactic you can move it from on part to the other or change the order in the left part.
 

Revision as of 09:34, 1 June 2012

Template:Saved book

Introduction

The purpose of this page is to give a common structure and guidelines to collaboratively build the ADVANCE Deliverable D3.2 (Methods and tools for model construction and proof I) which will be delivered to the European Commission at month 10 (31st July 2012). The deliverable will give to the project reviewers some insight on what happened in the work package 3, concerning its 3 main objectives:

  1. to provide the methodological and tooling means for modelling Systems-of-Systems.
  2. to provide expert formal proof support to the industrial partners;
  3. to improve the usability and productivity of the Rodin platform to support larger-scale developments;

Schedule

  • the template of the deliverable is released on 01-06-2012
  • the contents are contributed by 22-06-2012
  • the draft for internal review is sent on 29-06-2012
  • the final deliverable is produced for 31-07-2012

Template

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 the first 10 months of the project (Oct 2011-July 2012). 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).

Direct link with the DoW

To ease the reviewer's reading of the present deliverable, the structure of the document will follow the objectives mentioned in the DoW: D3.2) Methods and tools for model construction and proof I: This deliverable describes the maintenance actions carried through, together with a summary of progress on the improvement of automated proof and model checking. A list of the scalability enhancements achieved so far in the project, together with their expected impact on performance and capacity, is included and validated against the Tool Development Roadmap. Progress of the planned improvements to the existing automated proof tools is described, stating clearly what improvements have been delivered and how the development of longer-term improvements measures against the original plan. Appropriate documentation and tutorials are delivered to describe the methods that will ensure that these improvements can be best used to increase the proportion of automated proofs. Improvements to the ProB model checking tool and associated methods are also described. [month 10]

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 were 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 an outlook on the current status and the plans for future work.

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.
  • 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 31st July 2012, use past, present and future accordingly.
  • The dedicated category, [[Category:ADVANCE D3.2 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).

ADVANCE Deliverable

D3.2

Introduction (Laurent Voisin/Thomas Muller)
General Platform Maintenance
  • Core Rodin platform (Thomas Muller)
  • UML-B Improvements (Colin Snook, Vitaly Savicks)
  • Code generation (Andy Edmunds)
  • ProR (Michael Jastram/Lukas Ladenberger)
  • Camille (Ingo Weigelt)
Improvement of automated proof
  • Integrated provers (Laurent Voisin/Thomas Muller)
  • SMT Provers (Laurent Voisin)
Language extension (Issam Maamria)
Model Checking (Michael Leuschel & al.)
Model Composition and Decomposition (Renato Silva)
Retrieved from ‘https://wiki.event-b.org/index.php?title=The_Proving_Perspective_(Rodin_User_Manual)&oldid=11038’