Search results
From Event-B
Jump to navigationJump to searchCreate the page "Design" on this wiki! See also the search results found.
- [[Category:Design]]10 KB (1,604 words) - 09:19, 27 October 2011
- ...efinement level we introduce sensing and actuation which are considered as design steps. Here sensing involves polling the state of increase/decrease buttons7 KB (1,119 words) - 10:06, 12 May 2011
- * Design an EMF meta model (ecore) of your extension's abstract syntax. The model sh7 KB (1,094 words) - 10:50, 22 January 2010
- [[Category:Design]]9 KB (1,478 words) - 10:33, 27 October 2011
- The design of the ''Membership Goal'' reasoner<ref>http://wiki.event-b.org/index.php/M7 KB (1,145 words) - 10:05, 8 October 2013
- [[Category:Work in progress]] [[Category:Design]]8 KB (1,347 words) - 13:07, 21 July 2010
- One important design consideration was to be able to re-use the Rodin formula syntax and parser.8 KB (1,257 words) - 15:56, 28 January 2010
- ...hension, cannot be used to enter absolute values (''in fact, as in the new design the pipe used in set comprehension is only a syntaxic sugar, the same symbo [[Category:Design]]19 KB (2,883 words) - 18:20, 17 March 2014
- ...ndex.php/Constrained_Dynamic_Parser#Design_Alternatives ''Generic Parser's Design Alternatives'' ] ...ing modularisation a designer needs to identify a self-contained part of a design and captures it in an independent ''module''. A module is an Event-B develo35 KB (5,228 words) - 10:12, 23 April 2012
- [[Category:Design]]11 KB (1,773 words) - 07:41, 12 January 2016
- [[Category:Work in progress]] [[Category:Design]]18 KB (2,643 words) - 12:41, 12 August 2009
- Bug 2864985: Problem with Design of EventBRoot9 KB (1,298 words) - 10:06, 28 July 2010
- ...">[http://eprints.ecs.soton.ac.uk/16910/2/marktoberdorf2.pdf ''Incremental Design of Distributed Systems with Event-B'']</font>, in Marktoberdorf Summer Scho [[Category:Design]]43 KB (6,950 words) - 09:48, 27 October 2011
- * a graphical animator based on SWT that allows the user to design his/her own animations easily within the tool12 KB (1,869 words) - 16:35, 18 March 2014
- [[Category:Design]]14 KB (2,104 words) - 09:40, 11 May 2009
- [[Category:Design]]17 KB (2,521 words) - 15:25, 4 July 2013
- erroneous design decisions that were taken in previous Rodin releases.17 KB (2,614 words) - 16:25, 14 February 2014
- ...used phenomenon, or the fact that domain properties, requirement items and design decisions may only be expressed referring to phenomena that are visible in16 KB (2,554 words) - 14:05, 8 October 2013
- * Since extensibility is a very important design principle for reaching the level of an industrial strength tool we pointed16 KB (2,553 words) - 15:12, 27 January 2011
- The main objective in the tool design was to make a simple to use environment that can be used by a non-Event-B u19 KB (2,944 words) - 15:28, 27 January 2011