The DOI matches its Crossref record.
Expertise Browser: a quantitative approach to identifying expertise
Abstract
Finding relevant expertise is a critical need in collaborative software engineering, particularly in geographically distributed developments. We introduce a tool, called Expertise Browser (ExB), that uses data from change management systems to locate people with desired expertise. It uses a quantification of experience, and presents evidence to validate this quantification as a measure of expertise. The tool enables developers, for example, to easily distinguish someone who has worked only briefly in a particular area of the code from someone who has more extensive experience, and to locate people with broad expertise throughout large parts of the product, such as modules or even subsystems. In addition, it allows a user to discover expertise profiles for individuals or organizations. Data from a deployment of the tool in a large software development organization shows that newer, remote sites tend to use the tool for expertise location more frequently. Larger, more established sites used the tool to find expertise profiles for people or organizations. We conclude by describing extensions that provide continuous awareness of ongoing work and an interactive, quantitative resume/spl acute/.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
An empirical study of speed and communication in globally distributed software development
Herbsleb, J. D., & Mockus, A. (2003) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2003.1205177 · Cited by 997
Self-citationAnvik, J., Hiew, L., & Murphy, G. C. (2006) · Proceedings of the 28th international conference on Software engineering · doi:10.1145/1134285.1134336 · Cited by 924
A large-scale empirical study of just-in-time quality assurance
Kamei, Y., Shihab, E., Adams, B., Hassan, A. E., Mockus, A., Sinha, A., & Ubayashi, N. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2012.70 · Cited by 715
Self-citationGlobal Software Engineering: The Future of Socio-technical Coordination
Herbsleb, J. D. (2007) · Future of Software Engineering (FOSE '07) · doi:10.1109/fose.2007.11 · Cited by 645
Self-citationFormal models for expert finding in enterprise corpora
Balog, K., Azzopardi, L., & de Rijke, M. (2006) · Proceedings of the 29th annual international ACM SIGIR conference on Research and development in information retrieval · doi:10.1145/1148170.1148181 · Cited by 553
Kotlarsky, J., & Oshri, I. (2005) · European Journal of Information Systems · doi:10.1057/palgrave.ejis.3000520 · Cited by 520
Familiarity, complexity, and team performance in geographically distributed software development
Espinosa, J. A., Slaughter, S. A., Kraut, R. E., & Herbsleb, J. D. (2007) · Organization Science · doi:10.1287/orsc.1070.0297 · Cited by 420
Self-citationRecommendation Systems for Software Engineering
Robillard, M., Walker, R., & Zimmermann, T. (2010) · IEEE Software · doi:10.1109/ms.2009.161 · Cited by 388
Don't touch my code!: examining the effects of ownership on software quality
Bird, C., Nagappan, N., Murphy, B., Gall, H., & Devanbu, P. (2011) · Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering · doi:10.1145/2025113.2025119 · Cited by 340
Hipikat: a project memory for software development
Cubranic, D., Murphy, G. C., Singer, J., & Booth, K. S. (2005) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2005.71 · Cited by 324
Convergent contemporary software peer review practices
Rigby, P. C., & Bird, C. (2013) · Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering · doi:10.1145/2491411.2491444 · Cited by 311
Reducing the effort of bug report triage: Recommenders for development-oriented decisions
Anvik, J., & Murphy, G. C. (2011) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2000791.2000794 · Cited by 281
Modern code review: a case study at google
Sadowski, C., Söderberg, E., Church, L., Sipko, M., & Bacchelli, A. (2018) · Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice · doi:10.1145/3183519.3183525 · Cited by 280
Sharing Knowledge and Expertise: The CSCW View of Knowledge Management
Ackerman, M. S., Dachtera, J., Pipek, V., & Wulf, V. (2013) · Computer Supported Cooperative Work (CSCW) · doi:10.1007/s10606-013-9192-8 · Cited by 229
Code review quality: how developers see it
Kononenko, O., Baysal, O., & Godfrey, M. W. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884840 · Cited by 183
On the Comprehension of Program Comprehension
Maalej, W., Tiarks, R., Roehm, T., & Koschke, R. (2014) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2622669 · Cited by 180
Hard-to-answer questions about code
LaToza, T. D., & Myers, B. A. (2010) · Evaluation and Usability of Programming Languages and Tools · doi:10.1145/1937117.1937125 · Cited by 141
Today was a good day: The daily life of software developers
Meyer, A. N., Barr, E. T., Bird, C., & Zimmermann, T. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2904957 · Cited by 123
An Information Foraging Theory Perspective on Tools for Debugging, Refactoring, and Reuse Tasks
Fleming, S. D., Scaffidi, C., Piorkowski, D., Burnett, M., Bellamy, R., Lawrance, J., & Kwan, I. (2013) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2430545.2430551 · Cited by 79
Using developer interaction data to compare expertise metrics
Robbes, R., & Rothlisberger, D. (2013) · 2013 10th Working Conference on Mining Software Repositories (MSR) · doi:10.1109/msr.2013.6624041 · Cited by 36
An Industrial Case Study of Program Artifacts Viewed During Maintenance Tasks
Zou, L., & Godfrey, M. W. (2006) · 2006 13th Working Conference on Reverse Engineering · doi:10.1109/wcre.2006.12 · Cited by 20
Metadata
- Authors
- Mockus, A., & Herbsleb, J. D.
- Venue
- Proceedings of the 24th International Conference on Software Engineering. ICSE 2002
- Publisher
- ACM
- Published
- 2003-06-25
- Pages
- 503-512
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W3148527572
- Cited by
- 383
- References
- 0
- FWCI
- 13.47
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.