Expertise Browser: a quantitative approach to identifying expertise

By Audris Mockus, James D. Herbsleb. Proceedings of the 24th International Conference on Software Engineering. ICSE 2002, 2002

505 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems

View Paper: https://www.semanticscholar.org/paper/b3e26859989a7e60193ab7a07b5a587c131b4326

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Science Applications

In Information Systems

Citations in the corpus

An Empirical Study of Speed and Communication in Globally Distributed Software Development (2003, methodology): “We developed and deployed a tool that uses this strategy called Experience Browser [30], which provides a visualization of the CM system and is designed to make it easy to find and contact an appropriate expert.”
Familiarity, Complexity, and Team Performance in Geographically Distributed Software Development (2007, methodology): “Thus, consistent with similar measures of expertise used in prior software studies (Mockus and Herbsleb 2002), we measured task familiarity by counting the number of deltas developed for the subsystem by each team member prior to starting work on the MR project, and then averaged this count for the…”
Palantir: raising awareness among configuration management workspaces (2003, background): “We are not alone in making the above observations and concluding that the use of awareness can make a difference in how configuration management systems are used in coordinating the activities of developers [21,27].”
Convergent contemporary software peer review practices (2013, methodology): “To provide a preliminary measurement of the knowledge spreading effect of peer review, we extend the expertise measure developed by Mockus and Herbsleb [16].”
A large-scale empirical study of just-in-time quality assurance (2013, methodology): “Similarly to previous work [14], [32], [40], [41], we use the number of changes as the developer’s project experience.”
Formal models for expert finding in enterprise corpora (2006, background): “More recently there has been a move to automatically extract such representations from heterogeneous document collections such as those found within a corporate intranet [2].”
Hipikat: a project memory for software development (2005, methodology): “Expertise Browser by Mockus and Herbsleb [21] and Expertise Recommender by McDonald and Ackerman [22] use source change data to identify developers and groups with experience in given elements of a software project.”
Global Software Engineering: The Future of Socio-technical Coordination (2007, methodology): “McDonald and Ackerman [48] and Mockus and Herbsleb [49] have designed and deployed tools for locating expertise in software development projects, using data from the version control system about which developers have contributed to what parts of the code.”
Who should fix this bug? (2006, methodology): “Another means of acquiring developer proﬁles may be an approach such as used by the Expertise Browser [9] which uses experience atoms derived from source code.”
Don't touch my code!: examining the effects of ownership on software quality (2011, background): “[22] and Expertise Recommender from McDonald and Ackerman [18] both use measures of the amount of work that a developer has performed on a software component to recommend component experts.”