Agents to assist in finding help
Proceedings of the SIGCHI conference on Human Factors in Computing Systems
Evaluating expertise recommendations
GROUP '01 Proceedings of the 2001 International ACM SIGGROUP Conference on Supporting Group Work
Expertise browser: a quantitative approach to identifying expertise
Proceedings of the 24th International Conference on Software Engineering
How Developers Drive Software Evolution
IWPSE '05 Proceedings of the Eighth International Workshop on Principles of Software Evolution
Versioning Systems for Evolution Research
IWPSE '05 Proceedings of the Eighth International Workshop on Principles of Software Evolution
Using task context to improve programmer productivity
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Determining Implementation Expertise from Bug Reports
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
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
SpyWare: a change-aware development toolset
Proceedings of the 30th international conference on Software engineering
A degree-of-knowledge model to capture source code familiarity
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Syde: a tool for collaborative software development
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Refining code ownership with synchronous changes
Empirical Software Engineering
| Hi-index | 0.00 |
The expertise of a software developer is said to be a crucial factor for the development time required to complete a task. Even if this hypothesis is intuitive, research has not yet quantified the effect of developer expertise on development time. A related problem is that the design space for expertise metrics is large; out of the various automated expertise metrics proposed, we do not know which metric most reliably captures expertise. What prevents a proper evaluation of expertise metrics and their relation with development time is the lack of data on development tasks, such as their precise duration. Fortunately, this data is starting to become available in the form of growing developer interaction repositories. We show that applying MSR techniques to these developer interaction repositories gives us the necessary tools to perform such an evaluation.