Search results

From Event-B
Jump to navigationJump to search
  • ...the critical shortcomings of the previous version: generation of unwieldy proof obligations (a large disjunction in a goal comprising several hundreds of t ...isprover for these kind of proofs) and it was decided that the approach to proof generation requires a complete redesign.
    4 KB (699 words) - 17:36, 3 December 2010
  • ...of the Flows plug-in. The primary reason to offer such a weak guarantee is proof effort required for stronger types of connectives. ...and the proof obligations related to flow appear in the list of the model proof obligations.
    4 KB (609 words) - 11:37, 8 January 2010
  • ...h could be customized and parameterized tactics to discharge some specific proof obligations. The user can furthermore share and backup these defined tactic ...time frame of ADVANCE, and increases the rate of automatically discharged proof obligations.
    4 KB (596 words) - 13:21, 18 July 2012
  • * [[Accessing Proof Obligations]] * [[Extending the Proof Manager]]
    2 KB (179 words) - 09:17, 20 November 2013
  • ...''Obligation Explorer'' displays the proof obligations together with their proof state. ...original views into a single one that would display modelling elements and proof obligations together. This new single view should also take advantage of th
    5 KB (842 words) - 18:35, 26 March 2010
  • ...resent systems at different abstraction levels and the use of mathematical proof to verify consistency between refinement levels.
    306 bytes (47 words) - 09:57, 4 March 2009
  • ...s an open and extensible toolset for Event-B specification, refinement and proof. The flash file system is a complex system that is challenging to specify a === Modelling and proof of a Tree-structured File System===
    4 KB (656 words) - 13:06, 18 November 2010
  • ...[Event-B]] that provides effective support for refinement and mathematical proof. The platform is open source, contributes to the Eclipse framework and is f
    491 bytes (67 words) - 14:18, 19 September 2011
  • ...owing them to provide as many tactic applications as they will for a given proof node, even they apply to the same predicate and at the same position. ====Fixing Proof Obligations====
    6 KB (915 words) - 16:57, 27 February 2014
  • [[Rodin Proof Tactics]]
    310 bytes (38 words) - 10:51, 27 October 2011
  • ...ow_to_extend_Rodin_Tutorial)|8 Generating proof obligations (Extending the Proof Obligation Generator)}}
    4 KB (487 words) - 14:27, 5 September 2013
  • === Theory and Proof === * [[Isabelle for Rodin]]: Prove proof obligations with Isabelle/HOL. Export proof obligations to Isabelle/HOL theories.
    5 KB (757 words) - 16:19, 13 February 2020
  • ** New proof obligations: '''PRV''', '''BND''', '''FINACT'''. === Proof Obligations ===
    6 KB (749 words) - 17:54, 21 March 2018
  • This plug-in provides an automated proof tactic based on the theorem prover [http://isabelle.in.tum.de/index.html Is It also allows users to export proof obligations to Isabelle theories for later inspection with Isabelle.
    9 KB (1,317 words) - 10:07, 29 April 2013
  • Bug 2999977: Can not save proof after functional image simplification
    651 bytes (84 words) - 18:41, 22 February 2011
  • ...(given properties about the constants) and Theorems (assertions requiring proof) may be attached to the ClassTypes. ClassTypes either define ‘carrier’
    606 bytes (84 words) - 20:27, 10 September 2008
  • ...ive laws result in a more natural and compact model with fewer and simpler proof obligations. ...sequential composition through refinement steps may result in unmanageable proof obligations. It is also more difficult to conduct subsequent refinement of
    5 KB (777 words) - 23:20, 6 December 2010
  • ...within the work package 3: ''Methods and Tools for Model Construction and Proof'', during the second period of the ADVANCE project (Sept 2012 - Sept 2013), ...work package tasks: general platform maintenance, improvement of automated proof, model checking, language extension, model composition and decomposition.
    2 KB (325 words) - 17:32, 29 November 2013
  • ...ule-based prover plug-in offers a uniform mechanism to define and validate proof rules which can then be used in proofs. *Theory construct, where rules are defined and validated by means of proof obligations. Defining a rule includes stating whether it should be applied
    5 KB (796 words) - 11:44, 8 January 2010
  • ...et shows that the addition of new tactics, and enhancement of the existing proof tooling is a continuous duty which has to be carried on until the end of th ...out in WP4. However, they may require some evolution of the modelling and proof tools to be performed within WP3.
    4 KB (677 words) - 16:41, 2 December 2013

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)