Inferring developer expertise through defect analysis

Duesterwald,; Klinger,; Santhanam,

doi:10.1109/icse.2012.6227095

Cited by 16 publications

(11 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…These have been investigated recently by several authors along a separate research trend on the empirical characterization of debugging. Nguyen et al presented an analysis of 1500 defects from bug reports in 5 years for an IBM middleware, showing that the time to repair is influenced by developer expertise and by the topic . Zhang et al studied 3 open source software and found the following factors influencing the time lag between the defect assignment to a developer and the actual starting of the repair action: the assigned severity, the bug description, and the number of methods and code changes.…”

Section: Related Workmentioning

confidence: 99%

“…Significant attention has been devoted to the one of immediate debugging—ie, that corrections take zero time—which hardly holds in real projects. Software reliability growth model extensions have been proposed to this aim ; nonetheless, empirical studies have made it clear that debugging is a complex process , hardly modelled analytically.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Debugging‐workflow‐aware software reliability growth analysis

Cinque

Cotroneo

Pecchia

et al. 2017

Software Testing Verif & Rel

View full text Add to dashboard Cite

Software reliability growth models support the prediction/assessment of product quality, release time, and testing/debugging cost. Several software reliability growth model exten-\ud sions take into account the bug correction process. However, their estimates may be significantly inaccurate when debugging fails to fully fit modelling assumptions. This paper proposes debugging-workflow-aware software reliability growth method (DWA-SRGM), a method for reliability growth analysis leveraging the debugging data usually managed by companies in bug tracking systems. On the basis of a characterization of the debugging workflow within the soft- ware project under consideration (in terms of bug features and treatment phases), DWA-SRGM pinpoints the factors impacting the estimates and to spot bottlenecks, thus supporting process improvement decisions. Two industrial case studies are presented, a customer relationship man- agement system and an enterprise resource planning system, whose defects span a period of about 17 and 13 months, respectively. DWA-SRGM revealed effective to obtain more realistic estimates and to capitalize on the awareness of critical factors for improving debugging

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Debugging‐workflow‐aware software reliability growth analysis

Cinque

Cotroneo

Pecchia

et al. 2017

Software Testing Verif & Rel

View full text Add to dashboard Cite

show abstract

“…Many studies have explored expert identification and prediction from different perspectives. In references [2][3], Nguyen and Ma, et al evaluated the expertise of developers by analyzing the usage frequency of methods and time distribution on issue fixing, respectively. Thereafter, they designed the corresponding metrics to measure the technical capabilities of developers from the aspects of usage and implementation.…”

Section: A Expert Identification and Predictionmentioning

confidence: 99%

“…Nguyen et al [2] and Ma et al [3] proposed approaches to fix the recommendation issues by analyzing the implementation history and expertise of developers. Thongtanunam et al [4] and Yu et al [5] focused on the automatic pull-request reviewer recommendation problem by analyzing the development history and social connections of individuals in the software community.…”

Section: A Introductionmentioning

confidence: 99%

Who Will be Interested in? A Contributor Recommendation Approach for Open Source Projects

Zhang

Wang

Yin

et al. 2017

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-The crowds' continuous participation and contribution are the key factors for the success of open source projects. However, among the massive competitors, it is difficult for a project to attract enough contributors by just passively waiting for enthusiasts to join in. Instead, it should actively seek gifted developers. Most of the current studies mainly focus on recommending experts inside a repository for some specific development tasks. In this paper, we propose a novel approach A. IntroductionOpen source software (OSS) has become increasingly popular in software development. Quite different from the traditional software development, OSS is driven by massive crowds including developers, users, managers and so on. These stakeholders involve in OSS by interests, and most of them have their own full-time job and can only spend spare time on OSS. They can join in or withdraw from it at any time. Nevertheless, OSS has achieved great success at creating highquality software like Linux, MySQL, Spark and so on, and is viewed as "eating the software world" by "the Future of Open Source Survey" [1].The behavior of open source itself does not necessarily result in a project's success, but the continuous participation and active contribution from the crowds do play a crucial role. In GitHub, there are more than 48 million open source projects. However, over 2 million projects are not forked or watched by anyone after releasing, and 15.1% of them were not updated for more than a year and finally failed. Even DOI reference number: 10.18293/SEKE2017-067 for those projects which used to be successful will languish without continuous contribution of developers.Therefore, finding and attracting the right developers to participate is quite crucial for OSS. On the one hand, proper developers can provide necessary technical expertise that a project needs; On the other hand, suitable projects can inspire developers to participate in and to contribute their innovations continuously. However, there is a massive amount of competitive OSS, and developers are often limited by their time and energy to browse and choose from all the related projects. An automatic approach to bridge the gap between developers and projects and match them means much for both developers and projects.Several studies have explored the act of recommending developers to open source projects. Nguyen et al. [2] and Ma et al. [3] proposed approaches to fix the recommendation issues by analyzing the implementation history and expertise of developers. Thongtanunam et al. [4] and Yu et al. [5] focused on the automatic pull-request reviewer recommendation problem by analyzing the development history and social connections of individuals in the software community. Most of these studies mainly focus on specific software tasks and limit the recommended candidates to the core developers of the projects. By contrast, the current study is rooted in the granularity of open source repositories, and our output allows recommendations of external experts throughout the...

show abstract

“…The study in Ref. reports an analysis on 1500 defects revealed in 5 years on an IBM middleware, classifying defects per topic and developer expertise, showing that the time to fix is impacted from these two factors. Zhang et al .…”

Section: Related Workmentioning

confidence: 99%

Defect analysis in mission-critical software systems: a detailed investigation

Carrozza

Pietrantuono

Russo

2014

J. Softw. Evol. and Proc.

View full text Add to dashboard Cite

The practice of defect analysis is recognized as an essential task for software process measurement, yet its\ud effective application in the industrial development of large-scale software systems raises several challenges.\ud We report the results of a study conducted at SELEX ES - a large system integrator leader in the market of\ud software-intensive mission-critical systems. The article describes the defect analysis approach that we tailored to evaluate the software development process with respect to the quality of produced software and\ud its relation with the required effort. Three key phases of the process were addressed, regarding the software\ud implementation, the testing phase and the prerelease defect fixing activity, over a set of six computer software configuration items developed from 2009 to 2012 for the naval and maritime domain product line.\ud The analysis highlighted efficiency bottlenecks in each of the monitored phases, providing company engineers with insights about room for process improvement. The implemented approach, the observed phenomena and the inferred conclusions are of support to practitioners coping with systems, development models and\ud industrial environments similar to the considered one

show abstract

Inferring developer expertise through defect analysis

Cited by 16 publications

References 10 publications

Debugging‐workflow‐aware software reliability growth analysis

Debugging‐workflow‐aware software reliability growth analysis

Who Will be Interested in? A Contributor Recommendation Approach for Open Source Projects

Defect analysis in mission-critical software systems: a detailed investigation

Contact Info

Product

Resources

About