Software Fault Interactions and Implications for Software Testing¶
Kuhn, D. R., Wallace, D. R., & Gallo, A. M. (2004). Software Fault Interactions and Implications for Software Testing. IEEE Transactions on Software Engineering, 30(6), 418-421.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Cartesian Product
- A clinical-trial planner studying three doses, two routes, and four subgroups is reasoning on a \(3 \times 2 \times 4\) product of 24 cells; a software tester sweeping configuration \(\times\) operating system \(\times\) locale, a portfolio analyst spanning macro-scenario axes, and a manufacturer enumerating trim combinations are all doing the same structural work, and the move that translates among them is precisely the recognition that each lives on a Cartesian product.
This sourceCombinatorial (covering-array) testing over configuration × OS × locale spaces and pruning infeasible combinations.
Supported in partVerified against the publisher's abstract
Abstract backs combinatorial testing of parameter combinations for software, but not the clinical-trial, portfolio or manufacturing instances, nor the 3x2x4 arithmetic.
“We show that software failures in a variety of domains were caused by combinations of relatively few conditions. These results have important implications for testing. If all faults in a system can be triggered by a combination of n or fewer parameters, then testing all n-tuples of parameters is effectively equivalent to exhaustive testing”
- A clinical-trial planner studying three doses, two routes, and four subgroups is reasoning on a \(3 \times 2 \times 4\) product of 24 cells; a software tester sweeping configuration \(\times\) operating system \(\times\) locale, a portfolio analyst spanning macro-scenario axes, and a manufacturer enumerating trim combinations are all doing the same structural work, and the move that translates among them is precisely the recognition that each lives on a Cartesian product.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:3266158b2141 · see in the full table