[4] A. Bertolino, P. Inverardi, H. Muccini, and A. Rosetti, “An approach to integration testing based on

architectural descriptions,” Proceedings of the IEEE ICECCS- 97, pp. 77-84

16

[BIMR97] In this paper the authors propose to use formal architectural descriptions (CHAM) to model

the behavior of interest of the systems. Graph of all the possible behaviors of the system in terms of

the interactions between its components is derived and further reduced. A suitable set of reduced

graphs highlights specific architectural properties of the system, and can be used for the generation of

integration tests according to a coverage strategy, analogous to the control and data flow graphs in

structural testing.

Question: Method/Means

Result: Technique

Validation: Persuasion

[5] J.B. Good Enough and S. L. Gerhart, “Toward a Theory of Test Data Selection,” IEEE Transactions on

Software Engineering, June 1975, pp. 156-173

[GG75] This paper is the first published paper, which attempted to provide a theoretical foundation for

testing. The “fundamental theorem of testing” brought up by the authors characterizes the properties

of a completely effective test selection strategy. The authors think a test selection strategy is

completely effective if it is guaranteed to discover any error in a program. As an example, the

effectiveness of branch and path testing in discovering errors is compared. The use of decision table (a

mixture of requirements and design-based functional testing) as an alternative method is also proposed.

Question: Evaluation

Result: Analytic Model

Validation: Analysis

[6] D. Gelperin and B. Hetzel, “The Growth of Software Testing”, Communications of the ACM, Volume

31 Issue 6, June 1988, pp. 687-695

[GH88] In this article, the evolution of software test engineering is traced by examining changes in the

testing process model and the level of professionalism over the years. Two phase models, the

demonstration and destruction models, and two life cycle models, the evolution and prevention models

are given to characterize the growth of software testing with time. Based on the models a prevention

oriented testing technology is introduced and analyzed in detail.

Question: Characterization

Result: Descriptive Model

Validation: Persuasion

[7] J. Hartmann, C. Imoberdorf, and M.Meisinger, “UML-Based Integration Testing,” Proceedings of the

International Symposium on Software Testing and Analysis, ACM SIGSOFT Software Engineering Notes,

August 2000

[HIM00] Unified Modeling Language (UML) is widely used for the design and implementation of

distributed, component-based applications. In this paper, the issue of testing components by

integrating test generation and test execution technology with commercial UML modeling tools such

as Rational Rose is addressed. The authors present their approach to modeling components and

interactions, describe how test cases are derived from these component models and then executed to

verify their conformant behavior. The TnT environment of Siemens is used to evaluate the approach

by examples

Question: Method/Means

Result: Technique

Validation: Experience

[8] W. E. Howden, “Reliability of the Path Analysis Testing Strategy”, IEEE Transactions on Software

Testing, September 1976, pp. 208-215

17

[Howden76] The reliability of path testing provides an upper bound for the testing of a subset of a

program’s paths, which is always the case in reality. This paper begins by showing the impossibility

of constructing a test strategy that is guaranteed to discover all errors in a program. Three commonly

occurring classes of errors, computations, domain, and subcase, are characterized. The reliability

properties associated with these errors affect how path testing is defined.

Question: Characterization

Result: Technique

Validation: Analysis

[9] W. E. Howden, “Functional Testing and Design Abstractions,” The Journal of System and Software,

Volum 1, 1980, pp. 307-313

[Howden80] The usual practice of functional testing is to identify functions that are implemented by a

system or program from requirements specifications. In this paper, the necessity of testing design as

well as requirement functions is discussed. The paper indicates how systematic design methods, such

as Structured design and the Jackson design can be used to construct functional tests. Structured

design can be used to identify the design functions that must be tested in the code, while the Jackson

method can be used to identify the types of data which should be used to construct tests for those

functions.

Question: Method/Means

Result: Technique

Validation: Persuasion

[10] J. C. Huang, “An Approach to Program Testing,” ACM Computing Surveys, September 1975, pp.113-

128

[Huang75] This paper introduces the basic notions of dynamic testing based on detailed path analysis

in which full knowledge of the contents of the source program being tested is used during the testing

process. Instead of the common test criteria by which to have every statement in the program executed

at least once, the author suggested and demonstrated by an example, that a better criterion is to require

that every edge in the program diagraph be exercised at least once. The process of manipulating a

program by inserting probes along each segment in the program is suggested in this paper.

Question: Method/Means

Result: Technique

Validation: Analysis