Implementing design diversity to achieve fault tolerance

Kelly, J.P.J.; McVittie, Thomas I.; Yamamoto, Wayne

doi:10.1109/52.300038

Cited by 50 publications

(13 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is ironic, to say the least, that the quality control mechanism of replication, especially external replication, is so little practiced amongst those doing the science behind the engineering. There is an additional irony: because of the current state of software development practice, N-version programming has been suggested as a fault recovery mechanism (see, for example Kelly et al (1991) ). We know so little about doing it right, we end up replicating system functionality across several programs.…”

Section: Replication: the Motivationmentioning

confidence: 99%

Replication's Role in Software Engineering

Brooks

Roper

Wood

et al. 2008

Guide to Advanced Empirical Software Engineering

View full text Add to dashboard Cite

We provide motivation for researchers to replicate experiments in software engineering. The ideology of replication is discussed. We address the question: Is an experiment worth repeating? The current lack of replication studies is highlighted. We make clear that exact replication is unattainable and we draw on our first experience of performing an external replication. To categorise various kinds of replication, we propose a simple extension to Basili et al.'s framework for experimentation in software engineering. We present guidance as to the level of reported detail required to enable others perform a replication. Our conclusion is that there is only one route for empirical software engineering to follow: to make available laboratory packages of experimental materials to facilitate internal and external replications, especially the latter, which have greater confirming power.

show abstract

Section: Replication: the Motivationmentioning

confidence: 99%

Replication's Role in Software Engineering

Brooks

Roper

Wood

et al. 2008

Guide to Advanced Empirical Software Engineering

View full text Add to dashboard Cite

show abstract

“…There are several software fault tolerant systems [15][6] that are based on design diversity [16] to tolerate software design faults.…”

Section: F Results Analysismentioning

confidence: 99%

A Case Study for Fault Tolerance Oriented Programming in Multi-core Architecture

Lü

Cui

2009

2009 11th IEEE International Conference on High Performance Computing and Communications

View full text Add to dashboard Cite

The multi-core architecture brings more and more challenges and means to common software developers. Reliable software system design approaches can give a high confidence that long-running online software systems run correctly. But anyway these approaches will certainly cause the loss of the efficiency. We found that the multi-core architecture is a quite suitable platform to support reliable software system design and can make the cost acceptable because of its advantages of the parallel performance and prevalence. In this paper we make use of the multi-core architecture to support software fault tolerance. This approach will make the integration of software fault tolerance and the multi-core architecture as a common design choice. According to the idea of software fault tolerance, for some key software units in a system we can develop N separate versions of them with equivalent functionalities. Each version is developed independently by an isolated group to prevent identical faults among versions. All implemented versions run separately from same initial conditions and inputs. Outputs of all redundant versions are submitted to a decision module that determines a single result from multiple results as the correct output. In this paper, we give a case study to show that with the multi-core architecture, the redundant versions of a key software unit can run in parallel on different cores to improve the efficiency.

show abstract

“…For example, if the battery level goes low beyond a certain limit, the system can go into a power-saving mode using features that incur minimum impact on battery consumption or replacing active components with back-up/standby ones which may provide lower quality/fewer services but consume less battery (e.g. in design diversity techniques [9]). Without the trade-off analysis introduced here, such a decision may not only be hard, but also will be blind in the sense that the side effects of a feature/component replacement on other aspects of the system will be unknown.…”

Section: Usage Examplementioning

confidence: 99%

Enabling trade-off analysis of NFRs on models of embedded systems

2011

View full text Add to dashboard Cite

Satisfaction of Non-Functional Requirements (NFR), is a key factor in successful design of embedded systems. This is mainly due to the constraints and resource limitations in these systems. A design that cannot achieve functionality of the system under these limitations is actually a failure. Therefore, NFRs in design of embedded systems deserve special attention. However, one big issue is that NFRs are interconnected and cannot be considered in isolation; especially that they can have direct impacts on each other such as security and performance. This means that a careful balance and trade-off analysis among NFRs is necessary. In this paper, we focus on this need and identify what information about NFRs is required in order to perform trade-off analysis. We propose and explain our inprogress approach to incorporate this information into system models in order to enable trade-off analysis. Our approach is based on UML profiling method to annotate model elements with necessary information.

show abstract

Implementing design diversity to achieve fault tolerance

Cited by 50 publications

References 11 publications

Replication's Role in Software Engineering

Replication's Role in Software Engineering

A Case Study for Fault Tolerance Oriented Programming in Multi-core Architecture

Enabling trade-off analysis of NFRs on models of embedded systems

Contact Info

Product

Resources

About