Search results
From Event-B
Jump to navigationJump to searchCreate the page "User Documentation" on this wiki! See also the search results found.
- Animation allows the user to validate if the model corresponds to the user's intentions. = Available Documentation =11 KB (1,711 words) - 09:47, 26 June 2012
- ...discharged using the auto prover, else there is no mark, meaning that the user had to edit the proof by hand (even partially). [[Category:User documentation]]3 KB (457 words) - 10:43, 18 March 2010
- [[Category:User documentation]]2 KB (287 words) - 08:56, 27 September 2010
- ...he only place where this information was present was in either the plug-in documentation (if present) or buried into the plug-in code. Moreover, if by chance a plug ...a few buttons outside the editing area. This enhancement originated from a user who has contributed a patch for it. The stability of the newer generic Rodi16 KB (2,554 words) - 14:05, 8 October 2013
- Eclipse which is more user-friendly and easy to use. This tool is available from (free registration re [[Category:Developer documentation]]2 KB (337 words) - 11:03, 10 November 2008
- [[Category:User documentation]]2 KB (276 words) - 22:12, 30 September 2020
- ...olymorphic theorems. The [http://wiki.event-b.org/images/Theory_Plugin.pdf user manual] provides a guide to developing and using theories. ===User Manual===7 KB (958 words) - 14:53, 14 June 2021
- ...ad to be made. In all these instances, meaningful error messages guide the user, and the editor attempts to be as unobtrusive as possible. = Available Documentation =8 KB (1,257 words) - 15:56, 28 January 2010
- ==User guide== ...[http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.user/concepts/cworkset.htm eclipse help].5 KB (842 words) - 18:35, 26 March 2010
- ...tions. Searching for a counterexample can be done effortlessly and without user interaction. If successful, the futility of a manual proof attempt is detec == Available Documentation ==7 KB (1,145 words) - 10:05, 8 October 2013
- select relevant hypotheses for a proof as opposed to the user doing this [[Category:User documentation]]4 KB (569 words) - 07:04, 1 August 2011
- ...]] and the corresponding [[Mathematical_Language_Evolution_Design|design]] documentation. ...a model can be tagged as generated by a tool, in order to prevent the end-user from directly editing them (and their descendants).6 KB (915 words) - 16:57, 27 February 2014
- The user must give a value for each constants. A constant value is set in the contex [[Category:User documentation]]4 KB (679 words) - 14:59, 16 September 2009
- [[Category:User documentation]]4 KB (630 words) - 20:28, 10 September 2008
- == Available Documentation == ...Both the Rodin handbook and the Event-B wiki represent the main source of documentation about Event-B and the Rodin toolset.20 KB (3,030 words) - 13:18, 18 July 2012
- ...experience. The whole performance was enhanced by core implementation and user interface refactorings. Improvements made to the proving experience will be This section concerns the actual editors that user work with to view and modify models.13 KB (1,991 words) - 20:57, 20 April 2012
- ==9th Rodin User and Developer Workshop== The 9th Rodin User and Developer Workshop, 8 June, 2021, Ulm, Germany (Virtual)4 KB (595 words) - 09:41, 29 June 2021
- A user builds and checks a Mode/FT view in the diagram editor, makes a link to an ...ilitate the development by leaving the Event-B modelling activity with the user. On the fault tolerance side, we are aware of the work on ProR framework fo5 KB (816 words) - 17:37, 3 December 2010
- [[Category:User documentation]]3 KB (445 words) - 07:03, 1 August 2011
- [[Category:User documentation|The Proving Perspective]] [[Category:User manual|The Proving Perspective]]10 KB (1,400 words) - 16:39, 12 May 2014
