ACM Home Page
Please provide us with feedback. Feedback
The implications of program dependencies for software testing, debugging, and maintenance
Full text PdfPdf (1.21 MB)
Source International Symposium on Software Testing and Analysis archive
Proceedings of the ACM SIGSOFT '89 third symposium on Software testing, analysis, and verification table of contents
Key West, Florida, United States
Pages: 168 - 178  
Year of Publication: 1989
ISBN:0-89791-342-6
Also published in ...
Authors
A. Podgurski  computer Engineering & Science Department, Case Western Reserve University, Cleveland, Ohio
L. Clarke  Software Development Laboratory, Computer & Information Science Department, University of Massachusetts, Amherst, Massachusetts
Sponsors
IEEE-CS : Computer Society
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 15,   Downloads (12 Months): 61,   Citation Count: 8
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/75308.75328
What is a DOI?

ABSTRACT

This paper presents a formal, general model of program dependencies. Two generalizations of control and data dependence, called weak and strong syntactic dependence, are presented. Some of the practical implications of program dependencies are determined by relating weak and strong syntactic dependence to a relation called semantic dependence. Informally, one program statement is semantically dependent on another if the latter statement can affect the execution behavior of the former. It is shown that weak syntactic dependence is a necessary condition for semantic dependence, but that neither weak nor strong syntactic dependence are sufficient conditions. The implications of these results for software testing, debugging, and maintenance are then explored.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
Aho74
 
Aho86
Berg85
Cart89
 
DeMi88
DeMillo, R.A., Guindi, D.S., King, K.N., McCracken, W.M., and Offutt, A.J. An extended overview of the Mothra software testing environment. Proceedings of the Second Workshop on Software Testing, Verification und Analysis, Banff, Alberta, July 1988, pp. 142-151.
Denn77
Ferr87
Fosd76
 
Fran87
 
Grei75
Horw88a
Horw88b
 
Kore87
 
Lask83
Laski, J. W. and Korel, B. A data flow oriented program testing strategy. IEEE Transactions on Software Engineering, Vol. SE-g, No. 3, May 1983, pp. 347- 354.
 
Mann74
 
More84
 
Ntaf84
Ntafos, S. C. On Required Element Testing. IEEE Transac2ions on Software Engineering, Vol. SE- 10, No. 6, Nov. 1984, pp. 795-803.
Padu86
 
Podg89
 
Rapp85
 
Reps89
Reps, T. and Yang, W. The semantics of program slicing. Technical report, University of Wisconsin-Madison, 1989.
 
Rich88
R h d ic ar son, D. J. and Thompson, M. C. The RELAY model of error detection and its application. Proc. Second Workshop on Software Testing, Verification, and Analysis, Banff, Canada, 1988.
Selk89
 
Weis79
Weis82
 
Weis84
Weiser, M. Program slicing. IEEE Transactions on Software Engineering, Vol. SE-lo, No. 4, July 1984, pp. 352-356.

CITED BY  8