Search results

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

• Event-B to SMT-LIB
  [[Category:Design]]
  5 KB (797 words) - 10:29, 24 October 2011
• Rodin Workshop 2013
  ...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
• D23 Improvements to Existing Provers
  improving existing tools, while others needed a full design and development of
  5 KB (789 words) - 11:41, 27 January 2010
• Rodin Workshop 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
• D23 Decomposition
  * Design/architectural decision. It applies in particular when it is noticed that it
  6 KB (825 words) - 13:27, 27 January 2010
• ADVANCE D3.2 Model Composition and Decomposition
  '''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
• Extending Refinement Actions
  [[Category:Design proposal]]
  5 KB (764 words) - 15:49, 19 April 2011
• ADVANCE D3.2 General Platform Maintenance
  ...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
• Scenarios for Merging Proofs
  [[Category:Design proposal]]
  6 KB (1,046 words) - 10:34, 27 October 2011
• Pattern
  ...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
• Mode/FT Views
  ...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
• D32 Modes and Fault Tolerance
  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
• 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
• Index Query
  [[Category:Design]]
  7 KB (953 words) - 09:31, 10 March 2009
• D23 Modularisation Plug-in
  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
• Camille Editor
  Due to some design decisions and its combination with the Rodin platform the TextEditor comes
  6 KB (945 words) - 12:22, 27 January 2015
• ADVANCE Deliverable D3.3
  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
• Revisiting Feasibility POs
  [[Category:Design]]
  8 KB (1,284 words) - 18:33, 30 January 2012
• Rodin Workshop 2014
  ...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
• D32 Mathematical Extensions
  ...ndex.php/Constrained_Dynamic_Parser#Design_Alternatives ''Generic Parser's Design Alternatives'' ]
  7 KB (1,095 words) - 14:40, 21 December 2010

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