ACM Home Page
Please provide us with feedback. Feedback
Expertise browser: a quantitative approach to identifying expertise
Full text PdfPdf (1.27 MB)
Source International Conference on Software Engineering archive
Proceedings of the 24th International Conference on Software Engineering table of contents
Orlando, Florida
SESSION: Technical papers: software presentation table of contents
Pages: 503 - 512  
Year of Publication: 2002
ISBN:1-58113-472-X
Authors
Audris Mockus  Avaya Labs Research, Basking Ridge, NJ
James D. Herbsleb  Bell Laboratories, Lisle, IL
Sponsors
IEEE-CS\DATC : IEEE Computer Society
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 19,   Downloads (12 Months): 106,   Citation Count: 29
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/581339.581401
What is a DOI?

ABSTRACT

Finding relevant expertise is a critical need in collaborative software engineering, particularly in geographically distributed developments. We introduce a tool 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, easily to 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 module 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.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
Allen, T. J., Managing the Flow of Technology. 1977, Cambridge, MA: MIT Press.
 
3
Carmel, E., Global Software Teams. 1999, Upper Saddle River, NJ: Prentice-Hall.
 
4
Cedeqvist, P. et al, CVS Manual. May be fond on: http://www.cvshome.org/CVS/.
 
5
6
 
7
Graves, T. and Mockus, A. Identifying productivity drivers by modeling work units using partial data. Technometrics, 43(2):168-179, May 2001.
8
 
9
 
10
 
11
 
12
Herbsleb, J. D., et al. Object-oriented analysis and design in software project teams. Human-Computer Interaction 10,, 1995, 249-292.
13
14
 
15
Kohonen, T. The self organizing map. IEEE Transactions on Computers, 78(9):1464-1480, 1990.
 
16
17
 
18
Midha, A.K. Software configuration management for the 21st century. Bell Labs Technical Journal, 2(1), Winter 1997.
 
19
Mockus, A. and Weiss, D. M. Predicting risk of software changes. Bell Labs Technical Journal, 5(2):169-180, April-June 2000.
 
20
 
21
Wills, G.W. Linked data views. Statistical and Computing Graphics Newsletter, 10(1):20-24, Summer 1999.

CITED BY  29
 
 
 
 
 
 
 
 
 
 

Collaborative Colleagues:
Audris Mockus: colleagues
James D. Herbsleb: colleagues

Peer to Peer - Readers of this Article have also read: