[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
10.1007/11767718_14guideproceedingsArticle/Chapter ViewAbstractPublication PagesConference Proceedingsacm-pubtype
Article

Difficulties in establishing a defect management process: a case study

Published: 12 June 2006 Publication History

Abstract

A well-organized defect management process is one of the success factors for implementing software projects in time and in budget. The defect management process includes defect prevention, defect discovery and resolution, defect causal analysis, and the process improvement. However, establishing an organization-wide defect management process is a complicated task. The main research question in this paper is what kind of difficulties organizations have regarding the defect management process. Our findings show that problems are related to defect resolution reports, limited project resources for fixing defects, and challenges in creating a test environment. Results are based on our observations from four case organizations. The main contribution of this study is to help organizations to identify and avoid typical problems with defect management.

References

[1]
Florac, W.: Software quality measurement a framework for counting problems and defects. Technical Report CMU/SEI-92-TR-22 (1992).
[2]
Hirmanpour, I., Schofield, J.: Defect management through the personal software process. Crosstalk, The Journal of Defense Software Engineering (2003).
[3]
Mays, R.G., Jones, C.L., Holloway, G.J., Studinski, D.P.: Experiences with defect prevention. IBM Syst. J. 29(1) (1990) 4-32.
[4]
Office of Government Commerce: ITIL Service Support. The Stationary Office, UK (2002).
[5]
Leszak, M., Perry, D.E., Stoll, D.: A case study in root cause defect analysis. In: ICSE '00: Proceedings of the 22nd international conference on Software engineering, New York, NY, USA, ACM Press (2000) 428-437.
[6]
El-Emam, K., Wieczorek, I.: The repeatability of code defect classifications. Technical Report. International Software Engineering Research Network, ISERN-98-09. (1998).
[7]
Humphrey, W.S.: A personal commitment to software quality. In: ESEC. (1995) 5-7.
[8]
Jalote, P.: CMM in Practise, Processes for Executing Software Projects at Infosys. Addison-Wesley (2000).
[9]
Jäntti, M., Toroi, T.: Uml-based testing: A case study. In: Proceedings of NWUML'2004. 2nd Nordic Workshop on the Unified Modeling Language, Turku: Turku Centre for Computer Science (2004) 33-44.
[10]
Kruchten, P.: The Rational Unified Process: An Introduction. Addison-Wesley (2001).
[11]
Yin, R.: Case Study Research: Design and Methods. Beverly Hills, CA: Sage Publishing (1994).
[12]
Binder, R.: Testing Object-Oriented Systems: Models, Patterns, and Tools. Addison-Wesley (2000).
[13]
Quality Assurance Institute: A software defect management process. Research Report number 8 (1995).
[14]
Eisenhardt, K.: Building theories from case study research. Academy of Management Review 14 (1989) 532-550.
[15]
Ahonen, J.J., Junttila, T., Sakkinen, M.: Impacts of the organizational model on testing: Three industrial cases. Empirical Softw. Engg. 9(4) (2004) 275-296.
[16]
Henninger, S.: Using software process to support learning software organizations. In: 1st International Workshop on Learning Software Organizations, Kaiserlautern (1999).
[17]
Hartmann, J., Imoberdorf, C., Meisinger, M.: Uml-based integration testing. In: ISSTA '00: Proceedings of the 2000 ACM SIGSOFT international symposium on Software testing and analysis, New York, NY, USA, ACM Press (2000) 60-70.
[18]
Gilb, T., Graham, D.: Software Inspection. Addison-Wesley (1993).
[19]
Card, D.N.: Learning from our mistakes with defect causal analysis. IEEE Software 15(1) (1998) 56-63.
[20]
Office of Government Commerce: ITIL Service Delivery. The Stationary Office, UK (2002).

Cited By

View all
  • (2010)Applying DPPIProceedings of the 11th international conference on Product-Focused Software Process Improvement10.1007/978-3-642-13792-1_9(92-106)Online publication date: 21-Jun-2010
  • (2007)A checklist for evaluating the software problem management modelProceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering10.5555/1332044.1332046(7-12)Online publication date: 13-Feb-2007

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image Guide Proceedings
PROFES'06: Proceedings of the 7th international conference on Product-Focused Software Process Improvement
June 2006
473 pages
ISBN:3540346821
  • Editors:
  • Jürgen Münch,
  • Matias Vierimaa

Publisher

Springer-Verlag

Berlin, Heidelberg

Publication History

Published: 12 June 2006

Qualifiers

  • Article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 21 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2010)Applying DPPIProceedings of the 11th international conference on Product-Focused Software Process Improvement10.1007/978-3-642-13792-1_9(92-106)Online publication date: 21-Jun-2010
  • (2007)A checklist for evaluating the software problem management modelProceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering10.5555/1332044.1332046(7-12)Online publication date: 13-Feb-2007

View Options

View options

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media