Toward understanding the rhetoric of small source code changes

IEEE Transactions on Software Engineering

Volumn 31, Issue 6, 2005, Pages 511-526

  Purushothaman, Ranjith ^a   Perry, Dewayne E ^b  

^a DELL INC   (United States)

^b UNIVERSITY OF TEXAS AT AUSTIN   (United States)

Author keywords

Fault probabilities; One line changes; Software faults; Source code changes

Indexed keywords

CODES (SYMBOLS); COMPUTER SOFTWARE MAINTENANCE; DATA REDUCTION; FAULT TOLERANT COMPUTER SYSTEMS; PROBABILITY;

FAULT PROBABILITIES; ONE-LINE CHANGES; SOFTWARE FAULTS; SOURCE CODE CHANGES;

SOFTWARE ENGINEERING;

EID: 24344488030     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/TSE.2005.74     Document Type: Article

References (34)

1. F. Brooks, The Mythical Man-Month. Addison-Wesley, 1975.
2. M. Leszak, D.E. Perry, and D. Stoll, "Classification and Evaluation of Defects in a Project Retrospective," J. Systems and Software, vol. 61, no. 3, pp. 173-187, 2002.
3. A. Mockus and L.G. Votta, "Identifying Reasons for Software Changes Using Historic Databases," Proc. Int'l Conf. Software Maintenance, pp. 120-130, Oct. 2000.
4. T.L. Graves and A. Mockus, "Inferring Change Effort from Configuration Management Databases," Proc. Fifth Int'l Symp. Software Metrics, pp. 267-273, 1998.
5. 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 Trans. Software Eng., vol. 27, no. 1, Jan. 2001.
6. D.E. Perry and H.P. Siy, "Challenges in Evolving a Large Scale Software Product," Proc. Int'l Workshop Principles of Software Evolution (ICSE 1998), Apr. 1998.
7. A. Mockus and D.M. Weiss, "Predicting Risk of Software Changes," Bell Labs Technical J., pp. 169-180, Apr.-June 2000.
8. R. Rogers, "Deterring the High Cost of Software Defects," technical paper, Upspring Software, Inc., Year?
9. G.M. Weinberg, "Kill That Code!" Infosystems, pp. 48-49, Aug. 1983.
10. D.M. Weiss and V.R. Basili, "Evaluating Software Development by Analysis of Changes: Some Data from the Software Engineering Laboratory," IEEE Trans. Software Eng., vol. 11, no. 2, pp. 157-168, Feb. 1985.
11. M. Lipow, "Prediction of Software Failures," The J. Systems and Software, pp. 71-75, 1979.
12. E.B. Swanson, "The Dimensions of Maintenance," Proc. Second Int'l Conf. Software Eng., pp. 492-497, Oct. 1976.
13. T.L. Graves, A.F. Karr, J.S. Marron, and H. Siy, "Predicting Fault Incidence Using Software Change History," IEEE Trans. Software Eng., vol. 26, no. 7, pp. 653-661, July 2000.
14. H.E. Dunsmore and J.D. Gannon, "Analysis of the Effects of Programming Factors on Programming Effort," The J. Systems and Software, pp. 141-153, 1980.
15. I.-H. Lin and D.A. Gustafson, "Classifying Software Maintenance," Proc. IEEE, pp. 241-247, 1988.
16. D.E. Perry, H.P. Siy, and L.G. Votta, "Parallel Changes in Large Scale Software Development: An Observational Case Study," ACM Trans. Software Eng. and Methodology, vol. 10, no. 3, pp 308-337, July 2001.
17. L. Hatton, "Reexamining the Fault Density-Component Size Connection," IEEE Software, vol. 14, no. 2, pp. 89-97, Mar./Apr. 1997.
18. V.R. Basili and B.T. Perricone, "Software Errors and Complexity: An Empirical Investigation," Comm. ACM, vol. 27, no. 1, pp. 42-52, Jan. 1984.
19. D.E. Perry and W.M. Evangelist, "An Empirical Study of Software Interface Errors," Proc. Int'l Symp. New Directions in Computing, pp. 32-38, Aug. 1985.
20. D.E. Perry and W.M. Evangelist, "An Empirical Study of Software Interface Faults - An Update," Proc. 20th Ann. Hawaii Int'l Conf. Systems Sciences, pp. 113-126, Jan. 1987.
21. G.J. Holtzmann, "The Logic of Bugs," Proc. 10th ACM SIGSOFT Symp. Foundations of Software Eng. (FSE-10), pp. 81-87, Nov. 2002.
22. K.E. Martersteck and A.E. Spencer, "Introduction to the 5ESS™ Switching System," AT&T Technical J., vol. 64, no. 6, pp. 1305-1314, July-Aug. 1985.
23. D.C. Carr, A. Dandekar, and D.E. Perry, "Experiments in Process Interface Descriptions, Visualizations and Analyses," Proc. European Workshop Software Process Technology, pp. 119-137, 1995.
24. L.G. Votta and M.L. Zajak, "Design Process Improvement Case Study Using Process Waiver Data," Proc. European Software Eng. Conf., pp. 44-58, 1995.
25. P.A. Tuscany, "Software Development Environment for Large Switching Projects," Proc. Sixth Int'l Conf. Software Eng., pp. 58-67, Sept. 1992.
26. M.J. Rochkind, "The Source Code Control System," IEEE Trans. Software Eng., vol. 1, no. 4, pp. 364-370, Dec. 1975.
27. M.M. Lehman, D.E. Perry, and J.F. Ramil, "Implications of Evolution Metrics on Software Maintenance," Proc. Int'l Conf. Software Maintenance, 1998.
28. CVS - Concurrent Versions System, http://www.cvshome.org, 2004.
29. D.B. Leblang, "The CM Challenge: Configuration Management that Works," Configuration Management: Trends in Software, W.F. Tichy, ed., John Wiley and Sons, 1994.
30. A.E. Hassan, "Mining Software Repositories to Assist Developers and Support Managers," PhD thesis, Dept. of Computer Science, Univ. of Waterloo, Feb. 2005.
31. A.E. Hassan and R.C. Holt, "Studying the Chaos of Code Development," Proc. WCRE 2003: Working Conf. Reverse Eng., Nov. 2003.
32. S.G. Eick, J.L. Steffen, and E.E. Sumner Jr., "Seesoft - A Tool for Visualizing Line Oriented Software Statistics," IEEE Trans. Software Eng., vol. 18, no. 11, pp. 957-968, Nov. 1992.
33. J. Meltzoff, Critical Thinking about Research: Psychology and Related Fields. Washington D.C.: Psychological Assoc., 1997.
34. D.E. Perry, "An Empirical Approach to Design Metrics and Judgments," Proc. New Vision for Software Design and Production Workshop, Dec. 2001.