This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
A Formal Evaluation of Data Flow Path Selection Criteria
November 1989 (vol. 15 no. 11)
pp. 1318-1332

The authors report on the results of their evaluation of path-selection criteria based on data-flow relationships. They show how these criteria relate to each other, thereby demonstrating some of their strengths and weaknesses. A subsumption hierarchy showing their relationship is presented. It is shown that one of the major weaknesses of all the criteria is that they are based solely on syntactic information and do not consider semantic issues such as infeasible paths. The authors discuss the infeasible-path problem as well as other issues that must be considered in order to evaluate these criteria more meaningfully and to formulate a more effective path-selection criterion.

[1] L. A. Clarke, A. Podgurski, D. J. Richardson, and S. J. Zeil, "A comparison of data flow path selection criteria," inProc. 8th Inf. Conf. Sofware Eng.(London UK), Aug. 1985. Los Alamitos, CA: IEEE Computer Soc., 1985, pp. 244-251.
[2] L. A. Clarke and D. J. Richardson, "Applications of symbolic evaluation,"J. Syst. Software, vol. 5, pp. 15-35, 1985.
[3] R. A. DeMillo, D. S. Guindi, K. N. King, W. M. McCracken, and A. J. Offutt, "An extended overview of the Mothra software testing environment," inProc. Second Workshop Software Testing, Verification and Analysis, Banff, Alberta, July 1988, pp. 142-151.
[4] P. G. Frankl and E. J. Weyuker, "Data flow testing in the presence of unexecutable paths," inProc. ACM SIGSOFT/IEEE Workshop Software Testing, IEEE Comput. Soc., Banff, Alberta, Canada, July 1986, pp. 4-13.
[5] P. M. Herman, "A data flow analysis approach to program testing,"Australian Comput. J., vol. 8, no. 3, Nov. 1976.
[6] W. E. Howden, "Methodology for the generation of program test data,"IEEE Trans. Comput., vol. C-24, no. 5, pp. 554-559, May 1975.
[7] W. E. Howden, "A functional approach to program testing and analysis,"IEEE Trans. Software Eng., vol. SE-12, no. 10, pp. 997-1005, Oct. 1986.
[8] J. W. Laski, "On the comparative analysis of some data flow testing strategies," Dep. Eng. Comput. Sci.,Oakland Univ., Rochester, MI, Tech. Rep. 87-05, May 1987.
[9] J. W. Laski and B. Korel, "A data flow oriented program testing strategy,"IEEE Trans. Software Eng., vol. SE-9, no. 3, pp. 347- 354, May 1983.
[10] L. J. Morell, "Theoretical insights into fault-based testing," inProc. 2nd Workshop on Software Testing, Verification, and Analysis(Banff, AB, Can.), July 1988. Los Alamitos, CA: IEEE Computer Soc., 1988, pp. 45-62.
[11] S. C. Ntafos, "On testing with required elements," inProc. COMPSAC '81, IEEE Comput. Soc., Nov. 1981, pp. 132-139.
[12] S. C. Ntafos, "On required element testing," Comput. Sci. Program, Univ. Texas, Dallas, Tech. Rep. 123, Nov. 1982.
[13] S. C. Ntafos, "On required element testing,"IEEE Trans. Software Eng., vol. SE-10, no. 6, pp. 795-803, Nov. 1984.
[14] S. C. Ntafos, "A comparison of some structural testing strategies," Comput. Sci. Program, Univ. Texas, Dallas, Tech. Rep. 210, June 1985.
[15] S. C. Ntafos, "A comparison of some structural testing strategies,"IEEE Trans. Software Eng., vol. SE-14, no. 6, pp. 868-874, June 1988.
[16] L. J. Osterweil and L. D. Fosdick, "DAVE--A validation, error detection, and documentation system for Fortran programs,"Software Practice and Experience, vol. 6, no. 4, pp. 473-486, Oct. 1976.
[17] A. Podgurski and L. A. Clarke, "The implications of program dependencies of software testing, debugging, and maintenance," inProc. ACM SIGSOFT Conf. Software Testing, Analysis, and Verification, Key West, FL, Dec. 1989, pp. 168-178.
[18] S. Rapps and E. J. Weyuker, "Data flow analysis techniques for program test data selection," inProc. 6th Int. Conf. Software Eng., Sept. 1982, pp. 272-278.
[19] S. Rapps and E. J. Weyuker, "Selecting software test data using data flow information,"IEEE Trans. Software Eng., vol. SE-11, no. 4, pp. 367-375, Apr. 1985.
[20] D. J. Richardson and M. C. Thompson, "An analysis of test data selection criteria using the RELAY model of error detection," Tech. Rep. 86-65, Comput. and Information Science, University of Massachusetts, Amherst, Dec. 1986.
[21] D. J. Richardson and M. C. Thompson, "The RELAY model of error detection and its application," inProc. Second Workshop Software Testing, Verification, and Analysis. IEEE Computer Society, Los Angeles, CA, 1988.
[22] L. G. Stucki, "Automatic generation of self-metric software," inRec. 1973 IEEE Symp. Software Reliability, IEEE Comput. Soc., Apr. 1973, pp. 94-100.
[23] E. J. Weyuker, "The complexity of data flow criteria for test data selection,"Inform. Processing Lett., vol. 19, no. 2, pp. 103-109, Aug. 1984.
[24] E. J. Weyuker, "An empirical study of the complexity of data flow testing," inProc. ACM SIGSOFT/IEEE Second Workshop Software Testing, Verification, and Analysis, IEEE Comput. Soc., Banff, Alberta, Canada, July 1988, pp. 188-195.
[25] M. R. Woodward, D. Hedley, and M. A. Hennel, "Experience with path analysis and testing of programs,"IEEE Trans. Software Eng., vol. SE-6, no. 3, pp. 278-286, May 1980.
[26] S. J. Zeil, "Selectivity of data-flow and control-flow path criteria," inProc. ACM SIGSOFT/IEEE Second Workshop Software Testing, Verification, and Analysis, IEEE Comput. Soc., Banff, Alberta, Canada, July 1988, pp. 216-222.
[27] S. J. Zeil, "Perturbation techniques for detecting domain errors,"IEEE Trans. Software Eng., vol. SE-15, no. 6, pp. 737-746, June 1989.

Index Terms:
formal evaluation; data flow path selection criteria; data-flow relationships; subsumption hierarchy; syntactic information; infeasible-path problem; flowcharting; software engineering
Citation:
L.A. Clarke, A. Podgurski, D.J. Richardson, S.J. Zeil, "A Formal Evaluation of Data Flow Path Selection Criteria," IEEE Transactions on Software Engineering, vol. 15, no. 11, pp. 1318-1332, Nov. 1989, doi:10.1109/32.41326
Usage of this product signifies your acceptance of the Terms of Use.