An empirical study of fine-grained software modifications

Empirical Software Engineering

Volumn 11, Issue 3, 2006, Pages 369-393

  German, Daniel M ^a  

^a UNIVERSITY OF VICTORIA   (Canada)

Author keywords

Software artifacts; Software evolution; Software visualization; Version control

Indexed keywords

CLASSIFICATION (OF INFORMATION); COMPUTER DEBUGGING; CONTROL SYSTEMS; HEURISTIC METHODS; INFORMATION RETRIEVAL; MODERNIZATION; MODIFICATION; PROJECT MANAGEMENT;

SOFTWARE ARTIFACTS; SOFTWARE EVOLUTION; SOFTWARE VISUALIZATION; VERSION CONTROL;

COMPUTER AIDED SOFTWARE ENGINEERING;

EID: 33746069380     PISSN: 13823256     EISSN: 15737616     Source Type: Journal    
DOI: 10.1007/s10664-006-9004-6     Document Type: Article

References (30)

1. Collberg C, Kobourov S, Nagra J, Pitts J, Wampler K (2003) A system for graph-based visualization of the Evolution of software. In: Soft Vis '03: Proceedings of the 2003 ACM symposium on software visualization, ACM, New York, New York, pp 77-ff
2. Eick SG, Graves XL, Karr AF, Mockus A, Schuster P (2002) Visualizing software changes. IEEE Trans Softw Eng 28(4):396-412
3. Fischer M, Pinzger M, Gall H (2003a) Analyzing and relating bug report data for feature tracking. In: Proc. 10th working conference on reverse engineering, IEEE, pp 90-101
4. Fischer M, Pinzger M, Gall H (2003b) Populating a release history database from version control and bug tracking systems. In: Proceedings of the 19 IEEE international conference on software maintenance (ICSM'03), IEEE Computer Society, pp 23-32
5. Fisher M, Gall H (2003) MDS-views: visualizing problem report data of large scale software using multidimensional scaling. In: Proceedings of the international workshop on Evolution of large-scale industrial software applications (ELISA)
6. Gall H, Jazayeri M, Krajewski J (2003) CVS release history data for detecting logical couplings. In: Proceedings of the international workshop on principles of software Evolution (IWPSE), IEEE, pp 12-23
7. German DM (2004a) Decentralized open source global software development, the GNOME experience. Journal of Software Process: Improvement and Practice 8(4):201-215
8. German DM (2004b) Mining CVS repositories, the softChange experience. In: 1st international workshop on mining software repositories, pp 17-21
9. German DM (2004c) Using software trails to reconstruct the Evolution of software. Journal of Software Maintenance and Evolution: Research and Practice 16(6):367-384
10. German DM, Mockus A (2003) Automating the measurement of open source projects. In: Proceedings of the 3rd workshop on open source software engineering
11. German DM, Hindle A, Jordan N (2004) Visualizing the Evolution of software using softChange. In: Proceedings SEKE 2004 The 16th international conference on software engineering and knowledge engineering, Knowledge Systems Institute, 3420 Main St. Skokie, Illinois 60076, USA, pp 336-341
12. Girba T, Ducasse S, Lanza M (2004) Yesterday's weather: guiding early reverse engineering efforts by summarizing the Evolution of changes. In: Proceedings of the 20th IEEE International Conference on Software Maintenance (ICSM'04), pp 44-49
13. Graves TL, Karr AF, Siy H (2000) Visualizing software changes. IEEE Trans Softw Eng 26(7):653-661
14. Hassan AE, Holt RC (2003) The chaos of software development. In: Proceedings of the international workshop on principles of software Evolution (IWPSE), pp 84-95
15. Hassan AE, Holt RC (2004) Predicting change propagation in software systems. In: Proceedings of the 20th IEEE international conference on software maintenance (ICSM'04), pp 284-293
16. Lanza M (2001) The Evolution Matrix: recovering software Evolution using software visualization techniques. In: Proceedings of the 4th international workshop on principles of software Evolution (IWPSE), pp 37-42
17. Lerner J, Triole J (2000) The simple economics of open source. Working Paper 7600, National Bureau of Economic Research, http://papers.nber.org/papers/ w7600
18. Liu Y, Stroulia E (2003) Reverse engineering the process of small novice software teams. In: Proc. 10th working conference on reverse engineering. IEEE, pp 102-112
19. Liu Y, Stroulia E, Wong K, German D (2004) Using CVS historical information to understanding how students develop software. In: 1st international workshop on mining software repositories, pp 32-36
20. Mockus A, Fielding RT, Herbsieb J (2002) Two case studies of open source software development: Apache and Mozilla. ACM Trans Softw Eng Methodol 11(3):1-38
21. Ostrand TJ, Weyuker EJ (2004) A tool for mining defect-tracking systems to predict fault-prone files. In: 1st international workshop on mining software repositories, pp 85-89
22. Ostrand TJ, Weyuker EJ, Bell R (2005) Predicting the location and number of faults in large software systems. IEEE Trans Softw Eng 340-355
23. Purushothaman R, Perry DE (2005) Toward understanding the rhetoric of small source code changes. IEEE Trans Softw Eng 31(6):511-526
24. Storey MA, Čubranić D, German DM (2005) On the use of visualization to support awareness of human activities in software development: a survey and a framework. In: Proceedings of the 2nd ACM symposium on software visualization, pp 193-202. To be presented
25. Williams CC, Hollingsworth JK (2005) Automatic mining of source code repositories to improve bug finding techniques. IEEE Trans Softw Eng 31(6):466-480
26. Wu J, Holt RC, Hassan AE (2004a) Exploring software Evolution using spectrographs. In: Proc. 11th working conference on reverse engineering, pp 80-89
27. Wu X, Murray A, Storey M-A, Lintern R (2004b) A reverse engineering approach to support software maintenance: version control knowledge extraction. In: Proc. 11th working conference on reverse engineering, pp 90-99
28. Ying A, Murphy GC, Ng R, Chu-Carroll MC (2005) Predicting source code changes by mining change history. IEEE Trans Softw Eng 31 (9):574-586
29. Zimmermann T, Weissgerber P (2004) Preprocessing CVS data for fine-grained analysis. In: 1st international workshop on mining software repositories, pp 2-6
30. Zimmermann T, Weissgerber P, Diehl S, Zeller A (2005) Mining version histories to guide software changes. IEEE Trans Softw Eng 31(6):429-445