Difference between revisions of "Event Model Decomposition"
imported>Pascal |
imported>Pascal (Introduction) |
||
Line 1: | Line 1: | ||
{{TOCright}} | {{TOCright}} | ||
− | === Bibliography == | + | == Introduction == |
+ | One of the most important feature of the Event-B approach is the ability to introduce new events during refinement steps, but a consequence is an increasing complexity of the refinement process when having to deal with many events and many state variables. | ||
+ | |||
+ | The main idea of the decomposition is to cut a model <math>A</math> into sub-models <math>A_1, ..., A_n</math>, which can be refined separately and more confortably than the whole. | ||
+ | |||
+ | The constraint that shall be satisfied by the decomposition is that these refined models might - the recomposition will never be performed in practice - be recomposed into a whole model <math>R</math> in a way that guarantees that <math>R</math> refines <math>A</math>. An event-based decomposition of a model is detailed in [[Event Model Decomposition]]: the events of a model are partitioned to form the events of the sub-models. In parallel, the variables on which these events are acting are distributed among the sub_models. | ||
+ | |||
+ | The purpose is here to precisely describe what is required at the Rodin platform level to integrate this event model decomposition, and to explain why. The details of how it could be implemented are out of scope. | ||
+ | |||
+ | == Terminology == | ||
+ | |||
+ | == Architecture == | ||
+ | |||
+ | == Specification == | ||
+ | |||
+ | === Requirements === | ||
+ | |||
+ | |||
+ | == Bibliography == | ||
+ | |||
+ | * J.R. Abrial, Mathematical Models for Refinement and Decomposition, in ''The Event-B Book'', February 2007. | ||
+ | * J.R. Abrial, ''[[Event Model Decomposition]]'', Version 1.3, April 2009. | ||
+ | * M. Butler, Decomposition Structures for Event-B, in ''Integrated Formal Methods iFM2009'', Springer, LNCS 5423, 2009 ([http://eprints.ecs.soton.ac.uk/16965/1/butler.pdf lien externe]). | ||
+ | |||
− | |||
− | |||
[[Category:Design]] | [[Category:Design]] | ||
[[Category:Work in progress]] | [[Category:Work in progress]] |
Revision as of 10:23, 10 June 2009
Introduction
One of the most important feature of the Event-B approach is the ability to introduce new events during refinement steps, but a consequence is an increasing complexity of the refinement process when having to deal with many events and many state variables.
The main idea of the decomposition is to cut a model into sub-models
, which can be refined separately and more confortably than the whole.
The constraint that shall be satisfied by the decomposition is that these refined models might - the recomposition will never be performed in practice - be recomposed into a whole model in a way that guarantees that
refines
. An event-based decomposition of a model is detailed in Event Model Decomposition: the events of a model are partitioned to form the events of the sub-models. In parallel, the variables on which these events are acting are distributed among the sub_models.
The purpose is here to precisely describe what is required at the Rodin platform level to integrate this event model decomposition, and to explain why. The details of how it could be implemented are out of scope.
Terminology
Architecture
Specification
Requirements
Bibliography
- J.R. Abrial, Mathematical Models for Refinement and Decomposition, in The Event-B Book, February 2007.
- J.R. Abrial, Event Model Decomposition, Version 1.3, April 2009.
- M. Butler, Decomposition Structures for Event-B, in Integrated Formal Methods iFM2009, Springer, LNCS 5423, 2009 (lien externe).