Software engineering data collection for field studies

Guide to Advanced Empirical Software Engineering

Volumn , Issue , 2008, Pages 9-34

  Singer, Janice ^a   Sim, Susan E ^b   Lethbridge, Timothy C ^c  

^a NATIONAL RESEARCH COUNCIL CANADA   (Canada)

^b 5226 Donald Bren Hall   (United States)

^c UNIVERSITY OF OTTAWA   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84890132353     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/978-1-84800-044-5_1     Document Type: Chapter

References (55)

1. Anda, B., Benestad, H., and Hove, S. 2005. A multiple-case study of effort estimation based on use case points. In ISESE 2005 (Fourth International Symposium on Empirical Software Engineering). IEEE Computer Society, Noosa, Australia, November 17-18, pp. 407-416.
2. Baddoo, N. and Hall, T. 2002. Motivators of software process improvement: an analysis of practitioners' views. Journal of Systems and Software, 62, 85-96.
3. Bellotti, V. and Bly, S. 1996. Walking Away from the Desktop Computer: Distributed Collaboration and Mobility in a Product Design Team. Conference on Computer Supported Cooperative Work, Cambridge, MA, pp. 209-219.
4. Berlin, L.M. 1993. Beyond Program Understanding: A Look at Programming Expertise in Industry. Empirical Studies of Programmers, Fifth Workshop, Palo Alto, pp. 6-25.
5. Briand, L., El Emam, K. and Morasca, S. 1996. On the application of measurement theory in software engineering. Empirical Software Engineering, 1, 61-88.
6. Bratthall, L. and Jørgensen, M. 2002. Can you trust a single data source exploratory software engineering case study? Empirical Software Engineering: An International Journal, 7(1), 9-26.
7. Budgen, D. and Thomson, M. 2003. CASE tool evaluation: experiences from an empirical study. Journal of Systems and Software, 67, 55-75.
8. Buckley, J. and Cahill, T. 1997. Measuring Comprehension Behaviour Through System Monitoring. International Workshop on Empirical Studies of Software Maintenance, Bari, Italy, 109-113.
9. Chi, M. 1997. Quantifying qualitative analyzes of verbal data: a practical guide. The Journal of the Learning Sciences, 6(3), 271-315.
10. Curtis, B., Krasner, H., and Iscoe, N. 1988. A field study of the software design process for large systems. Communications of the ACM, 31(11), 1268-1287.
11. Damian, D., Zowghi, D., Vaidyanathasamy, L., and Pal, Y. 2004. An industrial case study of immediate benefits of requirements engineering process improvement at the Australian Center for Unisys Software. Empirical Software Engineering: An International Journal, 9(1-2), 45-75.
12. Delbecq, A.L., Van de Ven, A.H., and Gustafson, D.H. 1975. Group Techniques for Program Planning. Scott, Foresman & Co, Glenview, IL
13. Draper, S. 2004. The Hawthorne Effect. http://www.psy.gla.ac.uk/steve/ hawth.html]
14. Ericcson, K. and Simon, H. 1984. Protocol Analysis: Verbal Reports as Data. The MIT Press, Cambridge, MA
15. Herbsleb, J. and Mockus, A. 2003. An empirical study of speed and communication in globally distributed software development. IEEE Transactions of Software Engineering, 29(6), 481-494.
16. Hungerford, B., Hevner, A., and Collins, R. 2004. Reviewing software diagrams: a cognitive study. IEEE Transactions of Software Engineering, 30(2), 82-96.
17. Iivari, J. 1996. Why are CASE tools not used? Communications of the ACM, 39(10), 94-103.
18. Izquierdo, L., Damian, D., Singer, J., and Kwan, I. (2007). Awareness in the Wild: Why Communication Breakdowns Occur. ICGSE 2007, Germany
19. Jick, T. 1979. Mixing qualitative and quantitative methods: triangulation in action. Administrative Science Quarterly, 24(4), 602-611.
20. Jordan, B. and Henderson, A. 1995. Interaction analysis: foundations and practice. The Journal of the Learning Sciences, 4(1), 39-103.
21. Jørgensen, M. 1995. An empirical study of software maintenance tasks. Software Maintenance: Research and Practice, 7, 27-48.
22. Karahasanovic, A., Hinkel, U., Sjøberg D., and Thomas, R. (2007). Comparing of Feedback Collection and Think-Aloud Methods in Program Comprehension Studies. Accepted for publication in Journal of Behaviour & Information Technology, 2007
23. Keller, R., Schauer, R. Robitaille, S., and Page, P. 1999. Pattern-based Reverse Engineering of Design Components. Proceedings, International Conference on Software Engineering, Los Angeles, CA, pp. 226-235.
24. Ko, A.J., DeLine, R., and Venolia, G. (2007). Information needs in collocated software development teams. International Conference on Software Engineering (ICSE), May 20-26, 344-353.
25. Lethbridge, T.C. 2000. Priorities for the education and training of software engineers. Journal of Systems and Software, 53(1), 53-71.
26. Miles, M.B. 1979. Qualitative data as an attractive nuisance: the problem of analysis. Administrative Science Quarterly, 24(4), 590-601.
27. Miles, M.B. and Huberman, A.M. 1994. Qualitative Data Analysis: An Expanded Sourcebook, Second Edition. Sage Publications, Thousand Oaks, CA
28. Mockus, A., Fielding, R.T., and Herbsleb, J.D. 2002. Two case studies of open source software development: Apache and Mozilla. ACM Transactions on Software Engineering and Methodology, 11(3), 209-246.
29. NASA, SEL COTS Study Phase 1 Initial Characterization Study Report, SEL-98-001, August 1998. http://sel.gsfc.nasa.gov/website/documents/online-doc. htm
30. Perry, D.E., Staudenmayer, N., and Votta, L. 1994. People, organizations, and process improvement. IEEE Software, 11, 37-45.
31. Pfleeger, S.L. and Hatton, L. 1997. Investigating the influence of formal methods. Computer, 30, 33-43.
32. Pfleeger, S. and Kitchenham, B. 2001. Principles of survey research Part 1: turning lemons into lemonade. Software Engineering Notes, 26(6), 16-18.
33. Porter, A.A., Siy, H.P., Toman, C.A., and Votta, L.G. 1997. An experiment to assess the cost-benefits of code inspections in large scale software development. IEEE Transactions on Software Engineering, 23(6), 329-346.
34. Punter, T., Ciolkowski, M., Freimut, B., and John, I. 2003. Conducting On-Line Surveys in Software Engineering. Proceedings on the International Symposium on Empirical Software Engineering'03, pp. 80-88.
35. Rainer, A. and Hall, T. 2003. A quantitative and qualitative analysis of factors affecting software processes. Journal of Systems and Software, 66, 7-21.
36. Robbins, S.P. 1994. Essentials of Organizational Behavior, Fourth edition. Prentice Hall, Englewood Cliffs, NJ
37. Robillard, P.N., d'Astous, P., Détienne, D., and Visser, W. 1998. Measuring Cognitive Activities in Software Engineering. Proceedings on the 20th International Conference on Software Engineering, Japan, pp. 292-300.
38. Sayyad-Shirabad, J., Lethbridge, T.C., and Lyon, S. 1997. A Little Knowledge Can Go a Long Way Towards Program Understanding. Proceedings of 5th International Workshop on Program Comprehension, IEEE, Dearborn, MI, pp. 111-117.
39. Seigel, S. and Castellan, N.J. 1988. Nonparametric Statistics for the Behavioral Sciences, Second Edition. McGraw-Hill, New York
40. Seaman, C.B. and Basili, V.R. 1998. Communication and organization: an empirical study of discussion in inspection meetings. IEEE Transactions on Software Engineering, 24(7), 559-572.
41. Seaman, C., Mendonca, M., Basili, V., and Kim, Y. 2003. User interface evaluation and empirically-based evolution of a prototype experience management tool. IEEE Transactions on Software Engineering, 29, 838-850.
42. Shull, F., Lanubile, F., and Basili, V. 2000. Investigating reading techniques for object-oriented framework learning. IEEE Transactions on Software Engineering, 26, 1101-1118.
43. Sim S.E. and Holt, R.C. 1998. The Ramp-Up Problem in Software Projects: A Case Study of How Software Immigrants Naturalize. Proceedings on the 20th International Conference on Software Engineering, Kyoto, Japan, April, pp. 361-370.
44. Singer, J., Lethbridge, T., Vinson, N., and Anquetil, N. 1997. An Examination of Software Engineering Work Practices. Proceedings of CASCON, IBM Toronto, October, pp. 209-223.
45. Somé, S.S. and Lethbridge T.C. 1998. Parsing Minimizing when Extracting Information from Code in the Presence of Conditional Compilation. Proceedings of the 6th IEEE International Workshop on Program Comprehension, Italy, June, pp. 118-125.
46. Storey, M.-A., Cheng, L., Singer, J., Muller, M., Ryall, J., and Myers, D. (2007). Turning Tags into Waypoints for Code Navigation. ICSM, Paris, France
47. Teasley, S., Covi, L., Krishnan, M., and Olson, J. 2002. Rapid software development through team collocation. IEEE Transactions on Software Engineering, 28, 671-683.
48. von Mayrhauser, A. and Vans, A.M. 1993. From Program Comprehension To Tool Requirements for an Industrial Environment. Proceedings of the 2nd Workshop on Program Comprehension, Capri, Italy, pp. 78-86.
49. von Mayrhauser, A. and Vans, A.M. 1995. Program understanding: models and experiments. In M.C. Yovita and M.V. Zelkowitz (eds.), Advances in Computers, Vol. 40, Academic Press, New York, pp. 1-38.
50. Walz, D.B., Elam, J.J., and Curtis, B. 1993. Inside a software design team: knowledge acquisition, sharing, and integration. Communications of the ACM, 36(10), 62-77.
51. Walenstein, A. 2003. Observing and Measuring Cognitive Support: Steps Toward Systematic Tool Evaluation and Engineering. Proceedings of the 11th IEEE Workshop on Program Comprehension
52. Williams, L., Kessler, R.R., Cunningham, W., and Jeffries, R. 2000. Strengthening the case for pair-programming. IEEE Software, July/Aug, 19-25.
53. Wolf, A. and Rosenblum, D. 1993. A Study in Software Process Data Capture and Analysis. Proceedings of the 2nd International Conference on Software Process, February, pp. 115-124.
54. Wu, J., Graham, T., and Smith, P. 2003. A Study of Collaboration in Software Design. Proceedings of the International Symposium on Empirical Software Engineering'03
55. Zou, L. and Godfrey, M. 2007. An Industrial Case Study of Program Artifacts Viewed During Maintenance Tasks. Proceedings of the 2006 Working Conference on Reverse Engineering (WCRE-06), 23-28 October, Benevento, Italy