Information needs for software development analytics

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2012, Pages 987-996

  Buse, Raymond P L ^a   Zimmermann, Thomas ^b  

^a UNIVERSITY OF VIRGINIA   (United States)

^b MICROSOFT RESEARCH   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

DECISION MAKING PROCESS; DRILL-DOWN; INFORMATION NEED; INFORMATION RESOURCE; ORGANIZATIONAL STRUCTURES; PROFESSIONAL SOFTWARE; SYSTEM ARCHITECTURES; TOOLS AND TECHNIQUES;

DECISION MAKING; ENGINEERING; INFORMATION SCIENCE; SOFTWARE DESIGN; SURVEYS;

ENGINEERS;

EID: 84864194945     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSE.2012.6227122     Document Type: Conference Paper

References (44)

1. R. P. L. Buse and W. R. Weimer, "A metric for software readability," in ISSTA '08, 2008, pp. 121-130.
2. T. J. McCabe, "A complexity measure," IEEE Trans. Software Eng., vol. 2, no. 4, pp. 308-320, 1976.
3. T. Addison and S. Vallabh, "Controlling software project risks: an empirical study of methods used by experienced project managers," in SAICSIT '02, 2002, pp. 128-140.
4. National Institute of Standards and Technology, "The economic impacts of inadequate infrastructure for software testing," Research Triangle Institute, Tech. Rep., 2002.
5. L. Strigini, "Limiting the dangers of intuitive decision making," IEEE Software, vol. 13, pp. 101-103, 1996.
6. J. T. Biehl, M. Czerwinski, G. Smith, and G. G. Robertson, "Fastdash: a visual dashboard for fostering awareness in software teams," in CHI '07, 2007, pp. 1313-1322.
7. A. J. Ko, R. DeLine, and G. Venolia, "Information needs in collocated software development teams," in ICSE'07, 2007, pp. 344-353.
8. J. Sillito, G. C. Murphy, and K. De Volder, "Questions programmers ask during software evolution tasks," in SIGSOFT '06/FSE-14, 2006, pp. 23-34.
9. B. Boehm and R. Ross, "Theory-w software project management principles and examples," IEEE TSE, vol. 15, no. 7, pp. 902-916, jul 1989.
10. L. Wallace, M. Keil, and A. Rai, "Understanding software project risk: a cluster analysis," Inf. Manage., vol. 42, no. 1, pp. 115-125, 2004.
11. A. Jedlitschka, "Evaluating a model of software managers' information needs - an experiment," in ESEM'10, 2010.
12. S. Vegas, N. J. Juzgado, and V. R. Basili, "Packaging experiences for improving testing technique selection," Journal of Systems and Software, vol. 79, no. 11, pp. 1606-1618, 2006.
13. T. Punter, "What information do software engineering practitioners need?" in Proc. of ESEIW Workshop on Empirical Studies in Software Engineering, 2003, pp. 85-95.
14. S. Komi-Sirvi, P. Parviainen, and J. Ronkainen, "Measurement automation: Methodological background and practical solutions-a multiple case study," in METRICS'01: IEEE International Symposium on Software Metrics, 2001, p. 306.
15. A. Rainer, T. Hall, and N. Baddoo, "Persuading developers to 'buy into' software process improvement: Local opinion and empirical evidence," in ISESE'03, 2003, pp. 326-335.
16. V. R. Basili, G. Caldiera, and H. D. Rombach, "Goal, question, metric paradigm," in Encyclopedia of Software Engineering Volume 1, J. J. Marciniak, Ed. John Wiley & Sons, 1994, pp. 528-532.
17. V. R. Basili, M. Lindvall, M. Regardie, C. Seaman, J. Heidrich, J. Münch, D. Rombach, and A. Trendowicz, "Linking software development and business strategy through measurement," IEEE Computer, vol. 43, pp. 57-65, 2010.
18. R. Kaplan and D. Norton, "The balanced scorecard - measures that drive performance," Harvard Business Review, p. 71, January/February 1992.
19. U. D. of Defense and U. Army, "Practical software and systems measurement: A foundation for objective project management, v.4.0c," March 2003, www.psmsc.com.
20. A. Kaushik, Web Analytics 2.0. Wiley Publishing, 2010.
21. V. R. Basili, "The experience factory and its relationship to other improvement paradigms," in ESEC'93, 1993, pp. 68-83.
22. A. Sillitti, A. Janes, G. Succi, and T. Vernazza, "Collecting, integrating and analyzing software metrics and personal software process data," in EUROMICRO, 2003, p. 336.
23. P. Johnson, H. Kou, M. Paulding, Q. Zhang, A. Kagawa, and T. Yamashita, "Improving software development management through software project telemetry," IEEE Software, vol. 22, no. 4, pp. 76-85, july-aug. 2005.
24. R. P. Buse and T. Zimmermann, "Analytics for software development," in FSE/SDP Workshop on the Future of Software Engineering Research, November 2010.
25. T. Davenport, J. Harris, and R. Morison, Analytics at Work. Boston, MA: Harvard Business School, 2010.
26. R. Buse and T. Zimmermann, "Information needs for software development analytics," Microsoft Research, Tech. Rep. MSR-TR-2011-8, 2010.
27. B. Kitchenham and S. Pfleeger, "Personal opinion surveys," in Guide to Advanced Empirical Software Engineering. Springer, 2007.
28. C. Cadar, V. Ganesh, P. M. Pawlowski, D. L. Dill, and D. R. Engler, "Exe: Automatically generating inputs of death," ACM Trans. Inf. Syst. Secur., vol. 12.
29. P. Godefroid, N. Klarlund, and K. Sen, "Dart: directed automated random testing," SIGPLAN Not., vol. 40, pp. 213-223, June 2005.
30. M. Kim, D. Cai, and S. Kim, "An empirical investigation into the role of refactorings during software evolution," in ICSE '11, 2011.
31. T. Mens and T. Tourwé, "A survey of software refactoring," IEEE Trans. Software Eng., vol. 30, no. 2, pp. 126-139, 2004.
32. G. Ruhe, Product Release Planning: Methods, Tools and Applications. Auerbach Publications, 2010.
33. K. Glerum, K. Kinshumann, S. Greenberg, G. Aul, V. Orgovan, G. Nichols, D. Grant, G. Loihle, and G. Hunt, "Debugging in the (very) large: ten years of implementation and experience," in SOSP '09: Proc. Symp. Operating Systems Principles, 2009, pp. 103-116.
34. T. Briggs, "How does usage data improve the office user experience?" blogs.technet.com, Feb 2010.
35. P. Koss-Nobel, "Data driven engineering: Tracking usage to make decisions," blogs.technet.com, Nov 2009.
36. S. Lipstein, "Designing with customers in mind," blogs. technet.com, Oct 2009.
37. T. M. Pigoski, Practical Software Maintenance: Best Practices for Managing Your Software Investment. John Wiley & Sons, Inc., 1996.
38. R. C. Seacord, D. Plakosh, and G. A. Lewis, Modernizing Legacy Systems: Software Technologies, Engineering Process and Business Practices. Addison-Wesley Longman, 2003.
39. A. Mockus, "Succession: Measuring transfer of code and developer productivity," in ICSE'09, 2009, pp. 67-77.
40. J. Cohen, Ed., Best Kept Secrets of Peer Code Review. Austin, TX: Smart Bear Inc., 2006.
41. C. Bird, A. Bachmann, E. Aune, J. Duffy, A. Bernstein, V. Filkov, and P. Devanbu, "Fair and balanced? bias in bug-fix datasets," in ESEC/FSE'09, 2009.
42. A. Bachmann, C. Bird, F. Rahman, P. Devanbu, and A. Bernstein, "The missing links: Bugs and bug-fix commits," in SIGSOFT'10/FSE-18. ACM, 2010.
43. T. H. D. Nguyen, B. Adams, and A. E. Hassan, "A case study of bias in bug-fix datasets," in WCRE '10, 2010.
44. T. May, The New Know: Innovation Powered by Analytics. Wiley, 2009.