imported>Im06r |
imported>Ladenberger |
| Line 1: |
Line 1: |
| − | Return to [[Rodin Plug-ins]]
| + | == Overview == |
| | + | {{TODO}} |
| | | | |
| − | See also [[Theory News and Support]]
| + | == Motivations / Decisions == |
| | + | '''B to TLA+''' |
| | | | |
| − | The Theory plug-in is the successor of the Rule-based Prover (which will be referred to as RbP) plug-in. The Theory plug-in
| + | '''LTL Fairness''' |
| − | provides capabilities to extend the Event-B language and the proving infrastructure in a familiar fashion to Rodin users. If you are looking for the user manual or the latest news on the Theory plug-in, please refer to [[Theory News and Support|Theory News and Support]].
| |
| − | This page provides useful information about the plug-in and its capabilities.
| |
| | | | |
| − | ===Motivation===
| + | '''Theory Support''' |
| − | The mathematical language used in Event-B has so far been fixed in the Abstract Syntax Tree (AST). See [http://wiki.event-b.org/index.php/Event-B_Mathematical_Language Mathematical Language] for more details. However, in Rodin 2.0, support for customized operator has been introduced. See [http://wiki.event-b.org/index.php/Mathematical_extensions Mathematical Extensions].
| |
| | | | |
| − | Prior to Rodin 2.0, since the AST of Event-B mathematical language was fixed, it was not possible to defined reusable polymorphic operators and datatypes. A workaround was to define any required operators as set constructs in contexts. Originally, contexts were supposed to provide a parametrization of machines. The aforementioned limitations of the AST lead to users to use contexts for purposes for which they were not intentionally devised. Examples of operators that can be useful to users include the sequence operator and the bag operator.
| + | '''Physical Units''' |
| | | | |
| − | ===Overview===
| + | The physical units analysis has been further stabilised, several reported bugs have been fixed. |
| − | The Theory plug-in is a Rodin extension that provides the facility to define mathematical extensions as well as prover extensions. | + | Support for physical units has been extended to theories along with the general theory-related improvements of ProB mentioned in the previous paragraph. |
| − | Mathematical extensions are new operator definitions and new datatype definitions. Operator definitions can be expression operators (card) and predicate operators (finite). Datatypes extensions can be used to define enumerated datatypes (DIRECTION) as well as inductive datatypes (Tree).
| + | The plug-in was ported to Rodin 3, all bugfixes and changes could be back ported to Rodin 2 successfully. |
| | | | |
| − | The placeholder for mathematical and prover extensions is a Theory construct which looks similar to contexts and machines. A theory can include datatypes definitions, operator definitions, inference and rewrite rules. The user manual provides a step-by-step guide to developing and using theories.
| + | Further extension to the unit analysis include: |
| | + | * Support for the analysis of units throughout refinement relations. |
| | + | * Support for abstract units like "length" that can later be concretised to standard SI units. |
| | | | |
| − | ===Capabilities===
| + | {{TODO}} |
| − | The Theory plug-in has the following capabilities:
| |
| − | * Theory Definition
| |
| − | ** Definition of datatypes: datatypes are defined by supplying the types on which they are polymorphic, a set of constructors one of which has to be a base constructor. Each constructor may or may not have destructors.
| |
| − | ** Definition of operators: operators can be defined as predicate or expression operators. An expression operator is an operator that "returns" an expression, an example existing operator is ''card(s)''. A predicate operator is one that "returns" a predicate, an example existing predicate operator is ''finite(s)''.
| |
| − | ** Definition of rewrite rules: rewrite rules are one-directional equalities that can be applied from left to right. The Theory plug-in can be used to define rewrite rules.
| |
| − | ** Definition of inference rules: inference rules can be used to infer new hypotheses, split a goal into sub-goals or discharge sequents.
| |
| − | ** Validation of extensions: where appropriate, proof obligations are generated to ensure soundness of extensions. This includes, proof obligations for validity of inference and rewrite rules, as well as proof obligations to validate operator properties such as associativity and commutativity.
| |
| − | * Theory Deployment: this step signifies that a theory is ready for use.
| |
| − | ** Theories can be deployed after they have been optionally validated by the user. It is strongly advisable to discharge all proof obligations before deployment.
| |
| − | ** Once a theory has been deployed to the designated project (at the moment MathExtensions project), all its extensions (mathematical and prover extensions) can be used in models as well as other theories.
| |
| | | | |
| − | ===Insider Look=== | + | == Available Documentation == |
| − | The Theory plug-in partially satisfies the requirements outlined in the following document:
| |
| − | * [http://deploy-eprints.ecs.soton.ac.uk/80/ Abrial, Jean-Raymond and Butler, Michael and Schmalz, Matthias and Hallerstede, Stefan and Voisin, Laurent. Mathematical Extensions Proposal]
| |
| | | | |
| − | A more accurate description of the implemented plug-in can be found in the following document:
| + | '''ProB'''<br> |
| − | * [http://deploy-eprints.ecs.soton.ac.uk/251/ Mathematical Extensions Summary]
| + | The ProB Website<ref>http://www.stups.uni-duesseldorf.de/ProB</ref> is the place where we collect information on the ProB toolset. There are several tutorials on ProB available in the User manual section. We also supply documentation on extending ProB for developers. |
| | | | |
| − | The following two papers describe rewriting and well-definedness issues that has to be accounted for:
| + | In addition we run a bug tracking system<ref>http://jira.cobra.cs.uni-duesseldorf.de/</ref> to document known bugs, workarounds and feature requests. |
| | | | |
| − | * [http://eprints.ecs.soton.ac.uk/18269/ Issam Maamria, Michael Butler, Andrew Edmunds, and Abdolbaghi Rezazadeh. On an Extensible Rule-based Prover for Event-B, ABZ'2010.]
| + | {{TODO}} |
| − | * [http://eprints.ecs.soton.ac.uk/21221/ Issam Maamria, Michael Butler. Rewriting and Well-Definedness within a Proof System.]
| |
| | | | |
| − | ===Improvements and Bugs=== | + | == Conclusion == |
| | + | {{TODO}} |
| | | | |
| − | See also the late [[Rule-based Prover Plug-in]], the last release of which was v0.3. The Theory plug-in starts at version v0.5.
| + | == References == |
| | + | <references/> |
