Search results
From Event-B
Jump to navigationJump to searchCreate the page "Computer-aided design" on this wiki! See also the search results found.
- ...[http://wiki.event-b.org/index.php/Image:SM%26D-KAR.pdf System Modelling & Design Using Event-B.] ===3 KB (351 words) - 11:30, 23 January 2014
- ...://wiki.event-b.org/images/Rodin-workshop-article.pdf System Modelling and Design: Refining Software Engineering] ...fang Yuan, [http://wiki.event-b.org/images/soton-workshop.pdf Quantitative Design Decisions Measurement using Formal Method]5 KB (766 words) - 09:59, 21 September 2011
- === Tool Support for Design Patterns === ...mportant aspect of the Event-B method. The background theoretical work for design patterns in Event-B has been done as part of a master thesis. The objective10 KB (1,629 words) - 12:50, 12 August 2009
- ...e elements, based on their type. In hindsight, we are taking here the same design decision we took for the event-B tools when defining the granularity of sta [[Category:Design]]14 KB (2,204 words) - 12:58, 12 October 2009
- ...ability issues occured at some point when feature addition was favoured to design refactorings. As the DEPLOY project was nearing its end, it appeared manda ...ressed referring to phenomena that are visible in the environment, whereas design decisions and plaform properties may only be expressed referring to phenome20 KB (3,030 words) - 13:18, 18 July 2012
- ...e modeller attention on modal specifics and thus decreases the chance of a design fault. It generally fits into the framework of architectural descriptions u ...ay modes and transitions are mapped into model events and thus cross-check design decisions in either part.21 KB (3,472 words) - 20:32, 26 June 2015
- * 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
- ...40. Springer, 2008.</ref> and Vampire<ref>A. Riazanov and A. Voronkov. The design and implementation of Vampire. AI Communications, 15(2-3):91-110, 2002.</re21 KB (3,334 words) - 21:20, 20 April 2012
- ...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