Difference between revisions of "User:Nicolas/Collections/ADVANCE D3.4 Language extension"

From Event-B
Jump to: navigation, search
(Overview)
(Available Documentation)
Line 8: Line 8:
  
 
== Available Documentation ==
 
== Available Documentation ==
{{TODO}}
+
 
 +
Pre-studies (states of the art, proposals, discussions):
 +
* Proposals for Mathematical Extensions for Event-B.<ref>http://deploy-eprints.ecs.soton.ac.uk/216/</ref>
 +
* Mathematical Extension in Event-B through the Rodin Theory Component.<ref>http://deploy-eprints.ecs.soton.ac.uk/251/</ref>
 +
* Generic Parser's Design Alternatives.<ref>http://wiki.event-b.org/index.php/Constrained_Dynamic_Parser#Design_Alternatives</ref>
 +
 
 +
Technical details (specifications):
 +
* Mathematical_Extensions wiki page.<ref>http://wiki.event-b.org/index.php/Mathematical_Extensions</ref>
 +
* Constrained Dynamic Lexer wiki page.<ref>http://wiki.event-b.org/index.php/Constrained_Dynamic_Lexer</ref>
 +
* Constrained Dynamic Parser wiki page.<ref>http://wiki.event-b.org/index.php/Constrained_Dynamic_Parser </ref>
 +
* Theory plug-in wiki page.<ref>http://wiki.event-b.org/index.php/Theory_Plug-in</ref>
 +
 
 +
User's guides:
 +
* Theory Plug-in User Manual.<ref>http://wiki.event-b.org/images/Theory_Plugin.pdf</ref>
  
 
== Conclusion ==
 
== Conclusion ==

Revision as of 15:03, 20 October 2014

Overview

Mathematical extensions have been co-developed by Systerel (for the Core Rodin Platform) and Southampton (for the Theory plug-in). The main purpose of this new feature was to provide the Rodin user with a way to extend the standard Event-B mathematical language by supporting user-defined operators, basic predicates and algebraic types. Along with these additional notations, the user can also define new proof rules (proof extensions).

The Theory plug-in provides, among other things, a user-friendly mechanism to extend the Event-B mathematical language as well as the prover. A theory is the dedicated component used to hold mathematical extensions (datatypes, operators with direct definitions, operators with recursive definitions and operators with axiomatic definitions), and proof extensions (polymorphic theorems, rewrite and inference rules). Theories are developed in the workspace (akin to models), and are subject to static checking and proof obligation generation. Proof obligations generated from theories ensure any contributed extensions do not compromise the soundness of the existing infrastructure for modelling and proof. In essence, the Theory plug-in provides a systematic platform for defining, validating and using extensions while exploiting the benefits brought by proof obligations.

Motivations / Decisions

TODO

Available Documentation

Pre-studies (states of the art, proposals, discussions):

  • Proposals for Mathematical Extensions for Event-B.[1]
  • Mathematical Extension in Event-B through the Rodin Theory Component.[2]
  • Generic Parser's Design Alternatives.[3]

Technical details (specifications):

  • Mathematical_Extensions wiki page.[4]
  • Constrained Dynamic Lexer wiki page.[5]
  • Constrained Dynamic Parser wiki page.[6]
  • Theory plug-in wiki page.[7]

User's guides:

  • Theory Plug-in User Manual.[8]

Conclusion

TODO

References