loading...
Test-Driven Development as a Defect-Reduction Practice
Denver, Colorado November 17-November 21
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ISSRE.2003.125102914th International Symposium on Softw ...
 This Article 
 
Buy PURCHASE ARTICLE: $19
PDF
HTML
Buy IEEE Xplore Subscribers
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
ASCII Text
x 
 
Laurie Williams, E. Michael Maximilien, Mladen Vouk, "Test-Driven Development as a Defect-Reduction Practice," Software Reliability Engineering, International Symposium on, pp. 34, 14th International Symposium on Software Reliability Engineering, 2003.
 
 
BibTex
x
 
@article{ 10.1109/ISSRE.2003.1251029,
author = {Laurie Williams and E. Michael Maximilien and Mladen Vouk},
title = {Test-Driven Development as a Defect-Reduction Practice},
journal ={Software Reliability Engineering, International Symposium on},
volume = {0},
year = {2003},
issn = {1071-9458},
pages = {34},
doi = {http://doi.ieeecomputersociety.org/10.1109/ISSRE.2003.1251029},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - Software Reliability Engineering, International Symposium on
TI - Test-Driven Development as a Defect-Reduction Practice
SN - 1071-9458
SP
EP
A1 - Laurie Williams,
A1 - E. Michael Maximilien,
A1 - Mladen Vouk,
PY - 2003
KW - null
VL - 0
JA - Software Reliability Engineering, International Symposium on
ER -
 
Laurie Williams, North Carolina State University
E. Michael Maximilien, IBM Corporation and North Carolina State University
Mladen Vouk, North Carolina State University
Test-driven development is a software development practice that has been used sporadically for decades. With this practice, test cases (preferably automated) are incrementally written before production code is implemented. Test-driven development has recently re-emerged as a critical enabling practice of the Extreme Programming software development methodology. We ran a case study of this practice at IBM. In the process, a thorough suite of automated test cases was produced after UML design. In this case study, we found that the code developed using a test-driven development practice showed, during functional verification and regression tests, approximately 40% fewer defects than a baseline prior product developed in a more traditional fashion. The productivity of the team was not impacted by the additional focus on producing automated test cases. This test suite will aid in future enhancements and maintenance of this code. The case study and the results are discussed in detail.
Citation:
Laurie Williams, E. Michael Maximilien, Mladen Vouk, "Test-Driven Development as a Defect-Reduction Practice," issre, pp.34, 14th International Symposium on Software Reliability Engineering, 2003
Usage of this product signifies your acceptance of the Terms of Use.