Identifying key developers using artifact traceability graphs

Simple item page
buir.contributor.authorÇetin, H. Alperen
buir.contributor.authorTüzün, Eray
dc.citation.epage60en_US
dc.citation.spage51en_US
dc.contributor.authorÇetin, H. Alperenen_US
dc.contributor.authorTüzün, Erayen_US
dc.contributor.editorMinku, L.
dc.contributor.editorMenzies, T.
dc.contributor.editorNagappan, M.
dc.coverage.spatialVirtual, USA
dc.date.accessioned2021-03-03T10:59:35Z
dc.date.available2021-03-03T10:59:35Z
dc.date.issued2020
dc.departmentDepartment of Computer Engineeringen_US
dc.descriptionDate of Conference: 8-9 November 2020en_US
dc.descriptionConference Name: 16th ACM International Conference on Predictive Models and Data Analytics in Software Engineering, Co-located with ESEC/FSE 2020
dc.description.abstractDevelopers are the most important resource to build and maintain software projects. Due to various reasons, some developers take more responsibility, and this type of developers are more valuable and indispensable for the project. Without them, the success of the project would be at risk. We use the term key developers for these essential and valuable developers, and identifying them is a crucial task for managerial decisions such as risk assessment for potential developer resignations. We study key developers under three categories: jacks, mavens and connectors. A typical jack (of all trades) has a broad knowledge of the project, they are familiar with different parts of the source code, whereas mavens represent the developers who are the sole experts in specific parts of the projects. Connectors are the developers who involve different groups of developers or teams. They are like bridges between teams. To identify key developers in a software project, we propose to use traceable links among software artifacts such as the links between change sets and files. First, we build an artifact traceability graph, then we define various metrics to find key developers. We conduct experiments on three open source projects: Hadoop, Hive and Pig. To validate our approach, we use developer comments in issue tracking systems and demonstrate that the identified key developers by our approach match the top commenters up to 92%.en_US
dc.description.provenanceSubmitted by Zeynep Aykut (zeynepay@bilkent.edu.tr) on 2021-03-03T10:59:35Z No. of bitstreams: 1 Identifying_key_developers_using_artifact_traceability_graphs.pdf: 784061 bytes, checksum: 7264ef899545b393228c2ba61df8fa22 (MD5)en
dc.description.provenanceMade available in DSpace on 2021-03-03T10:59:35Z (GMT). No. of bitstreams: 1 Identifying_key_developers_using_artifact_traceability_graphs.pdf: 784061 bytes, checksum: 7264ef899545b393228c2ba61df8fa22 (MD5) Previous issue date: 2020en
dc.identifier.doi10.1145/3416508.3417116en_US
dc.identifier.isbn9781450381277
dc.identifier.urihttp://hdl.handle.net/11693/75712
dc.language.isoEnglishen_US
dc.publisherAssociation for Computing Machineryen_US
dc.relation.isversionofhttps://dx.doi.org/10.1145/3416508.3417116en_US
dc.source.titleProceedings of the 16th ACM International Conference on Predictive Models and Data Analytics in Software Engineering, Co-located with ESEC/FSE 2020en_US
dc.subjectKey developersen_US
dc.subjectMost valuable developersen_US
dc.subjectDeveloper categoriesen_US
dc.subjectSocial networksen_US
dc.subjectArtifact traceability graphsen_US
dc.subjectJacken_US
dc.subjectMavenen_US
dc.subjectConnectoren_US
dc.titleIdentifying key developers using artifact traceability graphsen_US
dc.typeConference Paperen_US

Files

Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
Identifying_key_developers_using_artifact_traceability_graphs.pdf
Size:
765.68 KB
Format:
Adobe Portable Document Format
Description:
View / Download
Download
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.71 KB
Format:
Item-specific license agreed upon to submission
Description:
Download

Collections

Scholarly Publications - Computer Engineering