On Rigorous Design and Implementation of Fault Tolerant Ambient Systems

2008 Seventh European Dependable Computing Conference

Romanovsky

2008

Self Cite

The paper puts forward the idea of using fault tolerance refinement patterns to assist system developers in disciplined application of software fault tolerance mechanisms in rigorous system design. Two patterns are proposed to support a correct introduction of recovery blocks and Nversion programming into a system model; these are formally defined and their correctness proven. We also discuss several important issues involved in the use of these patterns in engineering systems, including tool support and pattern composition.

Section: Resultsmentioning

confidence: 99%

Refinement Patterns for Fault Tolerant Systems

2008 Seventh European Dependable Computing Conference

Romanovsky

2008

Self Cite

“…The current version of the tool is freely available from our web site [10].Several patterns developed with this tool were applied during formal modelling of the Ambient Campus case study of the RODIN Project [11].…”

Section: Tool For Refinement Automationmentioning

confidence: 99%

Patterns for Refinement Automation

Formal Methods for Components and Objects

Troubitsynå

Laibinis

et al. 2010

Self Cite

Formal modelling is indispensable for engineering highly dependable systems. However, a wider acceptance of formal methods is hindered by their in-sufficient usability and scalability. In this paper, we aim at assisting developers in rigorous modelling and design by increasing automation of development steps. We introduce a notion of refinement patterns -generic representations of typical correctnesspreserving model transformations. Our definition of a refinement pattern contains a description of syntactic model transformations, as well as the pattern applicability conditions and proof obligations for verification of correctness preservation. This establishes a basis for building a tool supporting formal system development via pattern reuse and instantiation. We present a prototype of such a tool and some examples of refinement patterns for automated development in the Event B formalism. AbstractFormal modelling is indispensable for engineering highly dependable systems. However, a wider acceptance of formal methods is hindered by their in-sufficient usability and scalability. In this paper, we aim at assisting developers in rigorous modelling and design by increasing automation of development steps. We introduce a notion of refinement patterns -generic representations of typical correctness-preserving model transformations. Our definition of a refinement pattern contains a description of syntactic model transformations, as well as the pattern applicability conditions and proof obligations for verification of correctness preservation. This establishes a basis for building a tool supporting formal system development via pattern reuse and instantiation. We present a prototype of such a tool and some examples of refinement patterns for automated development in the Event B formalism. About the authorAlexei Ilasov is a Research Associate within the School of Computing Science, Newcastle University.Alexander Romanovsky is a Research Professor. He has been involved in a number of ESPRIT, FP and EPSRC/UK projects on system dependability within which a wide range of general fault tolerance mechanisms and architectures have been developed (DSoS, PDCS, DeVa, CaberNet, MAFTIA, ReSIST, DISCS, RODIN). He has been a co-investigator of two EPSRC/UK projects (DOTS and TrAmS). Now he is coordinating a major FP7 Integrated Project DEPLOY aiming to make major advances in engineering methods for dependable systems through the deployment of formal engineering methods in 5 sectors of European industry. His main interests are in fault tolerance, rigorous design of resilient systems, software architectures, exception handing, mobile agents and service oriented architectures. Abstract. Formal modelling is indispensable for engineering highly dependable systems. However, a wider acceptance of formal methods is hindered by their insufficient usability and scalability. In this paper, we aim at assisting developers in rigorous modelling and design by increasing automation of development steps. Suggested keywordsWe introduce a notion...

“…In our previous work, we implemented two scenarios within the ambient campus case study using the Cama framework as the core component of the applications [15,16,4]. The first scenario (ambient lecture) deals with the activities carried out by the teacher and the students during a lecture -such as questions and answers, and group work among the students -using various mobile devices (PDAs and smartphones).…”

Section: Case Study Scenariosmentioning

confidence: 99%

“…These abstractions are backed by an effective and easy-to-use middleware allowing high system scalability and guaranteeing agent compatibility. More details on Cama and its abstractions can be found in [2][3][4].…”

Section: Introductionmentioning

confidence: 99%

Step-Wise Development of Resilient Ambient Campus Scenarios

Methods, Models and Tools for Fault Tolerance

Arief

Romanovsky

2009

Self Cite

Abstract. This paper puts forward a new approach to developing resilient ambient applications. In its core is a novel rigorous development method supported by a formal theory that enables us to produce a wellstructured step-wise design and to ensure disciplined integration of error recovery measures into the resulting implementation. The development method, called AgentB, uses the idea of modelling database to support a coherent development of and reasoning about several model views, including the variable, event, role, agent and protocol views. This helps system developers in separating various modelling concerns and makes it easier for future tool developers to design a toolset supporting this development. Fault tolerance is systematically introduced during the development of various model views. The approach is demonstrated through the development of several application scenarios within an ambient campus case study conducted at Newcastle University (UK) as part of the FP6 RODIN project.