%0 Conference Paper %B Proceedings of the 17th International Symposium on Software Reliability Engineering %D 2009 %T Putting it All Together: Using Socio-Technical Networks to Predict Failures %A Christian Bird %A Nachiappan Nagappan %A Devanbu, Premkumar %A Gall, Harald %A Brendan Murphy %K eclipse %K microsoft %K social network %K vista %K windows %X Studies have shown that social factors in development organizations have a dramatic effect on software quality. Separately, program dependency information has also been used successfully to predict which software components are more fault prone. Interestingly, the influence of these two phenomena have only been studied separately. Intuition and practical experience suggests, however, that task assignment (i.e. who worked on which components and how much) and dependency structure (which components have dependencies on others) together interact to influence the quality of the resulting software. We study the influence of combined socio-technical software networks on the fault-proneness of individual software components within a system. The network properties of a software component in this combined network are able to predict if an entity is failure prone with greater accuracy than prior methods which use dependency or contribution information in isolation. We evaluate our approach in different settings by using it on Windows Vista and across six releases of the Eclipse development environment including using models built from one release to predict failure prone components in the next release. We compare this to previous work. In every case, our method performs as well or better and is able to more accurately identify those software components that have more post-release failures, with precision and recall rates as high as 85%. %B Proceedings of the 17th International Symposium on Software Reliability Engineering %> https://flosshub.org/sites/flosshub.org/files/bird2009pat.pdf %0 Conference Paper %B Proceedings of the 30th international conference on Software engineering %D 2008 %T A tale of four kernels %A Diomidis Spinellis %K comparison %K freebsd %K linux %K open source %K opensolaris %K proprietary software %K windows %K wrk %X The FreeBSD, GNU/Linux, Solaris, and Windows operating systems have kernels that provide comparable facilities. Interestingly, their code bases share almost no common parts, while their development processes vary dramatically. We analyze the source code of the four systems by collecting metrics in the areas of file organization, code structure, code style, the use of the C preprocessor, and data organization. The aggregate results indicate that across various areas and many different metrics, four systems developed using wildly different processes score comparably. This allows us to posit that the structure and internal quality attributes of a working, non-trivial software artifact will represent first and foremost the engineering requirements of its construction, with the influence of process being marginal, if any. %B Proceedings of the 30th international conference on Software engineering %S ICSE '08 %I ACM %C New York, NY, USA %P 381–390 %@ 978-1-60558-079-1 %U http://doi.acm.org/10.1145/1368088.1368140 %R 10.1145/1368088.1368140