\input zb-basic
\input zb-ioport
\iteman{io-port 06104061}
\itemau{Ostrand, Thomas J.; Weyuker, Elaine J.}
\itemti{Can file level characteristics help identify system level fault-proneness?}
\itemso{Eder, Kerstin (ed.) et al., Hardware and software: verification and testing. 7th international Haifa verification conference, HVC 2011, Haifa, Israel, December 6--8, 2011. Revised selected papers. Berlin: Springer (ISBN 978-3-642-34187-8/pbk). Lecture Notes in Computer Science 7261, 176-189 (2012).}
\itemab
Summary: In earlier studies of multiple-release systems, we observed that the number of changes and the number of faults in a file in the past release, the size of a file, and the maturity of a file are all useful predictors of the file's fault proneness in the next release. In each case the data needed to make predictions have been extracted from a configuration management system which provides integrated change management and version control functionality. In this paper we investigate analogous questions for the system as a whole, rather than looking at its constituent files. Using two large industrial software systems, each with many field releases, we examine a number of questions relating defects to system maturity, how often the system has changed, the size difference of a release from the prior release, and the length of time a release has been under development before the start of system testing. Most of our observations match neither our intuition, nor the relations observed for these two systems when similar questions were asked at the file level.
\itemrv{~}
\itemcc{}
\itemut{software fault prediction; fault density; system maturity; system size; system changes; elapsed development time}
\itemli{doi:10.1007/978-3-642-34188-5\_16}
\end