A Constant Perturbation Method for Evaluation of Structural Diversity in Multiversion Software

Authors:
Luping Chen;John H. R. May;Gordon Hughes
Affiliations:
-;-;-
Venue:
SAFECOMP '00 Proceedings of the 19th International Conference on Computer Safety, Reliability and Security
Year:
2000

Citing 12
Cited 1

Selecting Software Test Data Using Data Flow Information

IEEE Transactions on Software Engineering
An experimental evaluation of the assumption of independence in multiversion programming

IEEE Transactions on Software Engineering
PODS—A project on diverse software

IEEE Transactions on Software Engineering - Special issue on reliability and safety in real-time process control
An Applicable Family of Data Flow Testing Criteria

IEEE Transactions on Software Engineering
Conceptual Modeling of Coincident Failures in Multiversion Software

IEEE Transactions on Software Engineering
Software testing

Journal of Information Processing
An experimental evaluation of data flow and mutation testing

Software—Practice & Experience
Software fault injection: inoculating programs against errors

Software fault injection: inoculating programs against errors
A 'Crystal Ball' for Software Liability

Computer
Structural Software Reliability Estimation

SAFECOMP '99 Proceedings of the 18th International Conference on Computer Computer Safety, Reliability and Security
The N-Version Approach to Fault-Tolerant Software

IEEE Transactions on Software Engineering
A Theoretical Basis for the Analysis of Multiversion Software Subject to Coincident Errors

IEEE Transactions on Software Engineering

Assessment of the Benefit of Redundant Systems

SAFECOMP '02 Proceedings of the 21st International Conference on Computer Safety, Reliability and Security

Quantified Score

Hi-index	0.00

Visualization

Abstract

In this paper, fault simulation is discussed as a test method for diversity assessment of multiversion software and data flow perturbation is used as a main technique for implementation. More specifically, constant perturbation is introduced as a specific example of data-flow perturbation. Some quantitative metrics are proposed for the description of software diversity, and the parameters needed to calculate the metrics estimated by fault injection experiments. A case study is presented to illustrate that the diversity metrics are appropriate, and that constant perturbation is a practical fault injecting technique to estimate parameters necessary for assessing diversity.