Search results

From Event-B
Jump to navigationJump to search

Page title matches

  • If you have suggestions or wishes regarding the documentation, please add them to the [[#Wish_List|Wish List]] at the end of this documen ...t using the tools without significant support." The effort to improve the documentation is now under way and will be coordinated by Düsseldorf.
    5 KB (720 words) - 11:28, 15 September 2011

Page text matches

  • == Rodin Platform User Documentation == [[Rodin User Manual]]
    310 bytes (38 words) - 10:51, 27 October 2011
  • == Event-B and Rodin Documentation Wiki == [[Rodin Platform|Rodin Platform User Support]]
    295 bytes (39 words) - 22:09, 4 July 2008
  • |title = User Documentation |content = Main Page/User Documentation
    2 KB (194 words) - 09:48, 19 May 2020
  • == User Documentation == You find the User Documentation in the form of a [[Requirements Tutorial]].
    2 KB (335 words) - 14:16, 3 December 2010
  • [[Category:User documentation]]
    322 bytes (43 words) - 15:26, 16 November 2009
  • [[Category:User documentation]]
    346 bytes (46 words) - 08:48, 27 October 2011
  • This page provides extensive documentation for the rule-based prover plug-in. == User Documentation ==
    2 KB (338 words) - 17:11, 9 July 2010
  • [[Category:User documentation]]
    390 bytes (45 words) - 15:20, 4 July 2013
  • [[Category:User documentation]]
    310 bytes (47 words) - 13:21, 2 May 2016
  • [[Category:User documentation]]
    410 bytes (54 words) - 08:45, 27 October 2011
  • [[Category:User documentation]]
    372 bytes (54 words) - 04:03, 12 October 2010
  • [[Category:User documentation]]
    285 bytes (38 words) - 20:26, 10 September 2008
  • * [[AnimB_start|User manual]] [[Category:User documentation]]
    632 bytes (85 words) - 01:04, 6 October 2010
  • This page provides some documentation for developers of the Theory plug-in. Documentation for users of the plug-in is available in [[Theory Plug-in|this page]]. ...et/p/forge/documentation/SFTP#for-managing-project-web-space Sourceforge's documentation]) and upload the files built previously (<code>p2.index</code>, <code>compo
    3 KB (394 words) - 07:15, 15 July 2021
  • [[Category:User documentation]]
    519 bytes (71 words) - 20:29, 10 September 2008
  • If you have suggestions or wishes regarding the documentation, please add them to the [[#Wish_List|Wish List]] at the end of this documen ...t using the tools without significant support." The effort to improve the documentation is now under way and will be coordinated by Düsseldorf.
    5 KB (720 words) - 11:28, 15 September 2011
  • [[Category:User documentation]]
    606 bytes (84 words) - 20:27, 10 September 2008
  • Here is the User Manual for the feature composition tool : [[Media:Feature_Composition_Tool_ [[User:Gondal|Ali Gondal]] at [[Southampton]] is in charge of the [[Feature Compos
    1 KB (192 words) - 10:15, 19 October 2010
  • [[Category:User documentation]]
    643 bytes (85 words) - 20:30, 10 September 2008
  • ...http://www.event-b.org Event-B.org] web site, including user and developer documentation available as a [http://wiki.event-b.org/index.php/Main_Page Wiki]. [[Category:User documentation]]
    2 KB (322 words) - 16:45, 20 April 2010
  • [[Category:User documentation]]
    617 bytes (79 words) - 08:47, 27 October 2011
  • ...php/Generic_Instantiation_Plug-in_User_Guide Generic Instantiation Plug-in User Guide]. ...ent-b.org/index.php/Generic_Instantiation_User_Guide Generic Instantiation User Guide].
    2 KB (232 words) - 15:23, 4 July 2013
  • ...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 t
    4 KB (648 words) - 14:52, 7 October 2013
  • ...e tool is very easy. To view the diagram of a particular Event-B project a user right-clicks on the project folder and from the context menu selects "Show ...nd for this reason manual moving of the elements and links is enabled to a user. Also, "Arrange All" button can be very helpful in situations when the layo
    2 KB (390 words) - 11:38, 16 November 2010
  • == Available Documentation == Documentation for composition is available in:
    5 KB (739 words) - 10:48, 23 September 2013
  • == Event-B Language Documentation == [[Category:User documentation]]
    3 KB (351 words) - 11:30, 23 January 2014
  • == Rodin Plug-in Documentation == * [[Decomposition Plug-in User Guide|Decomposition Plug-in]] allows the decomposition of Event-B machines/
    5 KB (757 words) - 16:19, 13 February 2020
  • [[Category:User documentation]]
    791 bytes (125 words) - 11:45, 14 January 2010
  • ...force a refresh of these views. We would like that these views behave more user-friendly and always display the expected information. ...ronment view is open and displays the type environment of the sequent. The user launches the post-tactic which removes the forall from the goal. One would
    4 KB (683 words) - 18:33, 16 December 2011
  • [[Category:User documentation]]
    1 KB (155 words) - 13:34, 2 May 2016
  • *The user interface was improved: using the form-based editor, if the symbol correspo In the latest version released (v1.2.3), the user's inputs and request were taken into account. In particular in terms of bet
    6 KB (891 words) - 17:21, 11 December 2012
  • ...del. Animation allows the user to validate if the model corresponds to the user's intentions. Model checking allows to check if the model contains errors a == Available Documentation ==
    6 KB (1,016 words) - 10:41, 23 September 2013
  • Furthermore, this view allows user to see together proof rules and corresponding sequents. [[Category:User documentation]]
    2 KB (299 words) - 12:50, 27 September 2011
  • ...one single plug-in. These approaches are indeed complementary and the end-user may take advantage of the former or of the latter, depending on the model, Choices, either related to the plug-in core or to the plug-in graphical user interface, have been made with the following constraints in mind:
    6 KB (825 words) - 13:27, 27 January 2010
  • [[Category:User documentation]]
    1 KB (203 words) - 11:28, 23 January 2014
  • [[Category:User documentation]]
    1 KB (174 words) - 12:43, 12 August 2009
  • [[Category:User documentation]]
    1 KB (177 words) - 13:06, 4 January 2013
  • Extensions and enhancements to the method documentation and tutorials are also supplied. It also presents the === Available Documentation ===
    6 KB (830 words) - 13:21, 7 October 2013
  • [[Category:User documentation|The Proving Perspective]] [[Category:User manual|The Proving Perspective]]
    2 KB (307 words) - 15:38, 29 November 2019
  • User's inputs and request were taken into account. In particular in terms of bet [[Category:User documentation]]
    3 KB (343 words) - 10:21, 25 November 2014
  • [[Category:User documentation]]
    1 KB (176 words) - 07:06, 1 August 2011
  • ...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 t
    4 KB (642 words) - 08:33, 29 June 2012
  • .../sourceforge.net/mailarchive/forum.php?forum_name=rodin-b-sharp-user Rodin user] [http://sourceforge.net/mailarchive/forum.php?forum_name=rodin-b-sharp-co === Documentation (not discussed ===
    4 KB (671 words) - 12:45, 12 August 2009
  • ...llocated to which sub-component. For the share variable decomposition, the user selects which events with be part of which sub-component. The rest of the s = Available Documentation =
    5 KB (780 words) - 11:22, 21 December 2010
  • ...We will also provide templates as needed, to simplify the creation of the documentation. The Reference Section will be the most comprehensive part of the documentation. It will consist of a number of chapters. At this point we see at least t
    9 KB (1,421 words) - 12:41, 8 December 2011
  • Beyond that, any user registered on SourceForge may record any encountered bug on the Rodin platf = Available Documentation =
    7 KB (963 words) - 11:30, 27 January 2010
  • * Documentation
    9 KB (1,423 words) - 16:28, 14 November 2011
  • [[Category:User documentation|Proof Obligation Names]] [[Category:User manual|Proof Obligation Names]]
    4 KB (575 words) - 15:09, 15 September 2011
  • [[User:Gondal|Ali Gondal]] at [[Southampton]] is working on the [[Feature Modellin [[Category:User documentation]]
    2 KB (320 words) - 07:06, 1 August 2011
  • ...of the element. This contains details which are otherwise hidden from the user. ...ditor view shows all the hidden details that are not normally visible to a user. (The tree shows the model element selected in the outline view, i.e. not a
    3 KB (507 words) - 07:02, 1 August 2011
  • ...ated in the ''latex'' directory can be modified to change the style of the documentation. Since B2Latex 0.6.1, this file won't be overwritten if already exists, so no user modifications are accidentally lost.
    4 KB (718 words) - 17:22, 8 July 2016
  • ...predicates and algebraic types. Along with these additional notations, the user can also define new proof rules (prover extensions). ...ies are deployed to the current workspace (i.e., Workspace Scope), and the user can use any defined extensions in any project within the workspace.
    7 KB (1,095 words) - 14:40, 21 December 2010
  • The purpose of the proof purger is to allow the user to delete obsolete proofs. [[Category:User documentation]]
    2 KB (400 words) - 10:20, 27 October 2011
  • ...nd parameterized tactics to discharge some specific proof obligations. The user can furthermore share and backup these defined tactics using the provided i ...n the tactic profile editor as well as an import/export feature. Indeed, a user that elaborates a good profile for a certain proof pattern is now able to s
    4 KB (596 words) - 13:21, 18 July 2012
  • ...up for running the transformations, and provides a simple library handling user input of Event-B elements such as machines, events, variables etc. ...psilonBook.pdf The Epsilon Book]. The full list of operations for handling user input and modifying Event-B elements can be found in [[Transformation_patte
    7 KB (1,011 words) - 13:08, 1 July 2013
  • ...ourceforge.net/projects/rodin-b-sharp/files/Core_Rodin_Platform</ref>. The documentation of the DEPLOY tools is available from two sites: ...enhanced proving experience, and proving ability with the introduction of user customizable and parametrizable tactic profiles.
    3 KB (500 words) - 09:18, 23 April 2012
  • [[Category:User documentation]]
    2 KB (281 words) - 15:57, 11 September 2017
  • * documentation is up to date for /org.rodinp.platform/html/root.html * generated documentation matches latest wiki sources for <tt>org.eventb.keyboard/doc</tt>
    6 KB (928 words) - 15:50, 11 September 2020
  • Please have a look also at the [[Rodin Editor User Guide]]. ...click, or where my text caret is.''' The caret position, also set when the user left-clicks in the editor, is the base for component modifications:
    4 KB (744 words) - 17:20, 3 June 2013
  • === Event-B User Interface === The Event-B User Interface of the Roding Platform has two major components that are concerne
    8 KB (1,260 words) - 12:45, 30 July 2015
  • 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 Rodi
    16 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 fo
    5 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
  • ...not strictly necessary but it can be used to distinguish projects that the user has created from ones that have been created programmatically). ...(true); // mark the project as derived (this could be used to distinguish user editable projects
    6 KB (784 words) - 15:19, 21 August 2023
  • * Prepare basic documentation for users. ...the Rodin platform uses self-made automatic theorem provers to support the user in proving.
    10 KB (1,629 words) - 12:50, 12 August 2009
  • ...orm_Maintenance#Available_Documentation</ref> and the SourceForge<ref name=documentation>http://wiki.event-b.org/index.php/D45_General_Platform_Maintenance#Availabl :*A Handbook to complete and enhance the existing documentation.
    35 KB (5,228 words) - 10:12, 23 April 2012
  • [[Category:User documentation]]
    3 KB (469 words) - 12:38, 17 April 2009
  • ...> packaged with the Rodin platform. This makes the tests closer to the end-user experience, and therefore more meaningful. [[Category:Developer documentation]]
    4 KB (652 words) - 08:48, 6 June 2014
  • [[Category:User documentation]]
    4 KB (559 words) - 12:43, 12 August 2009
  • ...[mailto:lvoisin@users.sourceforge.net Laurent Voisin] || generates a Latex documentation of the Event-B | [[Image:DecompositionPlug-in_logo.png|30px]] || [[Decomposition Plug-in User Guide | Decomposition]] || 1.3.1 || <span style="color:#8B4513"> not checke
    9 KB (1,244 words) - 13:52, 1 April 2022
  • [[Category:User documentation]]
    4 KB (535 words) - 14:58, 10 December 2012
  • [[Category:User documentation]]
    4 KB (535 words) - 14:56, 10 December 2012
  • ''For user support, see [[SMT Solvers Plug-in]]'' [[Category:Developer documentation]]
    4 KB (691 words) - 14:34, 19 May 2014
  • ...teps as possible automatically or at least supports the developer wherever user interaction is required. = Available Documentation =
    6 KB (1,034 words) - 14:43, 27 January 2010
  • [[Category:User documentation|The Proving Perspective]] [[Category:User manual|The Proving Perspective]]
    14 KB (2,054 words) - 16:50, 19 February 2024
  • [[Category:User documentation]]
    4 KB (550 words) - 10:39, 25 November 2014
  • * various simplifications of the user interaction * documentation
    9 KB (1,317 words) - 10:07, 29 April 2013
  • This tutorial walks the user through using the Systerel Requirements Plug-In for Rodin. This Plug-In al [[Category:User documentation]]
    7 KB (995 words) - 15:44, 25 February 2009
  • ...ling component that is generated programmatically, at the direction of the user. The Tasking Development consists of a number of machines (and perhaps asso [[Category:User documentation]]
    7 KB (1,009 words) - 10:59, 26 January 2011
  • # User selects element to be renamed at the Event-B Explorer # User introduces new element name in the first page of the wizard. Then click in
    11 KB (1,773 words) - 07:41, 12 January 2016
  • [[Category:User documentation]]
    5 KB (720 words) - 15:20, 4 July 2013
  • :#* Report to user if translation didn't proceed due to model validator - previously, it was n :#* Preference for line routing style for each diagram type - allows the user to choose whether to use rectilinear or oblique line routing for each diagr
    9 KB (1,382 words) - 11:05, 27 January 2011
  • ...Any modification to this page shall be announced on the [[#Mailing_lists |User]] mailing list!</font> ...\;\; \finite\,(T)}{\textbf{H} \;\;\vdash \;\; \finite\,(S)}</math> || the user has to write the set corresponding to <math>T</math> in the editing area of
    36 KB (5,611 words) - 10:22, 1 February 2024
  • ...e following, which should be installed if the features are required by the user for editing: We released a new version of the code generator on 30-11-2011, and updated documentation.
    17 KB (2,568 words) - 09:03, 19 October 2015
  • ...f [http://en.wikipedia.org/wiki/Wizard_%28software%29 wizard], guiding the user step by step toward ''test suite generation'', starting with the most abstr The first step requires the user to specify the value for the ''maximum sequence length'' constant (<math>l<
    9 KB (1,434 words) - 06:45, 6 April 2012
  • ...ns in a uniform and effective fashion. It is uniform because it offers the user (we shall call a theory developer) the possibility to develop and validate =Available Documentation=
    5 KB (796 words) - 11:44, 8 January 2010
  • ...of a loop in the dependencies, an internal error would be reported to the user (with details of the loop in the workspace log). [[Category:Developer documentation]]
    5 KB (764 words) - 15:49, 19 April 2011
  • [[Category:User documentation]]
    6 KB (895 words) - 06:12, 8 September 2011
  • ...ss subgoals, thus rendering well-definedness almost transparent to the end-user. For PP and newPP the user can still manually select the hypotheses he considers relevant, but that is
    11 KB (1,699 words) - 15:25, 27 January 2011
  • ...akes it easier to locate the file from the terminal command line since the user home directory is the default local directory in Terminal) [[Category:Developer documentation|*Index]]
    10 KB (1,436 words) - 09:06, 27 May 2015
  • There is a documentation plugin in the EMF translator source code that describes the necessary exten * ---user entered items---
    13 KB (1,988 words) - 11:01, 30 May 2020
  • ...t visible as a tab on the top right-hand corner of the main interface, the user can switch to it via "Window -> Open Perspective". ...at is not discharged yet by the prover. Instead, it has been "seen" by the user who decided to postpone the proof. Marking nodes as "reviewed" is very conv
    27 KB (4,348 words) - 08:56, 26 September 2011
  • ...t visible as a tab on the top right-hand corner of the main interface, the user can switch to it via "Window -> Open Perspective". ...at is not discharged yet by the prover. Instead, it has been "seen" by the user who decided to postpone the proof. Marking nodes as "reviewed" is very conv
    27 KB (4,348 words) - 18:45, 28 September 2011
  • ...e an error occurs during the decomposition, a message is displayed and the user is asked to delete the possible created files. The error will be displayed ...elements that belong to different sub-components. So solve this issue, the user must explicitly separate the elements (by a further refinement or introduci
    17 KB (2,521 words) - 15:25, 4 July 2013
  • ...e inclusion of more invariants (from the included machines) depends on the user’s choice on ''Includes''. The defined invariants on the composed machine [[Category:User documentation]]
    7 KB (1,161 words) - 11:02, 4 July 2013
  • ...validation algorithm now can animate a range of refinements together. The user can decide which levels are to be animated together. User experience is also improved, as he or she can inspect also the abstract var
    17 KB (2,580 words) - 15:55, 28 January 2010
  • [[Category:User documentation|The Proving Perspective]] [[Category:User manual|The Proving Perspective]]
    33 KB (4,853 words) - 16:17, 8 March 2024
  • ...nslation from Event-B into its internal representation in order to support user defined operators from the Theory plug-in. The work on the feature is curre = Available Documentation =
    7 KB (1,025 words) - 21:35, 20 April 2012
  • [[Category:User documentation|The Proving Perspective]] [[Category:User manual|The Proving Perspective]]
    29 KB (4,188 words) - 14:33, 13 April 2023
  • = Available Documentation = We have updated the documentation<ref>http://wiki.event-b.org/index.php/Code_Generation_Activity</ref>, inclu
    12 KB (1,818 words) - 08:31, 20 April 2012
  • ...ironment}}: in case you will not modify the type environment and allow the user to provide the most convenient type for him. You must not later cast the pa Please refer to the documentation of the extension point for further details on how to implement things.
    17 KB (2,614 words) - 16:25, 14 February 2014
  • ...ava code is produced from an intermediate model that is not visible to the user. The Common Language model (CLM), is generated from the Tasking Event-B by [[Category:User documentation]]
    11 KB (1,714 words) - 12:41, 2 September 2013
  • ...on for use when displaying the metadata about the content extension to the user. ...e active by default. Each content extension may be turned on or off by the user. The active state is differentiated from the visible state. See <tt>org.ecl
    20 KB (2,461 words) - 16:33, 24 May 2010
  • These changes are described from a user point of view in [[Changes to the Mathematical Language of Event-B]]. ...ath> are changed so that they take generic operators as input (see ppTrans documentation, rules IR39, IR43, IR44).
    14 KB (2,104 words) - 09:40, 11 May 2009
  • A Tasking Development is generated programmatically, at the direction of the user; the Tasking Development consists of a number of machines (and perhaps asso ...ided that we would produce a PrettyPrinter for the Ada code. This allows a user to cut and paste the Ada source code from the PrettyPrinter window to an Ad
    15 KB (2,298 words) - 15:08, 27 January 2011
  • ...event-b.org/current/html/preferences.html the preference page of the Rodin User’s Handbook v.2.4].<br> ...T auto-tactic profile (available since version 0.8.0 of the plug-in), or a user-defined profile using SMT solvers.
    17 KB (2,538 words) - 15:41, 2 October 2017
  • [[Category:User documentation]]
    9 KB (1,528 words) - 08:43, 2 September 2013
  • [[Category:User documentation]]
    11 KB (1,713 words) - 20:07, 18 April 2010
  • ...Y lifetime, a new way to manage tactics has been implemented. In fact, the user is now able to define various types of tactics called 'profiles' which coul ...rease directly the number of automatically discharged POs aims to help the user to interactively discharge them and spare his time.
    21 KB (3,334 words) - 21:20, 20 April 2012
  • = Available Documentation = ...mproving Testing of Enterprise Systems by Model-Based Testing on Graphical User Interfaces. In Proc. of the Satellite Workshops of ECBS'10. pp. 352-357, IE
    8 KB (1,215 words) - 15:14, 27 January 2011
  • [[Category:User documentation]]
    14 KB (1,930 words) - 12:58, 21 July 2010
  • [[Category:User documentation]]
    12 KB (1,741 words) - 08:25, 14 December 2010
  • Tactic providers allow to define how manual tactics contribute to the User Interface. [[Category:Developer documentation]]
    17 KB (2,378 words) - 09:48, 17 June 2010
  • [[Category:Plugin]] [[Category:User documentation]]
    13 KB (2,134 words) - 08:04, 6 October 2015
  • First, this can give the user a deeper insight into how the model behaves and how the refinement levels a ...be discharged. But without an animator it is not always easy to see for an user if this is caused by the complexity of the proof or by an error.
    16 KB (2,553 words) - 15:12, 27 January 2011
  • Each view generates a number of proof obligations to be discharged by a user. These POs formally ensure that the mode/FT view is actually a view on the [[Category:User documentation]]
    21 KB (3,472 words) - 20:32, 26 June 2015
  • ...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 fo ...was to make a simple to use environment that can be used by a non-Event-B user (e.g. requirements engineer, fault tolerance specialist), yet provides the
    19 KB (2,944 words) - 15:28, 27 January 2011