Myths in software engineering: from the other side
TAP'10 Proceedings of the 4th international conference on Tests and proofs
Evolution of developer collaboration on the jazz platform: a study of a large scale agile project
Proceedings of the 4th India Software Engineering Conference
Empirical software engineering at Microsoft Research
Proceedings of the ACM 2011 conference on Computer supported cooperative work
Don't touch my code!: examining the effects of ownership on software quality
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Mining development repositories to study the impact of collaboration on software systems
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
A field study of refactoring challenges and benefits
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Influence of confirmation biases of developers on software quality: an empirical study
Software Quality Control
Improving scenario testing process by adding value-based prioritization: an industrial case study
Proceedings of the 2013 International Conference on Software and System Process
An algorithmic approach to missing data problem in modeling human aspects in software development
Proceedings of the 9th International Conference on Predictive Models in Software Engineering
Dynamic networked organizations for software engineering
Proceedings of the 2013 International Workshop on Social Software Engineering
Organizational social structures for software engineering
ACM Computing Surveys (CSUR)
Hi-index | 0.00 |
Studies have shown that social factors in development organizations have adramatic effect on software quality.Separately,program dependencyinformation has also been used successfully to predict which software componentsare more fault prone. Interestingly, the influence of these two phenomenahaveonly been studied separately.Intuition and practical experience suggests,however, that task assignment (i.e. who worked on which components and howmuch) and dependency structure (which components have dependencies on others)together interact toinfluence the quality of the resulting software.Westudy the influence ofcombined socio-technical software networks onthe fault-proneness of individual software components within a system.Thenetworkproperties of a software component in thiscombined network are ableto predict if an entity is failure prone with greater accuracy than priormethods which use dependency or contribution information in isolation.Weevaluate our approach in different settings by using it on Windows Vista andacross six releases of the Eclipse development environment including usingmodels built from one release to predict failure prone components in the nextrelease.We compare this to previous work.In every case, our method performsas well or better and is able to more accurately identify those softwarecomponents that have more post-release failures, with precision and recallrates as high as 85%.