A field study of the software design process for large systems
Communications of the ACM
Software psychology: the need for an interdisciplinary program
Human-computer interaction
The persistence and transfer of learning in industrial settings
Management Science
The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
The role of knowledge in software development
Communications of the ACM
Predicting Fault Incidence Using Software Change History
IEEE Transactions on Software Engineering
The cathedral and the bazaar: musings on Linux and open source by an accidental revolutionary
The cathedral and the bazaar: musings on Linux and open source by an accidental revolutionary
Organizational Learning: Creating, Retaining, and Transferring Knowledge
Organizational Learning: Creating, Retaining, and Transferring Knowledge
On the Job Learning in the Software Industry: Corporate Culture and the Acquisition of Knowledge
On the Job Learning in the Software Industry: Corporate Culture and the Acquisition of Knowledge
Metrics and Models in Software Quality Engineering
Metrics and Models in Software Quality Engineering
Hipikat: recommending pertinent software development artifacts
Proceedings of the 25th International Conference on Software Engineering
An Empirical Study of Speed and Communication in Globally Distributed Software Development
IEEE Transactions on Software Engineering
Shared mental models and coordination in large-scale, distributed software development
Shared mental models and coordination in large-scale, distributed software development
Populating a Release History Database from Version Control and Bug Tracking Systems
ICSM '03 Proceedings of the International Conference on Software Maintenance
MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
How Developers Drive Software Evolution
IWPSE '05 Proceedings of the Eighth International Workshop on Principles of Software Evolution
Automatic Identification of Bug-Introducing Changes
ASE '06 Proceedings of the 21st IEEE/ACM International Conference on Automated Software Engineering
CSCW '06 Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Empirical Analysis of Object-Oriented Design Metrics for Predicting High and Low Severity Faults
IEEE Transactions on Software Engineering
Does a programmer's activity indicate knowledge of code?
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
The influence of organizational structure on software quality: an empirical case study
Proceedings of the 30th international conference on Software engineering
Exploring the relationship of history characteristics and defect count: an empirical study
DEFECTS '08 Proceedings of the 2008 workshop on Defects in large software systems
Journal of Systems and Software
Empirical Software Engineering
Can developer-module networks predict failures?
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Learning from Experience in Software Development: A Multilevel Analysis
Management Science
The promises and perils of mining git
MSR '09 Proceedings of the 2009 6th IEEE International Working Conference on Mining Software Repositories
Fair and balanced?: bias in bug-fix datasets
Proceedings of the the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops
Secure open source collaboration: an empirical study of linus' law
Proceedings of the 16th ACM conference on Computer and communications security
Why Programs Fail, Second Edition: A Guide to Systematic Debugging
Why Programs Fail, Second Edition: A Guide to Systematic Debugging
EQ-mine: predicting short-term defects for software evolution
FASE'07 Proceedings of the 10th international conference on Fundamental approaches to software engineering
The code orb: supporting contextualized coding via at-a-glance views (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
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
Bug prediction based on fine-grained module histories
Proceedings of the 34th International Conference on Software Engineering
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
Studying volatility predictors in open source software
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
How, and why, process metrics are better
Proceedings of the 2013 International Conference on Software Engineering
Dual ecological measures of focus in software development
Proceedings of the 2013 International Conference on Software Engineering
Distributed development considered harmful?
Proceedings of the 2013 International Conference on Software Engineering
WikiWho: precise and efficient attribution of authorship of revisioned content
Proceedings of the 23rd international conference on World wide web
Hi-index | 0.00 |
Recent research indicates that "people" factors such as ownership, experience, organizational structure, and geographic distribution have a big impact on software quality. Understanding these factors, and properly deploying people resources can help managers improve quality outcomes. This paper considers the impact of code ownership and developer experience on software quality. In a large project, a file might be entirely owned by a single developer, or worked on by many. Some previous research indicates that more developers working on a file might lead to more defects. Prior research considered this phenomenon at the level of modules or files, and thus does not tease apart and study the effect of contributions of different developers to each module or file. We exploit a modern version control system to examine this issue at a fine-grained level. Using version history, we examine contributions to code fragments that are actually repaired to fix bugs. Are these code fragments "implicated" in bugs the result of contributions from many? or from one? Does experience matter? What type of experience? We find that implicated code is more strongly associated with a single developer's contribution; our findings also indicate that an author's specialized experience in the target file is more important than general experience. Our findings suggest that quality control efforts could be profitably targeted at changes made by single developers with limited prior experience on that file.