Identification of Software Instabilities

Reverse Engineering - Working Conference Proceedings

Volumn , Issue , 2003, Pages 134-143

  Bevan, Jennifer ^a   James Whitehead Jr , E ^a  

^a UNIVERSITY OF CALIFORNIA   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

SOFTWARE DECAY; SOFTWARE INSTABILITY;

ALGORITHMS; CODES (SYMBOLS); GRAPH THEORY; INFORMATION TECHNOLOGY; PROGRAM DEBUGGING; SOFTWARE ENGINEERING;

COMPUTER SOFTWARE;

EID: 0346781631     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/WCRE.2003.1287244     Document Type: Conference Paper

References (22)

1. "ANTLR website," (2003). http://www.antlr.org/
2. "The Apache HTTP Server Project," (2003). http://httpd.apache.org/
3. "Aristotle Research Group," (2002). http://www.cc.gatech.edu/aristotle/
4. L. A. Belady and M. M. Lehman, "A Model of Large Program Development," IBM Systems Journal, vol. 15, no. 3 (1976), pp. 225-252.
5. J. Cheng, "Slicing Concurrent Programs - A Graph Theoretical Approach," Proc. Automated and Algorithmic Debugging, 1993, pp. 223-240.
6. "Center-TRACON Automation System (CTAS) for Air Traffic Control," (2003). http://www.ctas.arc.nasa.gov/
7. S. G. Eick, T. L. Graves, A. F. Karr, J. S. Marron and A. Mockus, "Does Code Decay? Assessing the Evidence from Change Management Data, " IEEE Transactions of Software Engineering, vol. 27, no. 1 (2001), pp. 1-13.
8. H. Gall, K. Hajek and M. Jazayeri, "Detection of Logical Coupling Based on Product Release History," Proc. International Conference on Software Maintenance, November 16-20, 1998, pp. 190-198.
9. D. German. ICSE 2003.
10. "Grammatech, Inc. - Products - Codesurfer," (2003). http://www.grammatech.com/products/codesurfer/
11. T. L. Graves, A. F. Karr, J. S. Marron and H. Siy, "Predicting Fault Incidence Using Software Change History," IEEE Transactions of Software Engineering, vol. 26, no. 7 (2000), pp. 653-661.
12. M. M. Lehman, "Rules and Tools for Software Evolution Planning and Management," Proc. FEAST 2000 Workshop, Imperial College, London, July 10-12, 2000, 2000.
13. M. M. Lehman and L. A. Belady, Program Evolution: Processes of Software Change: Academic Press, 1985.
14. M. M. Lehman and J. F. Ramil, "EpiCS: Evolution Phenomenology in Component-Intensive Software," Proc. Seventh IEEE Workshop on Empirical Studies of Software Maintenance (WESS 2001), November, 2001, 2001.
15. A. Mockus, D. Weiss and P. Zhang, "Understanding and Predicting Effort in Software Projects," Proc. 25th International Conference on Software Engineering (ICSE 2003), Portland, Oregon, May 3-10, 2003, 2003, pp. 274-284.
16. D. L. Parnas, "Software Aging," Proc. 16th International Conference on Software Engineering, Sorrento, Italy, May 16-21, 1994, 1994, pp. 279-287.
17. A. Podgurski and L. Clarke, "A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance," IEEE Transactions of Software Engineering, vol. 16, no. 9 (1990), pp. 965-979.
18. T. Reps, S. Horwitz and M. Sagiv, "Precise Interprocedural Dataflow Analysis via Graph Reachability," Proc. 22nd ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages (POPL'95), 1995, pp. 49-61.
19. S. Sinha, M. Harrold and G. Rothermel, "Interprocedural Control Dependence," A CM Transactions on Software Engineering and Methodology, vol. 10, no. 2 (2001), pp. 209-254.
20. "Soot: A Java Optimization Framework," (2003). http://www.sable.mcgill.ca/soot/
21. J. Stafford and A. Wolf, "Architecture-Level Dependence Analysis for Software Systems," Int'l Journal of Software Engineering and Knowledge Engineering, vol. 11, no. 4 (2001), pp. 431-451.
22. "Subversion project home page," (2003). http://subversion.tigris.org/