Title :
Verifying the completeness of test
Author_Institution :
SoHaR Inc., Culver City, CA
Abstract :
Testing of a software product can be claimed to be complete when these criteria have been satisfied: all elements that can fail must have been tested, and all test outcomes must be in agreement with the expected failure effects. This paper addresses how these criteria can be met with particular reference to critical software intensive systems such as aircraft or plant control systems.
Keywords :
formal verification; program testing; aircraft control systems; critical software intensive systems; failure effects; plant control systems; software product testing; software test; test verification; Aerospace control; Aircraft; Cause effect analysis; Cities and towns; Failure analysis; Power generation economics; Software safety; Software systems; Software testing; System testing; Software test; model based development; software FMEA; software verification;
Conference_Titel :
AUTOTESTCON, 2008 IEEE
Conference_Location :
Salt Lake Cirty, UT
Print_ISBN :
978-1-4244-2225-8
Electronic_ISBN :
1088-7725
DOI :
10.1109/AUTEST.2008.4662614