Software Fault Injection Testing of the Embedded Software of a Satellite Launch Vehicle

Samuel, Anil Abraham; Jayalal, N.; Valsa, B.; Ignatious, C. A.; Zachariah, John

doi:10.1109/mpot.2012.2236150

Cited by 5 publications

(1 citation statement)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Fault injection technique is described as a deliberate injection of a fault into a running system during a test activity, to determine whether the system reacts well to off-nominal or exceptional conditions [16,17]. Faults that injected into the system represent the actual faults that occur within the system.…”

Section: Fault Injection Techniquementioning

confidence: 99%

Integration testing based on indirect interaction for embedded system

Hossain

Lee

2019

IJRES

View full text Add to dashboard Cite

<span>Embedded systems comprise several modules that exchange data by interacting among themselves. Exchanging wrong resource data among modules may lead to execution errors or anomalies. Interacting resources produce dependencies between two modules where any change of resources by one module affects the functionality of another module. Several investigations of the embedded system such as aerospace or automobile system show interaction faults between modules are one of the major cause of critical software failures. Therefore, interaction testing is an essential phase to reduce the interaction faults and minimize the risk. The direct and indirect interaction between modules generates interaction faults where indirect interaction is made underneath the interface in which data dependence relationship with resources may cause a different outcome. We investigate errors based on the indirect interaction between modules and introduce a new test criterion for finding errors detectable by existing approaches in unit level but not in integration level. In this paper, we propose a noble approach to generate an interaction model using indirect interaction pattern and design test criteria based on different interaction errors to generate test cases. Finally, we use fault injection and data flow coverage techniques to evaluate the feasibility and effectiveness of our approach</span>

show abstract

Section: Fault Injection Techniquementioning

confidence: 99%