[18] L. J. White and E. I. Cohen, “A Domain Strategy for Computer Program Testing,” IEEE Transactions

on Software Engineering, May 1980, pp. 247-257

[WC80] Domain errors are in the subset of the program input domain, and can be caused by incorrect

predicates in branching statements or incorrect computations that affect variables in branching

statements. In this paper a set of constraints under which it’s possible to reliably detect domain errors

is introduced. The paper develops the idea of linearly bounded domains. The practical limitations of

the approach are also discussed, of which the most severe is that of generating and then developing test

points for all boundary segments of all domains of all program paths.

Question: Method/Means

Result: Technique

Validation: Analysis

[19] J. A. Whittaker, “What is Software Testing? And Why Is It So Hard?” IEEE Software, January 2000,

pp. 70-79

[Whit00] Being a practical tutorial article, the paper answers questions from developers how bugs

escape from testing. Undetected bugs come from executing untested code, difference of the order of

executing, combination of untested input values, and untested operating environment. A four-phase

approach is described in answering to the questions. By carefully modeling the software’s

environment, selecting test scenarios, running and evaluating test scenarios, and measuring testing

progress, the author offers testers a structure of the problems they want to solve during each phase.

Question: Characterization

Result: Qualitative & Descriptive Model

Validation: Persuasion

The End...