Towards understanding how developers spend their effort during maintenance activities

Proceedings - Working Conference on Reverse Engineering, WCRE

Volumn , Issue , 2013, Pages 152-161

  Soh, Zephyrin ^a   Khomh, Foutse ^a   Gueheneuc, Yann Gael ^a   Antoniol, Giuliano ^a  

^a ÉCOLE POLYTECHNIQUE DE MONTRÉAL   (Canada)

Author keywords

change complexity; developers' effort; interaction history; Maintenance task; patch

Indexed keywords

CHANGE COMPLEXITY; DEVELOPERS' EFFORT; INTERACTION HISTORY; MAINTENANCE TASKS; PATCH;

COMPUTER PROGRAMMING; REVERSE ENGINEERING; SOFTWARE ENGINEERING; TOOLS;

MAINTENANCE;

EID: 84893345345     PISSN: 10951350     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/WCRE.2013.6671290     Document Type: Conference Paper

References (18)

1. R. D. Banker, S. M. Datar, and C. F. Kemerer. Factors affecting software maintenance productivity: An exploratory study. In Proceedings of the International Conference on Information Systems, pages 160-175, 1987.
2. B. Boehm. Software engineering. IEEE Trans. Computers, 12(25):1226-1242, 1976.
3. B. Boehm. Improving software productivity. Computer, 20(9):43-57, 1987.
4. J. Feigenspan, C. Kastner, J. Liebig, S. Apel, and S. Hanenberg. Measuring programming experience. In Proceedings ICPC, pages 73-82, 2012.
5. T. Fritz, J. Ou, G. C. Murphy, and E. Murphy-Hill. A degree-ofknowledge model to capture source code familiarity. In Proceedings ICSE, pages 385-394, 2010.
6. A. E. Hassan. Predicting faults using the complexity of code changes. In Proceedings ICSE, pages 78-88, 2009.
7. M. Kersten and G. C. Murphy. Using task context to improve programmer productivity. In Proceedings of the 14th ACM SIGSOFT/FSE, pages 1-11, 2006.
8. A. J. Ko, B. A. Myers, M. J. Coblenz, and H. H. Aung. An exploratory study of how developers seek, relate, and collect relevant information during software maintenance tasks. IEEE Transaction on Software Engineering, 32(12):971-987, dec 2006.
9. A. Lamkanfi, S. Demeyer, E. Giger, and B. Goethals. Predicting the severity of a reported bug. In Proceedings MSR, pages 1-10, 2010.
10. S. Lee and S. Kang. Clustering and recommending collections of code relevant to tasks. In Proceedings ICSM, pages 536-539, 2011.
11. K. Maxwell and P. Forselius. Benchmarking software development productivity. Software, IEEE, 17(1):80-88, 2000.
12. N. I. of Standards & Technology. The economic impacts of inadequate infrastructure for software testing, May 2002. US Dept of Commerce.
13. L. D. Panjer. Predicting eclipse bug lifetimes. In Proceedings MSR, pages 29-, 2007.
14. R. Robbes and D. Rothlisberger. Using developer interaction data to compare expertise metrics. In Proceedings MSR, pages 297-300, 2013.
15. A. Serebrenik, B. Vasilescu, and M. v. d. Brand. Similar tasks, different effort: Why the same amount of functionality requires different development effort? In BENEVOL, 2011.
16. E. Shihab, A. Ihara, Y. Kamei, W. Ibrahim, M. Ohira, B. Adams, A. Hassan, and K.-i. Matsumoto. Studying re-opened bugs in open source software. Empirical Software Engineering, 32(12):1-38, 2012.
17. Z. Soh, F. Khomh, Y.-G. Gueheneuc, G. Antoniol, and B. Adams. On the effect of program exploration on maintenance tasks. In Working Conference on Reverse Engineering (WCRE), 2013. To appear.
18. S. Zaman, B. Adams, and A. E. Hassan. Security versus performance bugs: a case study on firefox. In Proceedings MSR, pages 93-102, 2011