Search results

From Event-B
Jump to navigationJump to search

Page title matches

  • [[Category:Design]]
    1,001 bytes (119 words) - 14:53, 21 January 2010
  • [[Category:Design]]
    3 KB (505 words) - 12:54, 12 August 2009
  • [[Category:Design]]
    2 KB (254 words) - 12:54, 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
  • The clean separation between modelling and proving looked good during paper design. However, users reported that they were constantly switching between the t The Single View Design uses the [http://wiki.eclipse.org/index.php/Common_Navigator_Framework Comm
    5 KB (842 words) - 18:35, 26 March 2010
  • [[Category:Design]]
    2 KB (291 words) - 09:27, 4 March 2009
  • ===Extending Single View Design=== Single View Design uses the [http://wiki.eclipse.org/index.php/Common_Navigator_Framework Comm
    4 KB (521 words) - 18:36, 26 March 2010
  • [[Category:Design]]
    14 KB (2,104 words) - 09:40, 11 May 2009

Page text matches

  • #REDIRECT [[Proof Purger Design]]
    33 bytes (4 words) - 15:59, 6 January 2009
  • #REDIRECT [[Proof Skeleton Design]]
    35 bytes (4 words) - 16:56, 6 January 2009
  • [[Category:Design proposal]]
    415 bytes (64 words) - 10:36, 25 August 2009
  • * [[Extending Single View Design]] * [[:Category:Design proposal]]
    2 KB (179 words) - 09:17, 20 November 2013
  • A first design proposal is also drafted. === Requirements Exported by the Current Language Design ===
    3 KB (440 words) - 09:10, 1 March 2010
  • ...ng mathematical formulas. These flaws were either present in the original design of the library or were overlooked when introducing mathematical extensions. [[Category:Design proposal]]
    1 KB (179 words) - 15:34, 22 July 2012
  • ===Extending Single View Design=== Single View Design uses the [http://wiki.eclipse.org/index.php/Common_Navigator_Framework Comm
    4 KB (521 words) - 18:36, 26 March 2010
  • ...scribe what result shall be produced by the tool. Finally, we describe the design retained for development. == Design for Improved Generation ==
    4 KB (617 words) - 09:43, 19 June 2012
  • This page describes the design of a tactic requested here : [https://sourceforge.net/tracker/index.php?fun = Design Decision =
    5 KB (824 words) - 16:05, 18 March 2014
  • == Design Decisions == ...UI, there is the notion of an active part (i.e., view or editor). The best design is then to refresh the Rule Details and Type environment views based on the
    4 KB (683 words) - 18:33, 16 December 2011
  • ...[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
  • [[Category:Design]]
    726 bytes (102 words) - 12:02, 12 August 2009
  • ==Design== [[Category:Design]]
    4 KB (599 words) - 15:56, 28 January 2009
  • In the original database design, file elements are hybrid as they fall in both It was found out at the end of the Rodin project, that this design decision was
    6 KB (897 words) - 11:47, 29 January 2009
  • {{see also|Undo Redo Design|l1=Undo/Redo design}} ...f Event-B]] and the corresponding [[Mathematical_Language_Evolution_Design|design]] documentation.
    6 KB (915 words) - 16:57, 27 February 2014
  • The clean separation between modelling and proving looked good during paper design. However, users reported that they were constantly switching between the t The Single View Design uses the [http://wiki.eclipse.org/index.php/Common_Navigator_Framework Comm
    5 KB (842 words) - 18:35, 26 March 2010
  • [[Category:Design proposal]]
    851 bytes (124 words) - 12:53, 26 March 2010
  • ...(smart completion, renaming, text editing, etc), decomposition support and design-pattern management. * Choices / decisions. The decisions (e.g. design decisions) are justified.
    3 KB (399 words) - 11:20, 27 January 2010
  • ...models, for helping the development process. The objective in introducing design patterns within formal methods in general, and in Event-B in particular, is ...and management for projects of industrial size mentioned above or even the design of extension capabilities. Extension capabilities became a major concern si
    13 KB (1,991 words) - 20:57, 20 April 2012
  • ...the addition of the Generic Instantiation Plug-in (previously mentioned as Design Pattern Management). * Choices / decisions. The decisions (e.g. design decisions) are justified.
    3 KB (500 words) - 09:18, 23 April 2012
  • [[Category:Design]]
    1,001 bytes (119 words) - 14:53, 21 January 2010
  • This design document describes how this has been implemented in a better way in the cor [[Category:Design]]
    4 KB (692 words) - 15:06, 20 November 2013
  • [[Category:Design]]
    2 KB (232 words) - 15:23, 4 July 2013
  • [[Category:Design]]
    2 KB (254 words) - 12:54, 12 August 2009
  • ...://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
  • * '''AWE''' - Co-Design Architecture (CODA) ...ervices for connected embedded systems, is applying the Rodin tools to the design of software for a simple medical device. The aim is to use the evidence pro
    5 KB (718 words) - 11:40, 23 October 2015
  • * Design a subsystem for Rodin that will realize the selected scenario(s) and implem [[Category:Design proposal]]
    4 KB (670 words) - 14:38, 29 January 2009
  • === 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 objective
    10 KB (1,629 words) - 12:50, 12 August 2009
  • [[Category:Design]]
    2 KB (291 words) - 09:27, 4 March 2009
  • * [[Rodin Index Design]] * [[Proof Purger Design|Proof Purger]] allows to delete unused proofs.
    8 KB (1,260 words) - 12:45, 30 July 2015
  • ...for each tool extension and improvement are expressed. The decisions (e.g. design decision) are reported.
    2 KB (325 words) - 17:32, 29 November 2013
  • [[Category:Design]]
    2 KB (365 words) - 12:52, 12 August 2009
  • ...for each tool extension and improvement are expressed. The decisions (e.g. design decision) are related.
    2 KB (371 words) - 16:27, 13 July 2012
  • [[Category:Design proposal]]
    2 KB (335 words) - 14:16, 3 December 2010
  • This page describes the design of a tactic replacing a predicate <math> P </math> in either a hypothesis o = Design Decision =
    10 KB (1,784 words) - 16:04, 18 March 2014
  • ...in the paper [http://www.springerlink.com/content/d088h53531x7226j "Using Design Patterns in Formal Methods: An Event-B Approach"].
    6 KB (1,034 words) - 14:43, 27 January 2010
  • ...ation could also be implemented by a sequence of Prolog Queries. This is a design decision that depends on whether we want to reuse parts of the sequence or
    3 KB (325 words) - 08:20, 4 February 2009
  • for the system. It proved to be a bad design choice and it was a burden for behaviour or on the design of the railway network.
    6 KB (967 words) - 12:57, 28 October 2008
  • [[Category:Design]]
    3 KB (343 words) - 10:21, 25 November 2014
  • [[Category:Design]]
    3 KB (444 words) - 16:57, 27 February 2014
  • This page describes the design of the reasoner MembershipGoal and its associated tactic MembershipGoalTac. = Design Decision =
    19 KB (3,362 words) - 13:50, 5 June 2014
  • ...Rodin Index Design]] for more general considerations about the purpose and design. [[Category:Design]]
    10 KB (1,541 words) - 17:41, 9 March 2009
  • A first design proposal is also drafted. === Requirements Exported by the Current Language Design ===
    27 KB (3,967 words) - 13:21, 15 February 2010
  • This page describes the design of a tactic for putting a sequent in Negation Normal Form, as requested by
    3 KB (596 words) - 16:48, 13 April 2011
  • * Choices / decisions. The decisions (e.g. design decisions) are justified.
    3 KB (415 words) - 17:03, 24 November 2010
  • The major design decision concerned how to carry out the process of fine tuning. The major design decision concerned the logic in which the semantics of Event-B's logic is f
    11 KB (1,699 words) - 15:25, 27 January 2011
  • [[Category:Design]]
    3 KB (505 words) - 12:54, 12 August 2009
  • [[Category:design proposal]]
    3 KB (496 words) - 12:58, 12 August 2009
  • * Design an EMF meta model (ecore) of your extension's abstract syntax. The model sh
    6 KB (506 words) - 12:00, 25 November 2009
  • ...ion has experimented several notation and methodological alternatives. The design has now been finalised and an implementation has been achieved. State-machi ...the meta-model in as generic a manner as possible. A driving factor in the design was to support both project level tools and component level tools. The latt
    8 KB (1,224 words) - 15:53, 28 January 2010
  • {{TODO}} REWORK: rethink the specification, avoid regex, new design based on a [http://en.wikipedia.org/wiki/Trie Trie] data structure. [[Category:Design]]
    9 KB (1,367 words) - 11:59, 23 June 2014
  • ...from UML-B state-machine subset, with incorporated animation support. This design was successfully implemented together with ProB and Rodin UI extensions int
    9 KB (1,382 words) - 11:05, 27 January 2011
  • ...TextEditor. It shows its EBNF, [[#Explanation|explains]] some details and design decisions and gives some [[#Examples|examples]].
    4 KB (559 words) - 12:43, 12 August 2009
  • [[Category:Design proposal]]
    4 KB (704 words) - 10:17, 5 December 2012
  • '''Model decomposition''' is a powerful technique to scale the design of large and complex systems. It enables first developers to separate compo
    5 KB (739 words) - 10:48, 23 September 2013
  • * Generic Parser's Design Alternatives.<ref>http://wiki.event-b.org/index.php/Constrained_Dynamic_Par
    4 KB (642 words) - 08:33, 29 June 2012
  • [[Category:Design proposal]]
    4 KB (660 words) - 16:36, 18 March 2014
  • [[Category:Design]]
    4 KB (650 words) - 16:07, 15 February 2013
  • * Generic Parser's Design Alternatives.<ref>http://wiki.event-b.org/index.php/Constrained_Dynamic_Par
    4 KB (648 words) - 14:52, 7 October 2013
  • [[Category:Design proposal]]
    10 KB (1,685 words) - 11:50, 26 February 2013
  • [[Category:Design]]
    5 KB (797 words) - 10:29, 24 October 2011
  • ...es Sharp, Michael Butler, John Colley, Andy Edmunds, Colin Snook: ''The Co-Design Architecture (CODA) Methodology and Plug-in Tool, Progress Update''
    4 KB (521 words) - 13:15, 13 June 2013
  • improving existing tools, while others needed a full design and development of
    5 KB (789 words) - 11:41, 27 January 2010
  • ...010-sld-robinson.pdf ''Reflections on the teaching of System Modelling and Design''], Ken Robinson
    5 KB (716 words) - 09:28, 22 November 2010
  • * Design/architectural decision. It applies in particular when it is noticed that it
    6 KB (825 words) - 13:27, 27 January 2010
  • '''Model decomposition''' is a powerful technique to scale the design of large and complex systems. It enables first developers to separate compo
    6 KB (891 words) - 17:21, 11 December 2012
  • [[Category:Design proposal]]
    5 KB (764 words) - 15:49, 19 April 2011
  • ...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 phenome
    20 KB (3,030 words) - 13:18, 18 July 2012
  • [[Category:Design proposal]]
    6 KB (1,046 words) - 10:34, 27 October 2011
  • ...ng the master's thesis [http://e-collection.ethbib.ethz.ch/view/eth:41612 "Design Patterns in Event-B and Their Tool Support“], the proofs of the pattern c
    17 KB (2,670 words) - 15:07, 24 January 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
  • The main objective in the tool design was to make a simple to use environment that can be used by a non-Event-B u
    5 KB (816 words) - 17:37, 3 December 2010
  • ...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
  • [[Category:Design]]
    7 KB (953 words) - 09:31, 10 March 2009
  • The primary objective in the tool design was to provide a simple to use tool that could be used by a non-expert mode
    6 KB (921 words) - 11:43, 8 January 2010
  • Due to some design decisions and its combination with the Rodin platform the TextEditor comes
    6 KB (945 words) - 12:22, 27 January 2015
  • This paragraph shall also summarize the decisions (eg. design decisions) and justify them. Thus, it may present the studied solutions, th
    6 KB (830 words) - 13:21, 7 October 2013
  • [[Category:Design]]
    8 KB (1,284 words) - 18:33, 30 January 2012
  • ...0 || Formalisation of Self-Organizing Multi-Agent Systems with Event-B and Design Patterns [http://wiki.event-b.org/images/ZGraja-RodinWorkshop2014.pdf]
    8 KB (1,073 words) - 06:13, 24 June 2014
  • ...ndex.php/Constrained_Dynamic_Parser#Design_Alternatives ''Generic Parser's Design Alternatives'' ]
    7 KB (1,095 words) - 14:40, 21 December 2010
  • [[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 buttons
    7 KB (1,119 words) - 10:06, 12 May 2011
  • * Design an EMF meta model (ecore) of your extension's abstract syntax. The model sh
    7 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/M
    7 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 develo
    35 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 EventBRoot
    9 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 tool
    12 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 in
    16 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 pointed
    16 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 u
    19 KB (2,944 words) - 15:28, 27 January 2011

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