An experimental evaluation of the assumption of independence in multiversion programming
IEEE Transactions on Software Engineering
Data Diversity: An Approach to Software Fault Tolerance
IEEE Transactions on Computers - Fault-Tolerant Computing
Conceptual Modeling of Coincident Failures in Multiversion Software
IEEE Transactions on Software Engineering
Analysis of Faults in an N-Version Software Experiment
IEEE Transactions on Software Engineering
How Accurate is Scientific Software?
IEEE Transactions on Software Engineering
Evaluating Testing Methods by Delivered Reliability
IEEE Transactions on Software Engineering
Modeling software design diversity: a review
ACM Computing Surveys (CSUR)
N-Version Design Versus One Good Version
IEEE Software
Assessment of the Reliability of Fault-Tolerant Software: A Bayesian Approach
SAFECOMP '00 Proceedings of the 19th International Conference on Computer Safety, Reliability and Security
A Theoretical Basis for the Analysis of Multiversion Software Subject to Coincident Errors
IEEE Transactions on Software Engineering
Journal of Systems Architecture: the EUROMICRO Journal
Experiences with the design of a run-time check
SAFECOMP'06 Proceedings of the 25th international conference on Computer Safety, Reliability, and Security
On the effectiveness of run-time checks
SAFECOMP'05 Proceedings of the 24th international conference on Computer Safety, Reliability, and Security
| Hi-index | 0.00 |
Abstract: Design diversity is a defence against design faults causing common-mode failure in redundant systems, but we badly lack knowledge about how much reliability it will buy in practice, and thus about its cost-effectiveness, the situations in which it is an appropriate solution and how it should be taken into account by assessors and safety regulators. Both current practice and the scientific debate about design diversity depend largely on intuition. More formal probabilistic reasoning would facilitate critical discussion and empirical validation of any predictions: to this aim, we propose a model of the generation of faults and failures in two separately-developed program versions. We show results about: i) what degree of reliability improvement an assessor can reliably expect from diversity; and ii) how this reliability improvement may change with higher-quality development processes. We discuss the practical relevance of these results and the degree to which they can be trusted.