Search results

Create the page "Design" on this wiki! See also the search results found.

Page title matches

• Auto-Completion Design
  [[Category:Design]]
  1,001 bytes (119 words) - 14:53, 21 January 2010
• Proof Purger Design
  [[Category:Design]]
  3 KB (505 words) - 12:54, 12 August 2009
• Proof Skeleton Design
  [[Category:Design]]
  2 KB (254 words) - 12:54, 12 August 2009
• Rodin Index Design
  ...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
• Single View Design
  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
• Undo Redo Design
  [[Category:Design]]
  2 KB (291 words) - 09:27, 4 March 2009
• Extending Single View Design
  ===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
• Mathematical Language Evolution Design
  [[Category:Design]]
  14 KB (2,104 words) - 09:40, 11 May 2009

Page text matches

• Proof Purger
  #REDIRECT [[Proof Purger Design]]
  33 bytes (4 words) - 15:59, 6 January 2009
• Proof Skeleton
  #REDIRECT [[Proof Skeleton Design]]
  35 bytes (4 words) - 16:56, 6 January 2009
• Requirements for merging models
  [[Category:Design proposal]]
  415 bytes (64 words) - 10:36, 25 August 2009
• Developer Documentation
  * [[Extending Single View Design]] * [[:Category:Design proposal]]
  2 KB (179 words) - 09:17, 20 November 2013
• Constrained Dynamic Lexer
  A first design proposal is also drafted. === Requirements Exported by the Current Language Design ===
  3 KB (440 words) - 09:10, 1 March 2010
• Stronger AST Library
  ...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
  ===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
• Improved WD Lemma Generation
  ...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
• Maplet Overriding in Goal
  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
• Current Proof Tree Node in UI
  == 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
• Event-B Language
  ...[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
• Prover Diagrams
  [[Category:Design]]
  726 bytes (102 words) - 12:02, 12 August 2009
• Undo Redo
  ==Design== [[Category:Design]]
  4 KB (599 words) - 15:56, 28 January 2009
• File Root Separation
  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
• Past Developments
  {{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
• Single View Design
  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
• Proposals of Changes to the Mathematical Language Specification
  [[Category:Design proposal]]
  851 bytes (124 words) - 12:53, 26 March 2010
• D23 Introduction
  ...(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
• D45 Scalability
  ...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
• D45 Introduction
  ...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
• Auto-Completion Design
  [[Category:Design]]
  1,001 bytes (119 words) - 14:53, 21 January 2010
• Language of an Event-B Component
  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
• Generic Instantiation
  [[Category:Design]]
  2 KB (232 words) - 15:23, 4 July 2013
• Proof Skeleton Design
  [[Category:Design]]
  2 KB (254 words) - 12:54, 12 August 2009
• Rodin Workshop 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
• Industrial Projects
  * '''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
• Scenarios for Team-based Development
  * 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
• Google Summer of Code 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
• Undo Redo Design
  [[Category:Design]]
  2 KB (291 words) - 09:27, 4 March 2009
• Rodin Developer Support
  * [[Rodin Index Design]] * [[Proof Purger Design|Proof Purger]] allows to delete unused proofs.
  8 KB (1,260 words) - 12:45, 30 July 2015
• ADVANCE D3.3 Introduction
  ...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
• Proof Trees
  [[Category:Design]]
  2 KB (365 words) - 12:52, 12 August 2009
• ADVANCE D3.2 Introduction
  ...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
• ReqsManagement
  [[Category:Design proposal]]
  2 KB (335 words) - 14:16, 3 December 2010
• Modus Ponens generalized
  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
• D23 Pattern Plug-in
  ...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
• ProB API
  ...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
• Railway Interlocking Feedback
  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
• Decomposition Release History
  [[Category:Design]]
  3 KB (343 words) - 10:21, 25 November 2014
• Identifier Decomposition
  [[Category:Design]]
  3 KB (444 words) - 16:57, 27 February 2014
• Membership in Goal
  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
• Indexing System
  ...Rodin Index Design]] for more general considerations about the purpose and design. [[Category:Design]]
  10 KB (1,541 words) - 17:41, 9 March 2009
• Constrained Dynamic Parser
  A first design proposal is also drafted. === Requirements Exported by the Current Language Design ===
  27 KB (3,967 words) - 13:21, 15 February 2010
• Negation Normal Form
  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
• D32 Introduction
  * Choices / decisions. The decisions (e.g. design decisions) are justified.
  3 KB (415 words) - 17:03, 24 November 2010
• D32 Provers
  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
• Proof Purger Design
  [[Category:Design]]
  3 KB (505 words) - 12:54, 12 August 2009
• Proof Simplification
  [[Category:design proposal]]
  3 KB (496 words) - 12:58, 12 August 2009
• DynamicContainer
  * Design an EMF meta model (ecore) of your extension's abstract syntax. The model sh
  6 KB (506 words) - 12:00, 25 November 2009
• D23 UML-B
  ...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

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