The Community for Technology Leaders
Green Image
Issue No. 03 - May/June (2011 vol. 28)
ISSN: 0740-7459
pp: 41-48
Ananda Basu , Verimag Laboratory
Jacques Combaz , Verimag Laboratory
Thanh-Hung Nguyen , Verimag Laboratory
Mohamad Jaber , Verimag Laboratory
Joseph Sifakis , Verimag Laboratory
Saddek Bensalem , Verimag Laboratory
Marius Bozga , Verimag Laboratory
ABSTRACT
Rigorous system design requires the use of a single powerful component framework allowing the representation of the designed system at different detail levels, from application software to its implementation. A single framework allows the maintenance of the overall coherency and correctness by comparing different architectural solutions and their properties. The authors present the BIP (behavior, interaction, priority) component framework, which encompasses an expressive notion of composition for heterogeneous components by combining interactions and priorities. This allows description at different abstraction levels from application software to mixed hardware/software systems. A rigorous design flow that uses BIP as a unifying semantic model derives a correct implementation from an application software, a model of the target architecture, and a mapping. Implementation correctness is ensured by applying source-to-source transformations that preserve correctness of essential design properties. The design is fully automated and supported by a toolset including a compiler, the D-Finder verification tool, and model transformers. The authors present an autonomous robot case study to illustrate BIP's use as a modeling formalism as well as crucial aspects of the design flow for ensuring correctness.
INDEX TERMS
component-based design, model-based design, design flow, model transformation, correctness, invariant generation, deadlock-freedom, code generation, autonomous robots
CITATION
Ananda Basu, Jacques Combaz, Thanh-Hung Nguyen, Mohamad Jaber, Joseph Sifakis, Saddek Bensalem, Marius Bozga, "Rigorous Component-Based System Design Using the BIP Framework", IEEE Software, vol. 28, no. , pp. 41-48, May/June 2011, doi:10.1109/MS.2011.27
109 ms
(Ver )