Survey reproduction of defect reporting in industrial software development
(2011) Empirical Software Engineering and Measurement (ESEM), 2011 International Symposium on p.197-206- Abstract
- Abstract in Undetermined
Context: Defect reporting is an important part of software development in-vivo, but previous work from open source context suggests that defect reports often have insufficient information for defect fixing. Objective: Our goal was to reproduce and partially replicate one of those open source studies in industrial context to see how well the results could be generalized. Method: We surveyed developers from six industrial software development organizations about the defect report information, from three viewpoints: concerning quality, usefulness and automation possibilities of the information. Seventy-four developers out of 142 completed our survey. Results: Our reproduction confirms the results of the prior... (More) - Abstract in Undetermined
Context: Defect reporting is an important part of software development in-vivo, but previous work from open source context suggests that defect reports often have insufficient information for defect fixing. Objective: Our goal was to reproduce and partially replicate one of those open source studies in industrial context to see how well the results could be generalized. Method: We surveyed developers from six industrial software development organizations about the defect report information, from three viewpoints: concerning quality, usefulness and automation possibilities of the information. Seventy-four developers out of 142 completed our survey. Results: Our reproduction confirms the results of the prior study in that "steps to reproduce" and "observed behaviour" are highly important defect information. Our results extend the results of the prior study as we found that "part of the application", "configuration of the application", and "operating data" are also highly important, but they were not surveyed in the prior study. Finally, we classified defect information as "critical problems", "solutions", "boosters", and "essentials" based on the survey answers. Conclusion: The quality of defect reports is a problem in the software industry as well as in the open source community. Thus, we suggest that a part of the defect reporting should be automated since many of the defect reporters lack technical knowledge or interest to produce high-quality defect reports. (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/2225547
- author
- Eero, Laukkanen and Mäntylä, Mika LU
- organization
- publishing date
- 2011
- type
- Chapter in Book/Report/Conference proceeding
- publication status
- published
- subject
- keywords
- Companies, Context, Hardware, Programming, Software, Software engineering, Testing, software debugging, software maintenance, software quality
- host publication
- International Symposium on Empirical Software Engineering and Measurement
- pages
- 10 pages
- publisher
- IEEE - Institute of Electrical and Electronics Engineers Inc.
- conference name
- Empirical Software Engineering and Measurement (ESEM), 2011 International Symposium on
- conference location
- Banff, Alberta, Canada
- conference dates
- 2011-09-22 - 2011-09-23
- external identifiers
-
- scopus:84858725905
- ISSN
- 1949-3789
- 1938-6451
- ISBN
- 978-1-4577-2203-5
- DOI
- 10.1109/ESEM.2011.28
- language
- English
- LU publication?
- no
- id
- 3310ddc9-c58f-4341-875a-aa5b8d83301e (old id 2225547)
- date added to LUP
- 2016-04-01 10:24:48
- date last changed
- 2024-01-06 15:59:22
@inproceedings{3310ddc9-c58f-4341-875a-aa5b8d83301e,
abstract = {{Abstract in Undetermined<br/>Context: Defect reporting is an important part of software development in-vivo, but previous work from open source context suggests that defect reports often have insufficient information for defect fixing. Objective: Our goal was to reproduce and partially replicate one of those open source studies in industrial context to see how well the results could be generalized. Method: We surveyed developers from six industrial software development organizations about the defect report information, from three viewpoints: concerning quality, usefulness and automation possibilities of the information. Seventy-four developers out of 142 completed our survey. Results: Our reproduction confirms the results of the prior study in that "steps to reproduce" and "observed behaviour" are highly important defect information. Our results extend the results of the prior study as we found that "part of the application", "configuration of the application", and "operating data" are also highly important, but they were not surveyed in the prior study. Finally, we classified defect information as "critical problems", "solutions", "boosters", and "essentials" based on the survey answers. Conclusion: The quality of defect reports is a problem in the software industry as well as in the open source community. Thus, we suggest that a part of the defect reporting should be automated since many of the defect reporters lack technical knowledge or interest to produce high-quality defect reports.}},
author = {{Eero, Laukkanen and Mäntylä, Mika}},
booktitle = {{International Symposium on Empirical Software Engineering and Measurement}},
isbn = {{978-1-4577-2203-5}},
issn = {{1949-3789}},
keywords = {{Companies; Context; Hardware; Programming; Software; Software engineering; Testing; software debugging; software maintenance; software quality}},
language = {{eng}},
pages = {{197--206}},
publisher = {{IEEE - Institute of Electrical and Electronics Engineers Inc.}},
title = {{Survey reproduction of defect reporting in industrial software development}},
url = {{http://dx.doi.org/10.1109/ESEM.2011.28}},
doi = {{10.1109/ESEM.2011.28}},
year = {{2011}},
}