Software Engineering of Fault Tolerant Systems

Guelfi, Nicolas; Muccini, Henry; Romanovsky, A

doi:10.1142/6362

Cited by 6 publications

(10 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…While there have been several workshops, tutorials and other events held which address related issues (e.g., [1], [2], [13], [71], [22]), this survey goes much further by summarising the existing body of work and analysing the major trends in the area. We hope our work will help to bring the researchers from the two communities together so that they can come up with even more integrated and practical solutions.…”

Section: Discussionmentioning

confidence: 99%

“…Recently, however, a number of studies have been conducted aiming to understand where and how fault tolerance can be integrated in the software life-cycle (e.g., [11], [12], [13]). It has been recognised that different classes of faults, errors and failures are identifiable during different phases of software development, and that it is therefore essential that fault tolerance is addressed at different phases of the software process, such as requirements, high-level (architectural) and low-level design.…”

mentioning

confidence: 99%

See 1 more Smart Citation

Architecting Fault Tolerant Systems

Muccini¹,

Romanovsky²

2007

2007 Working IEEE/IFIP Conference on Software Architecture (WICSA'07)

View full text Add to dashboard Cite

Building trustworthy (dependable) systems is a major challenge faced by software developers. To this end, various fault tolerance mechanisms have been developed by researchers and used in industry. Unfortunately, more often than not these solutions ignore earlier development phases-most importantly, the architecture design to exclusively focus on the implementation instead. This creates a dangerous gap between the requirement to build dependable (and fault tolerant) systems and the failure to address these issues at any stage preceding the implementation step. Software Architecture has been widely accepted as a way to achieve a better software quality while reducing the time and cost of production. While typical architectural specifications model only the normal behaviour of the system, ignoring the abnormal ones, several approaches have recently been developed which break the wrong pattern. The aim of this paper is to survey the existing approaches to architecting fault tolerant systems, offering its readers a clear picture of the state of the art research in this emerging area. This survey is built on developing a two-dimensional classification of the existing solutions: the first dimension is based on the traditional software engineering characteristics while the second one uses fault tolerance-related parameters. The paper analyses the major trends and identifies possible directions for future research.

show abstract

Section: Discussionmentioning

confidence: 99%

mentioning

confidence: 99%

Architecting Fault Tolerant Systems

Muccini¹,

Romanovsky²

2007

2007 Working IEEE/IFIP Conference on Software Architecture (WICSA'07)

View full text Add to dashboard Cite

show abstract

“…Dependability is the ability to deliver service that can justifiably be trusted [1]. Its main goal is to avoid service failures that are more frequent and more severe than the acceptable for the user.…”

Section: Introductionmentioning

confidence: 99%

“…The techniques to detect errors can be concurrent, if they take place during the service delivery, or they can be preemptive, if they act when the service is suspended and thus latent errors and dormant faults can be found. 1 The recovery consists of error handling (to leave the system into a state without detected errors) and fault handling (to leave the system into a state without faults that can be activated again).…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Analysis and framework-based design of a fault-tolerant web information system for m-health

Balbastro

Capozucca

Guelfi

2008

SOCA

View full text Add to dashboard Cite

The e-health domain has the objective to assist and manage citizens' health. It concerns many actors like patient, doctors, hospitals and administration. Current and forthcoming generations of application will be web based and will integrate more and more mobile devices. In such application domain, called m-health, dependability is a key notion. In addition, more and more functionalities of such systems will be implemented as services for providing qualities like adaptability and maintainability. This paper presents, through a case study, how we can analyse and design an application that controls the insulin injection and that is embedded in a mobile device belonging to an e-health Web Information System (WIS). In order to ensure the dependability of the control systems, we show how to use Coordinated Atomic Actions (CAA). CAAs provide well defined concepts for fault tolerance, error-detection and error recovery in a distributed context where competitive and cooperative concurrencies are considered. The combination of CAA and SOA at design level it is proposed, with the purpose of being able to design systems that are partially implemented using service-oriented technologies. We updated and used our implementation framework, called CAA-DRIP, which originally was not tailored for service-oriented mobile applications. Thus, in this paper, we also propose an adaptation of CAA-DRIP for mobile devices.

show abstract

Architecture Principles for Resilience

Furrer

2019

Future-Proof Software-Systems

View full text Add to dashboard Cite

Software Engineering of Fault Tolerant Systems

Cited by 6 publications

References 0 publications

Architecting Fault Tolerant Systems

Architecting Fault Tolerant Systems

Analysis and framework-based design of a fault-tolerant web information system for m-health

Architecture Principles for Resilience

Contact Info

Product

Resources

About