Maintaining mental models: a study of developer work habits

ABSTRACT

To understand developers' typical tools, activities, and practices and their satisfaction with each, we conducted two surveys and eleven interviews. We found that many problems arose because developers were forced to invest great effort recovering implicit knowledge by exploring code and interrupting teammates and this knowledge was only saved in their memory. Contrary to expectations that email and IM prevent expensive task switches caused by face-to-face interruptions, we found that face-to-face communication enjoys many advantages. Contrary to expectations that documentation makes understanding design rationale easy, we found that current design documents are inadequate. Contrary to expectations that code duplication involves the copy and paste of code snippets, developers reported several types of duplication. We use data to characterize these and other problems and draw implications for the design of tools for their solution.

REFERENCES

• 1: Cleidson R. B. de Souza , David Redmiles , Li-Te Cheng , David Millen , John Patterson, Sometimes you need to see through walls: a field study of application programming interfaces, Proceedings of the 2004 ACM conference on Computer supported cooperative work, November 06-10, 2004, Chicago, Illinois, USA [doi>10.1145/1031607.1031620]
• 2: Morten Hertzum , Annelise Mark Pejtersen, The information-seeking practices of engineers: searching for documents as well as for people, Information Processing and Management: an International Journal, v.36 n.5, p.761-778, Sept. 2000 [doi>10.1016/S0306-4573(00)00011-X]
• 3: Toshihiro Kamiya , Shinji Kusumoto , Katsuro Inoue, CCFinder: a multilinguistic token-based code clone detection system for large scale source code, IEEE Transactions on Software Engineering, v.28 n.7, p.654-670, July 2002 [doi>10.1109/TSE.2002.1019480]
• 4: Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Videira Lopes, C., Loingtier, J.-M., and Irwin, J. Aspect Oriented Programming. In Proceedings of ECOOP, 1997.
• 5: Miryung Kim , Lawrence Bergman , Tessa Lau , David Notkin, An Ethnographic Study of Copy and Paste Programming Practices in OOPL, Proceedings of the 2004 International Symposium on Empirical Software Engineering, p.83-92, August 19-20, 2004 [doi>10.1109/ISESE.2004.10]
• 6: Miryung Kim , Vibha Sazawal , David Notkin , Gail Murphy, An empirical study of code clone genealogies, Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering, September 05-09, 2005, Lisbon, Portugal
• 7: Thomas P. Moran , John M. Carroll, Design rationale: concepts, techniques, and use, Lawrence Erlbaum Associates, Inc., Mahwah, NJ, 1996
• 8: David Lorge Parnas, On ICSE's “most influential” papers, ACM SIGSOFT Software Engineering Notes, v.20 n.3, p.29-32, July 1995 [doi>10.1145/219308.219312]
• 9: Dewayne E. Perry , Nancy Staudenmayer , Lawrence G. Votta, People, Organizations, and Process Improvement, IEEE Software, v.11 n.4, p.36-45, July 1994 [doi>10.1109/52.300082]
• 10: Mary Beth Rosson , John M. Carroll, The reuse of uses in Smalltalk programming, ACM Transactions on Computer-Human Interaction (TOCHI), v.3 n.3, p.219-253, Sept. 1996 [doi>10.1145/234526.234530]
• 11: Ken Schwaber , Mike Beedle, Agile Software Development with Scrum, Prentice Hall PTR, Upper Saddle River, NJ, 2001
• 12: Janice Singer , Timothy Lethbridge , Norman Vinson , Nicolas Anquetil, An examination of software engineering work practices, Proceedings of the 1997 conference of the Centre for Advanced Studies on Collaborative research, p.21, November 10-13, 1997, Toronto, Ontario, Canada
• 13: Mark Weiser, Program slicing, Proceedings of the 5th international conference on Software engineering, p.439-449, March 09-12, 1981, San Diego, California, United States
• 14: George Wright , Peter Ayton, Eliciting and modelling expert knowledge, Decision Support Systems, v.3 n.1, p.13-26, March 1987 [doi>10.1016/S0167-9236(00)00124-X]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.7 Distribution, Maintenance, and Enhancement
          Subjects: Documentation

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.6 Programming Environments
          Subjects: Integrated environments
      D.2.9 Management
          Subjects: Programming teams

General Terms:
Design, Documentation, Experimentation, Human Factors

Keywords:
agile software development, code duplication, code ownership, communication, debugging, interruptions