Studying software engineers: Data collection techniques for software field studies

Empirical Software Engineering

Volumn 10, Issue 3, 2005, Pages 311-341

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

^a UNIVERSITY OF OTTAWA   (Canada)

^b Ringgold Standard Institution Informatics   (United States)

^c NATIONAL RESEARCH COUNCIL CANADA   (Canada)

Author keywords

Empirical software engineering; Field studies; Work practices

Indexed keywords

COMPUTER AIDED DESIGN; COMPUTER HARDWARE; COMPUTER SOFTWARE; DATA REDUCTION; HUMAN COMPUTER INTERACTION; PARAMETER ESTIMATION;

EMPIRICAL SOFTWARE ENGINEERING; FIELD STUDIES; MODELING TOOL; WORK PRACTICES;

COMPUTER AIDED ENGINEERING;

EID: 21744448173     PISSN: 13823256     EISSN: None     Source Type: Journal    
DOI: 10.1007/s10664-005-1290-x     Document Type: Article

References (68)

1. Anquetil, N., and Lethbridge, T. C. 1999. Recovering software architecture from the names of source files. Journal of Software Maintenance: Research and Practice 11: 201-221.
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. Baddoo, N., and Hall, T. 2002. De-motivators of software process improvement: An analysis of practitioners' views. Journal of Systems and Software 66: 23-33.
4. Basili, V. R. Software modeling and measurement: The Goal/Question/Metric paradigm. Tech. Rep. CS-TR-2956, Department of Computer Science, University of Maryland, College Park, MD 20742, Sept. 1992.
5. Beecham, S., Hall, T., and Rainer, A. 2003. Software process improvement problems in twelve software companies: An empirical analysis. Empirical Software Engineering 8: 7-42.
6. Bellotti, V., and Bly, S. 1996. Walking Away from the Desktop Computer: Distributed Collaboration and Mobility in a Product Design Team. Cambridge, MA: Conference on Computer Supported Cooperative Work, pp. 209-219.
7. Berlin, L. M. 1993. Beyond Program Understanding: A Look at Programming Expertise in Industry. Empirical Studies of Programmers. Palo Alto: Fifth Workshop, 6-25.
8. 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.
9. Briand, L., El Emam, K., and Morasca, S. 1996. On the application of measurement theory in software engineering. Empirical Software Engineering 1: 61-88.
10. Buckley, J., and Cahill, T. 1997. Measuring Comprehension Behaviour Through System Monitoring, Int. Workshop on Empirical Studies of Software Maintenance, Bari, Italy, 109-113.
11. Budgen, D., and Thomson, M. 2003. CASE tool Evaluation: Experiences from an empirical study. Journal of Systems and Software 67: 55-75.
12. Chi, M. 1997. Quantifying qualitative analyzes of verbal data: A practical guide. The Journal of the Learning Sciences 6(3): 271-315.
13. 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): November, 1268-1287.
14. 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.
15. Delbecq, A. L., Van de Ven, A. H., Gustafson, D. H. 1975. Group Techniques for Program Planning. Scott. Glenview, IL: Foresman & Co.
16. DeVaus, D. A. 1996. Surveys in Social Research. 4th edition. London: UCL Press.
17. Draper, S. 2004. The Hawthorne Effect. http://www.psy.gla.ac.uk/~steve/ hawth.html.
18. Ericcson, K., and Simon, H. 1984. Protocol Analysis: Verbal Reports as Data. Cambridge, MA: The MIT Press.
19. Foddy, W. 1994. Constructing Questions for Interviews and Questionnaires: Theory and Practice in Social Research. Cambridge, MA: Cambridge University Press.
20. Hassan, A., Holt, R., and Mockus, A. 2004. MSR 20004: The international workshop on mining software repositories. Proc. ICSE 2004: International Conference on Software Engineering, Scotland, UK, May, pp. 23-28.
21. Herbsleb, J., and Mockus, A. 2003. An empirical study of speed and communication in globally distributed software development. IEEE Transactions Software Engineering 29(6): 481-494.
22. Hungerford, B., Hevner, A., and Collins, R. 2004. Reviewing software diagrams: A cognitive study. IEEE, Transactions Software Engineering 30(2): 82-96.
23. Iivari, J. 1996. Why are CASE tools not used? Communications of the ACM 39(10): October, 94-103.
24. Jick, T. 1979. Mixing qualitative and quantitative methods: Triangulation in action. Administrative Science Quarterly 24(4): December, 602-611.
25. Jordan, B., and Henderson, A. 1995. Interaction analysis: Foundations and practice. The Journal of the Learning Sciences 4(1): 39-103.
26. Jørgensen, M. 1995. An empirical study of software maintenance tasks. Software Maintenance: Research and Practice 7: 27-48.
27. Keller, R., Schauer, R., Robitaille, S., and Page, P. 1999. Pattern-based reverse engineering of design components. In Proc, Int. Conf. Software Engineering, Los Angeles, CA, pp. 226-235.
28. Kemerer, C. F., and Slaughter, S. A. 1997. Determinants of software maintenance profiles: An empirical investigation. Software Maintenance: Research and Practice 9: 235-251.
29. Kensing, F. 1998. Prompted Reflections: A Technique for Understanding Complex Work, interactions, January/February, 7-15.
30. Lethbridge, T. C. 2000. Priorities for the education and training of software engineers. Journal of Systems and Software 53(1): 53-71.
31. Lethbridge, T. C., and Anquetil, N. 2000. Evaluation of approaches to clustering for program comprehension and remodularization. In H. Erdogmus and O. Tanir, (eds.). Advances in Software Engineering: Topics in Evolution, Comprehension and Evaluation, New York: Springer-Verlag.
32. Lethbridge, T. C., and Laganière, R. 2001. Object-Oriented Software Engineering: Practical Software Development Using UML and Java. London: McGraw-Hill.
33. Miles, M. B. 1979. Qualitative data as an attractive nuisance: The problem of analysis. Administrative Science Quarterly 24(4): 590-601.
34. Miles, M. B., and Huberman, A. M. 1994. Qualitative Data Analysis: An Expanded Sourcebook. 2nd edition. Thousand Oaks, CA: Sage Publications.
35. Mockus, A., Fielding, R. T., and Herbsleb, J. D. 2002. Two case studies of open source software development: Apache and mozilla. ACM Trans. on Software Engineering and Methodology 11(3) 209-246.
36. NASA. SEL COTS Study Phase 1 Initial Characterization Study Report, SEL-98-001, August 1998, http://sel.gsfc.nasa.gov/website/documents/online-oc. htm.
37. Nielsen, J. 1997. The Use and Misuse of Focus Groups, http://www.useit.com/papers/focusgroups.html.
38. Perry, D. E., Staudenmayer, N., and Votta, L. 1994. People, organizations, and process improvement. IEEE Software July, 37-45.
39. Pfleeger, S. L., and Hatton, L. 1997. Investigating the influence of formal methods. Computer February, 33-43.
40. Pfleeger, S., and Kitchenham, B. 2001. Principles of survey research Part 1: Turning lemons into lemonade. Software Engineering Notes 26(6) 16-18.
41. 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 Software Engineering 23(6): 329-346.
42. Punter, T., Ciolkowski, M., Freimut, B., John, I. 2003. Conducting on-line surveys in software engineering. Proceedings Int. Symp. on Empirical Software Eng. '03, pp. 80-88.
43. Rainer, A., and Hall, T. 2003. A quantitative and qualitative analysis of factors affecting software processes. Journal of Systems and Software 66: 7-21.
44. Robbins, S. P. 1994. Essentials of Organizational Behavior. 4th edition. Englewood Cliffs, NJ: Prentice Hall.
45. Robillard, P. N., d'Astous, P., Détienne, D., and Visser, W. 1998. Measuring cognitive activities in software engineering. Proc. 20th Int. Conf. Software Engineering, Japan, pp. 292-300.
46. Sayyad-Shirabad, J., Lethbridge, T. C., and Lyon, S. 1997. A little knowledge can go a long way towards program understanding. Proc. 5th Int. Workshop on Program Comprehension. Dearborn, MI: IEEE, pp. 111-117.
47. Sayyad-Shirabad, J., Lethbridge, T. C., and Matwin, S. 2003. Applying data mining to software maintenance records. Proc CASCON 2003, Toronto, October, IBM, in ACM Digital Library, pp. 136-148.
48. Scacchi, W. 2003. Issues and experiences in modeling open source software processes. Proc. 3rd. Workshop on Open Source Software Engineering, Portland, OR: 25th. Int. Conf. Software Engineering, May.
49. 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): July, 559-572.
50. 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.
51. Seigel, S., and Castellan, N. J. 1988. Nonparametric Statistics for the Behavioral Sciences. 2nd edition. Boston, MA: McGraw-Hill.
52. Shull, F., Lanubile, F., and Basili, V. 2000. Investigating reading techniques for object-oriented framework learning. IEEE Transactions on Software Engineering 26: 1101-1118.
53. Sim S. E., and Holt, R. C. 1998. The ramp-up problem in software projects: A case study of how software immigrants naturalize. Proc. 20th Int. Conf. on Software Engineering, Kyoto, Japan, April, pp. 361-370.
54. Sim, S. E., Clarke, C. L. A., and Holt, R. C. 1998. Archetypal source code searches: A survey of software developers and maintainers. Proc. Int. Workshop on Program Comprehension, Ischia, Italy, pp. 180-187.
55. Singer, J., Lethbridge, T., Vinson, N., and Anquetil, N. 1997. An examination of software engineering work practices. Proc. CASCON. IBM Toronto, 209-223, October.
56. Singer, J. 1998. Practices of software maintenance. Proc. Int. Conf. on Software Maintenance. Washington, DC, November, pp. 139-145.
57. Singer, J., Lethbridge, T. C., and Vinson, N. 1998. Work practices as an alternative method to assist tool design in software engineering. Proc. International Workshop on Program Comprehension. Ischia, Italy, pp. 173-179.
58. Singer, J., and Vinson, N. 2002. Ethical issues in empirical studies of software engineering. IEEE Transactions on Software Engineering, 28: 1171-1180.
59. Snelling, L., and Bruce-Smith, D. 1997. The work mapping technique. Interactions 25-31, July/August.
60. Somé, S. S., and Lethbridge T. C. 1998. Parsing minimizing when extracting information from code in the presence of conditional compilation. Proc. 6th IEEE International Workshop on Program Comprehension. Italy, June pp. 118-125.
61. Teasley, S., Covi, L, Krishnan, M., and Olson, J. 2002. Rapid software development through team collocation. IEEE Transactions on Software Engineering 28: 671-683.
62. von Mayrhauser, A., and Vans, A. M. 1993. From program comprehension to tool requirements for an industrial environment. Proc. of the 2nd Workshop on Program Comprehension, Capri, Italy, July, pp. 78-86.
63. 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, pp. 1-38.
64. Walenstein, A. 2003. Observing and measuring cognitive support: Steps toward systematic tool evaluation and engineering. Proc. the 11th IEEE Workshop on Program Comprehension.
65. 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): October, 62-77.
66. Williams, L., Kessler, R. R., Cunningham, W., and Jeffries, R. 2000. Strengthening the case for pair-programming, IEEE Software July/Aug, 19-25.
67. Wolf, A., and Rosenblum, D. 1993. A study in software process data capture and analysis. Proc. 2nd International Conference on Software Process February, pp. 115-124.
68. Wu, J., Graham, T., Smith, P. 2003. A study of collaboration in software design. Proc. Int. Symp. Empirical Software Eng. '03.