Filters








345 Hits in 3.3 sec

Effective Bug Triage Based on Historical Bug-Fix Information

Hao Hu, Hongyu Zhang, Jifeng Xuan, Weigang Sun
2014 2014 IEEE 25th International Symposium on Software Reliability Engineering  
We evaluate BugFixer on three large-scale open source projects and two smaller industrial projects.  ...  We find that the effectiveness of a bug triage technique largely depends on the size of a project team (measured in terms of the number of developers).  ...  This work is supported by the National Natural Science Foundation of China under a grant 61272089 and the INRIA Postdoctoral Research Fellowship.  ... 
doi:10.1109/issre.2014.17 dblp:conf/issre/HuZXS14 fatcat:z4fkt5vu4fdrvl2xpawk37uvuy

Why software repositories are not used for defect-insertion circumstance analysis more often: A case study

Lutz Prechelt, Alexander Pepper
2014 Information and Software Technology  
In DICA, data from existing repositories (version archive, bug tracker) is evaluated largely automatically in order to determine conditions (such as the people, roles, components, or time-periods involved  ...  make use of these data.  ...  We thank Stephan Salinger for helpful comments on a draft of the article.  ... 
doi:10.1016/j.infsof.2014.05.001 fatcat:pq7kfyojsfgj5b5dw5bvxiqi2i

Bflinks: Reliable Bugfix Links via Bidirectional References and Tuned Heuristics

Lutz Prechelt, Alexander Pepper
2014 International Scholarly Research Notices  
For a commercial repository, a product expert manually verifies over 2500 links to validate the results with unprecedented accuracy. Results.  ...  The first step in such analyses is identifying defect-correcting changes in the version archive (bugfix commits) and enriching them with additional metadata by establishing bugfix links to corresponding  ...  Acknowledgments We thank Thomas Witt and the development team at Infopark for helping with access to and understanding of the repository data.  ... 
doi:10.1155/2014/701357 pmid:27433506 pmcid:PMC4897393 fatcat:6rrow5itcjh5tndf53vvu4kaxq

On the feasibility of automated prediction of bug and non-bug issues

Steffen Herbold, Alexander Trautsch, Fabian Trautsch
2020 Empirical Software Engineering  
We demonstrate the usefulness of issue type prediction through the example of labelling bugfixing commits.  ...  manually specified knowledge about issues.  ...  Models for this purpose should be trained with a large corpus of data that does not require manual validation.  ... 
doi:10.1007/s10664-020-09885-w fatcat:34fb4yabqrgqdb33js3yu6uzji

On the Feasibility of Automated Issue Type Prediction [article]

Steffen Herbold, Alexander Trautsch, Fabian Trautsch
2020 arXiv   pre-print
We demonstrate the usefulness of issue type prediction through the example of labelling bugfixing commits.  ...  manually specified knowledge about issues.  ...  Models for this purpose should be trained with a large corpus of data that does not require manual validation.  ... 
arXiv:2003.05357v2 fatcat:swsxlft755fwxdspnd2d2uf7v4

The SmartSHARK Ecosystem for Software Repository Mining [article]

Alexander Trautsch, Fabian Trautsch, Steffen Herbold, Benjamin Ledel, Jens Grabowski
2020 arXiv   pre-print
The collection and analysis of detailed data can be challenging, especially if data shall be shared to enable replicable research and open science practices.  ...  data and enables manual validations.  ...  Mynbou uses inducing changes determined by inducingSHARK for bug fix labels based on manually validated data with the VisualSHARK.  ... 
arXiv:2001.01606v1 fatcat:r2go6pkzzvfxpbdqutd7k6fffu

Analyzing the Context of Bug-Fixing Changes in the OpenStack Cloud Computing Platform

Domenico Cotroneo, Luigi De Simone, Antonio Ken Iannillo, Roberto Natella, Stefano Rosiello, Nematollah Bidokhti
2019 2019 IEEE 30th International Symposium on Software Reliability Engineering (ISSRE)  
Therefore, in this paper we perform a thorough empirical analysis of bug-fixing changes in three OpenStack projects, focusing on both the what and the where of the changes.  ...  Previous studies in this field focus on what has been changed due to bug-fixes, such as in terms of code edit actions.  ...  ACKNOWLEDGMENTS This work has been partially supported by the PRIN project "GAUSS" funded by MIUR (n. 2015KWREMX 002) and by UniNA and Compagnia di San Paolo in the frame of Programme STAR.  ... 
doi:10.1109/issre.2019.00041 dblp:conf/issre/CotroneoSINRB19 fatcat:odgiukclq5dzbfk7lgzbiw4h7e

CIASYS--Change Impact Analysis at System Level

Gabriella Tóth, Csaba Nagy, Judit Jász, Árpád Beszédes, Lajos Jeno Fülöp
2010 2010 14th European Conference on Software Maintenance and Reengineering  
The research field of change impact analysis plays an important role in software engineering theory and practice nowadays.  ...  For these reasons, they are not applicable to large industrial systems where both scalability and precision are very important.  ...  Experience shows that the current static techniques do not scale well for the impact analysis of large industrial systems.  ... 
doi:10.1109/csmr.2010.35 dblp:conf/csmr/TothNJBF10 fatcat:nrxejruerzg4lbmxi23cgigfda

Better Data Labelling with EMBLEM (and how that Impacts Defect Prediction) [article]

Huy Tu and Zhe Yu and Tim Menzies
2020 arXiv   pre-print
Also, in studies with 9 open source software projects, labelling via EMBLEM's incremental application of human+AI is at least an order of magnitude cheaper than existing methods (≈ eight times).  ...  Standard automatic methods for recognizing problematic development commits can be greatly improved via the incremental application of human+artificial expertise.  ...  Hence, a large scale Linkster-style analysis would be too costly in real-world scenarios.  ... 
arXiv:1905.01719v3 fatcat:uf5gnpl7rfhrjk3heqdjoetfs4

A study on the changes of dynamic feature code when fixing bugs: towards the benefits and costs of Python dynamic features

Zhifei Chen, Wanwangying Ma, Wei Lin, Lin Chen, Yanhui Li, Baowen Xu
2017 Science China Information Sciences  
changes between bug-fix and non-bugfix activities.  ...  The study results reveal that (1) the changes of dynamic feature code are significantly related to bug-fix activities rather than non-bugfix activities; (2) compared with non-dynamic feature code, dynamic  ...  Threats to internal validity. We manually inspected, explained, and classified change occurrences at 226 bug-fix commits.  ... 
doi:10.1007/s11432-017-9153-3 fatcat:fppx4mxg7fdofnzhguebq3dcea

On the usefulness of ownership metrics in open-source software projects

Matthieu Foucault, Cédric Teyton, David Lo, Xavier Blanc, Jean-Rémy Falleri
2015 Information and Software Technology  
Objective: The relationship between these metrics and software quality was initially validated on proprietary software projects.  ...  metrics such as the number of lines of code, the number of modifications performed over the last release, or the number of developers of a module.  ...  Acknowledgments The authors would like to thank Alan Charpentier for his help in the realization of several manual tasks performed in this study, as well as for his helpful comments regarding the methodology  ... 
doi:10.1016/j.infsof.2015.01.013 fatcat:tkyk3dqg4zdjldarnf5frt5tnm

Ammonia: an approach for deriving project-specific bug patterns

Yoshiki Higo, Shinpei Hayashi, Hideaki Hata, Meiyappan Nagappan
2020 Empirical Software Engineering  
Next, through manual analysis, we determined that six of those change patterns were actual bugs and submitted pull requests based on those bug patterns.  ...  Accordingly, in this paper, we propose an approach called Ammonia, which is based on statically analyzing changes across the development history of a project, as a means to identify project-specific bug  ...  and it would be unrealistic to manually analyze such a large number of change patterns.  ... 
doi:10.1007/s10664-020-09807-w fatcat:gaskz3uquvg7fcmtrb7mowescm

The Impact of Coverage on Bug Density in a Large Industrial Software Project

Thomas Bach, Artur Andrzejak, Ralf Pannemans, David Lo
2017 2017 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)  
In this work we study whether covered code contains a smaller number of future bugs than uncovered code (assuming appropriate scaling).  ...  To this end we analyse 16 000 internal bug reports and bug-fixes of SAP HANA, a large industrial software project.  ...  They find a weak but significant correlation between statement coverage and number of bugfixes.  ... 
doi:10.1109/esem.2017.44 dblp:conf/esem/BachAPL17 fatcat:nbxq77ttyzhn5lyndcqtgnqwtu

Revealing Missing Bug-Fixes in Code Clones in Large-Scale Code Bases

Martin Poehlmann, Elmar Juergens
2013 Electronic Communications of the EASST  
In practice, however, fixes are often incomplete, which causes the bug to remain in one or more of the clones.  ...  The approach then performs incremental clone detection to reveal those clones that became inconsistent as a result of such a fix.  ...  This work was partially funded by the German Federal Ministry of Education and Research (BMBF), grant "EvoCon, 01IS12034A". The responsibility for this article lies with the authors.  ... 
doi:10.14279/tuj.eceasst.60.853 dblp:journals/eceasst/PoehlmannJ13 fatcat:6r63cnovjfaddp4r3nfyttr6nu

Evaluating SZZ Implementations Through a Developer-informed Oracle [article]

Luca Pascarella, Simone Scalabrino, Rosalia Tufano, Gabriele Bavota, Michele Lanza, Rocco Oliveto
2021 arXiv   pre-print
This was followed by a manual filtering step aimed at ensuring the quality and accuracy of the oracle.  ...  In both cases, these manual evaluations are performed by researchers with limited knowledge of the studied subject systems.  ...  However, by manually analyzing a large dataset of bugfixing commits, it should be possible to identify fixing patterns with associated buggy lines.  ... 
arXiv:2102.03300v1 fatcat:5ov6ojulljg4nmtc6doprpgeje
« Previous Showing results 1 — 15 out of 345 results