Home > Research > Publications & Outputs > On the impact of injection triggers for OS robu...

Research

Associated organisational units

Links

Text available via DOI:

Keywords

View graph of relations

On the impact of injection triggers for OS robustness evaluation

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

On the impact of injection triggers for OS robustness evaluation. / Johansson, A.; Suri, Neeraj; Murphy, B.
The 18th IEEE International Symposium on Software Reliability (ISSRE '07). IEEE, 2007. p. 127-136.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Johansson, A, Suri, N & Murphy, B 2007, On the impact of injection triggers for OS robustness evaluation. in The 18th IEEE International Symposium on Software Reliability (ISSRE '07). IEEE, pp. 127-136. https://doi.org/10.1109/ISSRE.2007.23

APA

Johansson, A., Suri, N., & Murphy, B. (2007). On the impact of injection triggers for OS robustness evaluation. In The 18th IEEE International Symposium on Software Reliability (ISSRE '07) (pp. 127-136). IEEE. https://doi.org/10.1109/ISSRE.2007.23

Vancouver

Johansson A, Suri N, Murphy B. On the impact of injection triggers for OS robustness evaluation. In The 18th IEEE International Symposium on Software Reliability (ISSRE '07). IEEE. 2007. p. 127-136 doi: 10.1109/ISSRE.2007.23

Author

Johansson, A. ; Suri, Neeraj ; Murphy, B. / On the impact of injection triggers for OS robustness evaluation. The 18th IEEE International Symposium on Software Reliability (ISSRE '07). IEEE, 2007. pp. 127-136

Bibtex

@inproceedings{b6e22b72173b401fafb70c92cb12a1e5,
title = "On the impact of injection triggers for OS robustness evaluation",
abstract = "Traditionally, in fault injection-based robustness evaluation of software (specifically for Operating Systems - OS's), faults or errors are injected at specific code locations. This paper studies the sensitivity and accuracy of the robustness evaluation results arising from varying the timing of injecting the faults into the OS. A strategy to guide the triggering of fault injection is proposed, based on the observation that the operational usage profile of a driver shows a high degree of regularity in the calls being made. The concept of call blocks (i.e., a distinct sequence of calls made to the driver) can be used to guide injections into different system states, corresponding to the driver operations carried out. A real-world case study compares the effectiveness of the proposed strategy to traditional location-based approaches, demonstrating that significant and useful insights can be gained by modulating the injection instants. {\textcopyright} 2007 IEEE.",
keywords = "Automobile drivers, Computer operating systems, Computer software, Computer software selection and evaluation, Location, Quality assurance, Shelters (from attack), Software reliability, Technical presentations, Case studies, Fault-injection, International symposium, Location-based, Operating systems (OS), Operational usage, Real world, Robustness evaluation, Software reliability engineering, System states, Reliability",
author = "A. Johansson and Neeraj Suri and B. Murphy",
year = "2007",
month = nov,
day = "5",
doi = "10.1109/ISSRE.2007.23",
language = "English",
isbn = "0769530249",
pages = "127--136",
booktitle = "The 18th IEEE International Symposium on Software Reliability (ISSRE '07)",
publisher = "IEEE",

}

RIS

TY - GEN

T1 - On the impact of injection triggers for OS robustness evaluation

AU - Johansson, A.

AU - Suri, Neeraj

AU - Murphy, B.

PY - 2007/11/5

Y1 - 2007/11/5

N2 - Traditionally, in fault injection-based robustness evaluation of software (specifically for Operating Systems - OS's), faults or errors are injected at specific code locations. This paper studies the sensitivity and accuracy of the robustness evaluation results arising from varying the timing of injecting the faults into the OS. A strategy to guide the triggering of fault injection is proposed, based on the observation that the operational usage profile of a driver shows a high degree of regularity in the calls being made. The concept of call blocks (i.e., a distinct sequence of calls made to the driver) can be used to guide injections into different system states, corresponding to the driver operations carried out. A real-world case study compares the effectiveness of the proposed strategy to traditional location-based approaches, demonstrating that significant and useful insights can be gained by modulating the injection instants. © 2007 IEEE.

AB - Traditionally, in fault injection-based robustness evaluation of software (specifically for Operating Systems - OS's), faults or errors are injected at specific code locations. This paper studies the sensitivity and accuracy of the robustness evaluation results arising from varying the timing of injecting the faults into the OS. A strategy to guide the triggering of fault injection is proposed, based on the observation that the operational usage profile of a driver shows a high degree of regularity in the calls being made. The concept of call blocks (i.e., a distinct sequence of calls made to the driver) can be used to guide injections into different system states, corresponding to the driver operations carried out. A real-world case study compares the effectiveness of the proposed strategy to traditional location-based approaches, demonstrating that significant and useful insights can be gained by modulating the injection instants. © 2007 IEEE.

KW - Automobile drivers

KW - Computer operating systems

KW - Computer software

KW - Computer software selection and evaluation

KW - Location

KW - Quality assurance

KW - Shelters (from attack)

KW - Software reliability

KW - Technical presentations

KW - Case studies

KW - Fault-injection

KW - International symposium

KW - Location-based

KW - Operating systems (OS)

KW - Operational usage

KW - Real world

KW - Robustness evaluation

KW - Software reliability engineering

KW - System states

KW - Reliability

U2 - 10.1109/ISSRE.2007.23

DO - 10.1109/ISSRE.2007.23

M3 - Conference contribution/Paper

SN - 0769530249

SN - 9780769530246

SP - 127

EP - 136

BT - The 18th IEEE International Symposium on Software Reliability (ISSRE '07)

PB - IEEE

ER -