Difference between pages "Rodin Proving Perspective" and "User:Tommy/Collections/Deploy Deliverable D45"

From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Im06r
 
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}}
+
== Introduction ==
== Overview ==
+
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).
The Proving Perspective is made of a number of windows (views): the Proof Tree, the Goal, the Selected Hypotheses, the Proof Control, the Proof Information, and the Search Hypotheses. In subsequent sections, we study each of these windows. Below is a screenshot of the proving perspective:
 
  
[[Image:ProvPers.png|center]]
+
== Template ==
 +
For each section covered in this document, a wiki page has been created and <b>shall be completed</b> (see [[#Contents | 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.<br>
 +
:<b>Goal: give to the project reviewers some insight which should look like an executive summary on a given WP9 topic.<br>
 +
:All details (papers, detailed wiki pages, etc.) should be made available as pointers.</b>
  
== Loading a Proof ==
+
This template provides a common structure for all of these pages.<br>
In order to load a proof, switch to the Proving Perspective, select the project from the Event-B Explorer, select and expand the component (context or machine), finally select the proof obligation of interest. The corresponding proof will be loaded.
+
Each page shall be quite short (ca. 4-5 printed pages as the D45 contains 7 sections).<br>
 +
Each section is decomposed into 5 paragraphs. <b>For each topic, a subparagraph should be written.</b><br>
  
== The Proof Tree ==
+
=== Overview ===
The proof tree describe each individual proof step in the proof. The proof tree can be seen in its corresponding window as seen in the following screenshot:
+
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?
  
[[Image:ProTree.png|center]]
+
=== 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.
  
Each line in the 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. Each node is labelled with a comment (description) explaining how it can be discharged. By selecting a node in the proof tree, the corresponding sequent is loaded: the hypotheses of the sequent are loaded to the Selected Hypotheses window, and the goal of the sequent is loaded to the Goal window.
+
=== 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.
  
=== Decoration===
+
=== Available Documentation ===
The leaves of the tree are decorated with three kinds of logos:
+
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.
  
* a green logo with a "'''<math>\surd </math>'''" in it means that this leaf is discharged,
+
=== Status ===
* a brown logo with a "'''?'''" in it means that this leaf is not discharged,
+
This paragraph shall give the current status of the work being done for a given topic (as of 27 Apr 2012).
* a blue logo with a "'''R'''" in it means that this leaf has been reviewed.
 
  
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: the node will become "brown" again (undischarged) and you can now try to discharge it.
+
== 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.
 +
* 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, <nowiki>[[Category:D45 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 since the D32.
 +
: By doing so, you will have to add the additional paragraph (below) at the end of the page you complete:
 +
==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).
  
=== Navigation within the Proof Tree===
+
== Deploy Deliverable ==
On top of the proof tree window, one can see three buttons:
+
=== D45 ===
  
* the "'''G'''" buttons allows you to see the goal of the sequent corresponding to the node
 
* the "'''+'''" button allows you to fully expand the proof tree
 
* the "'''-'''" allows you to fully collapse the tree: only the root stays visible.
 
  
=== Manipulating the Proof Tree===
+
:[[D45 Introduction|Introduction]] (Laurent Voisin)
 +
:[[D45 General Platform Maintenance|General Platform Maintenance]]
 +
:*Platform maintenance (Thomas Muller)
  
==== Hiding ====
+
:*Mathematical extensions / Theory Plug-in (Issam Maamria)
The little triangle (with a "+" or "-" inside) next to each node in the proof tree allows you to expand or collapse the subtree starting at that node.
 
  
==== Pruning ====
+
:*Plug-in Incompatibilities (All partners)
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 brown decorated. This allows you to resume the proof from that node. After selecting a sequent in the proof tree, pruning can be performed by right-clicking and then selecting "Prune".
 
  
Note that after pruning, the post-tactic is not applied to the new current sequent: if needed you have to press the "post-tactic" button in the Proof Control window. 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.
+
:*Modularisation (Alexei Illiasov)
  
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).
+
:*Decomposition (Renato Silva)
  
==== Copy/Paste ====
+
:*Team-based Development (Colin Snook, Vitaly Savicks)
  
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.
+
:*UML-B (Colin Snook, Vitaly Savicks)
  
== Goal and Selected Hypotheses ==
+
:*ProR (Michael Jastram)
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:GoalHyp.png|center]]
 
  
A selected hypothesis can be deselected (and as a result becomes hidden) by first clicking in the box (check 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:
+
:[[D45 Scalability|Scalability]]
 +
:*Improved performance (Laurent Voisin, Nicolas Beauger, Thomas  Muller)
  
[[Image:GoalHypSelect.png|center]]
+
:*Design Pattern Management / Generic Instantiation (Thai Son Hoang)
  
Here is the result:
+
:*Edition (Thomas Muller, Ingo Weigelt)
  
[[Image:GoalHypSelectRes.png|center]]
+
:[[D45 Prover Enhancement|Prover Enhancement]]
  
Notice that the deselected hypotheses are not lost: you can get them back by means of the Search Hypotheses window. The other two buttons next to the red ('''-''') button allow the user (in the order of their appearance from left to right) to select all hypotheses as well as inverse the current selection.
+
:*New rewriting and inference rules (Laurent Voisin)
  
The ('''ct''') button next to the goal allows you to do a proof by contradiction: by pressing it, the negation of the goal becomes a selected hypothesis whereas the goal becomes "'''⊥'''".
+
:*Advanced Preferences for Auto-tactics (Nicolas Beauger)  
  
The ('''ct''') button next to a selected hypothesis allows you to do another kind of proof by contradiction: by pressing it, the negation of the concerned hypothesis becomes the goal whereas the negated goal becomes an hypothesis.
+
:*Isabelle Plug-in (Matthias Schmaltz)
  
=== Applying Proof Rules ===
+
:*ProB Disprover (Daniel Plagge, Jens Bendiposto)
The red hyperlinks as well as the ('''ct''') buttons (also occasionally other green filled buttons next to it e.g., AND introduction in goal) allows the user to carry out interactive proofs. They are used to invoke proof rules (rewrite rules as well as inference rules).
 
  
[[Image:ApplyRewRule.png|center]]
+
:*SMT Solver Integration (Laurent Voisin)
  
==== Rewrite Rules ====
+
:[[D45 Code Generation|Code Generation]] (Andy Edmunds)
Rewrite rules are one-directional equalities (and equivalences) that can be used to simplify formulas (the goal or a single hypothesis). A rewrite rule is applied from left to right either in the goal or in one of the selected hypotheses, when its ''side condition'' holds.
 
  
A rewrite rule is applied either automatically ('''A''') or manually ('''M'''):
+
:[[D45 Model-based testing| Model-based testing]] (Michael Leuschel, Alin Stefanescu)  
* automatically, when post tactics are enabled. These rules are equivalence simplification laws.
 
* manually, through an interactive command. These rules gathers non equivalence laws, definition laws, distributivity laws and derived laws.
 
  
Each rule is named after the following elements:
+
:[[D45 Model Checking|Model Checking]] (Michael Leuschel)
  
* The law category: simplification law (SIMP), definition law (DEF), distributivity law (DISTRI), or else derived law (DERIV).
+
[[Category:D45 Deliverable]]
* 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.
+
[[Category:Books]]
* 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:
 
 
 
<center><math>  \True  = \False  \;\;\defi\;\;  \bfalse </math></center>
 
 
 
should also produce the rule:
 
 
 
<center><math>  \False  = \True  \;\;\defi\;\;  \bfalse </math></center>
 
 
 
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.
 
 
 
Rules marked with a star in the first column are implemented in the current prover.  Rules without a star are planned for implementation.
 
 
 
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 (see [[Proof 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.
 
 
 
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.
 
 
 
See [[Inference Rules]] list.
 
 
 
== The Proof Control Window ==
 
 
 
The Proof Control window contains the buttons which you can use to perform an interactive proof.
 

Revision as of 11:37, 7 November 2011

Template:Saved book

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

Deploy Deliverable

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