The secret life of bugs: Going past the errors and omissions in software repositories
Authors:
Top Cited Papers
- 1 January 2009
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 02705257,p. 298-308
Abstract
Every bug has a story behind it. The people that discover and resolve it need to coordinate, to get information from documents, tools, or other people, and to navigate through issues of accountability, ownership, and organizational structure. This paper reports on a field study of coordination activities around bug fixing that used a combination of case study research and a survey of software professionals. Results show that the histories of even simple bugs are strongly dependent on social, organizational, and technical knowledge that cannot be solely extracted through automation of electronic repositories, and that such automation provides incomplete and often erroneous accounts of coordination. The paper uses rich bug histories and survey results to identify common bug fixing coordination patterns and to provide implications for tool designers and researchers of coordination in software development.Keywords
This publication has 17 references indexed in Scilit:
- What makes a good bug report?2008
- Information Needs in Collocated Software Development Teams2007
- The Social Dynamics of Pair Programming29th International Conference on Software Engineering (ICSE'07), 2007
- Maintaining mental models2006
- How software engineers use documentation: the state of the practiceIEEE Software, 2003
- An empirical study of speed and communication in globally distributed software developmentIEEE Transactions on Software Engineering, 2003
- The importance of trust in software engineers' assessment and choice of information sourcesInformation and Organization, 2002
- Splitting the organization and integrating the code1999
- Coordination in software developmentCommunications of the ACM, 1995
- People, organizations, and process improvementIEEE Software, 1994