Filters








526 Hits in 6.3 sec

Comparing fine-grained source code changes and code churn for bug prediction

Emanuel Giger, Martin Pinzger, Harald C. Gall
2011 Proceeding of the 8th working conference on Mining software repositories - MSR '11  
In this paper, we explore the advantage of using fine-grained source code changes (SCC) for bug prediction. SCC captures the exact code changes and their semantics down to statement level.  ...  Code churn in terms of lines modified (LM) and past changes turned out to be significant indicators of bugs.  ...  In our previous work, we pointed out this discrepancy between changes based on a text-line level and fine-grained source code changes, and showed that fine-grained source code changes can be used to qualify  ... 
doi:10.1145/1985441.1985456 dblp:conf/msr/GigerPG11 fatcat:2sx6rbwlofd6zddry6o6w575om

Bug prediction based on fine-grained module histories

Hideaki Hata, Osamu Mizuno, Tohru Kikuno
2012 2012 34th International Conference on Software Engineering (ICSE)  
Prediction on a fine-grained level, which represents the method level, is required because there may be interesting results compared to coarse-grained (package and file levels) prediction.  ...  The results indicate that fine-grained (method-level) prediction outperforms coarse-grained (package and file levels) prediction when taking the efforts necessary to find bugs into account.  ...  Studies of fine-grained prediction are necessary because desirable results may be obtained when compared to coarse-grained prediction.  ... 
doi:10.1109/icse.2012.6227193 dblp:conf/icse/HataMK12 fatcat:wfsiqbrt45azfl5sb3poxp5o6m

An Empirical Study on Factors Impacting Bug Fixing Time

Feng Zhang, Foutse Khomh, Ying Zou, Ahmed E. Hassan
2012 2012 19th Working Conference on Reverse Engineering  
We examine factors affecting bug fixing time along three dimensions: bug reports, source code involved in the fix, and code changes that are required to fix the bug.  ...  A typical process of bug fixing consists of the following steps: 1) a user files a bug report; 2) the bug is assigned to a developer; 3) the developer fixes the bug; 4) changed code is reviewed and verified  ...  ACKNOWLEDGMENT The authors would like to thank Daniele Romano at Delft University of Technology and Michael Wrsch at University of Zurich for their kind help on solving ChangeDistiller problems.  ... 
doi:10.1109/wcre.2012.32 dblp:conf/wcre/ZhangKZH12 fatcat:7ofqxwsfibcfbbbeqzkrh566qy

Method-level bug prediction

Emanuel Giger, Marco D'Ambros, Martin Pinzger, Harald C. Gall
2012 Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement - ESEM '12  
The models are based on change metrics and source code metrics that are typically used in bug prediction.  ...  The models are based on change metrics and source code metrics that are typically used in bug prediction.  ...  In a prior study using the change history of Eclipse, we compared lines based code churn and fine-grained source code changes for bug prediction [16] .  ... 
doi:10.1145/2372251.2372285 dblp:conf/esem/GigerDPG12 fatcat:nzrpuacxkzaodfsx5mrpukcequ

Evaluating defect prediction approaches: a benchmark and an extensive comparison

Marco D'Ambros, Michele Lanza, Romain Robbes
2011 Empirical Software Engineering  
We present a benchmark for defect prediction, in the form of a publicly available dataset consisting of several software systems, and provide an extensive comparison of well-known bug prediction approaches  ...  Researchers have devised and implemented a plethora of defect/bug prediction approaches varying in terms of accuracy, complexity and the input data they require.  ...  We acknowledge the financial support of the Swiss National Science foundation for the project "SOSYA" (SNF Project No. 132175).  ... 
doi:10.1007/s10664-011-9173-9 fatcat:6qezbnnfkbawdajfscdzjwvrhi

An extensive comparison of bug prediction approaches

Marco D'Ambros, Michele Lanza, Romain Robbes
2010 2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)  
We present a benchmark for defect prediction, in the form of a publicly available data set consisting of several software systems, and provide an extensive comparison of the explanative and predictive  ...  Researchers have devised and implemented a plethora of bug prediction approaches varying in terms of accuracy, complexity and the input data they require.  ...  We gratefully acknowledge the financial support of the Swiss National Science foundation for the project "DiCoSA" (SNF Project No. 118063) and the European Smalltalk User Group (http://www.esug.org).  ... 
doi:10.1109/msr.2010.5463279 dblp:conf/msr/DAmbrosLR10 fatcat:6lb5hvzq6fd5vafp5sxqfhvnvm

The Need for a Fine-grained approach in Just-in-Time Defect Prediction [article]

Giuseppe Ng, Charibeth Cheng
2021 arXiv   pre-print
predicts whether a code change is defective.  ...  As code change can impact several files, we investigate an open source project to identify potential gaps with features in JIT perspective.  ...  Comparing Coarse-grained and Fine-grained JIT A commit or code change can either be clean, completely bug inducing, or partially bug inducing.  ... 
arXiv:2110.00579v1 fatcat:tgeetdxx3bd53is3tbz3qitwhy

Analyzing Structural Software Changes: A Case Study

Crt Gerlec, Marjan Hericko
2012 Balkan Conference in Informatics  
The research showed that the number of structural source code changes increased near the release dates.  ...  In the study, we focused on analyzing structural software changes between software's versions. We used the WatiN project and observed its structural changes during the.  ...  The idea resulted in defining a code delta and a code churn. E. Ginger et al. [8] compared fine-grained source code changes and code churn in order to predict bugs in software system.  ... 
dblp:conf/bci/GerlecH12 fatcat:k5m6v3iqw5cb3j3p7tr47ebpuu

What can changes tell about software processes?

Barbara Russo, Maximilian Steff
2014 Proceedings of the 5th International Workshop on Emerging Trends in Software Metrics - WETSoM 2014  
Code changes propagate. Type, frequency, size of changes typically explain and even predict impact of changes in software products. What can changes tell about software processes?  ...  For this, we introduced a new measure of architectural change based on hashing and a linear-time kernel for bit-labels graphs.  ...  They identified a number of fine-grained changes and how the impact of these changes could be evaluated before implementation.  ... 
doi:10.1145/2593868.2593869 dblp:conf/icse/RussoS14 fatcat:vqqtg3lfonbmhgs62dn3feo3ti

An Empirical Study of Fault Prediction with Code Clone Metrics

Yasutaka Kamei, Hiroki Sato, Akito Monden, Shinji Kawaguchi, Hidetake Uwano, Masataka Nagura, Ken-Ichi Matsumoto, Naoyasu Ubayashi
2011 2011 Joint Conference of the 21st International Workshop on Software Measurement and the 6th International Conference on Software Process and Product Measurement  
We empirically evaluated the performance of fault prediction models with clone metrics using 3 datasets from the Eclipse project and compared it to fault prediction without clone metrics.  ...  The result suggested that clone metrics were effective in fault prediction for large modules but not for small modules.  ...  Nagappan and Ball [23] used relative code churn metrics, which measure the amount of code change, to predict fault density.  ... 
doi:10.1109/iwsm-mensura.2011.12 dblp:conf/iwsm/KameiSMKUNMU11 fatcat:pu4qpydvmzdzflr4z3l2vklkrm

The Delta Maintainability Model: Measuring Maintainability of Fine-Grained Code Changes

Marco Di Biase, Ayushi Rastogi, Magiel Bruntink, Arie Van Deursen
2019 Zenodo  
The Delta Maintainability Model: Measuring Maintainability of Fine-Grained Code Changes - 2nd International Conference on Technical Debt (TechDebt 2019) - Montréal, Canada - May 26–27, 2019 Technical Report  ...  for the paper and dataset available at: https://zenodo.org/record/2542535  ...  This project received funding from European Union's Horizon 2020 research and innovation programme under the Marie Sklodowska-Curie grant agreement No 642954.  ... 
doi:10.5281/zenodo.2606632 fatcat:xlazrjqozjclxecyuttexjdh6e

The Delta Maintainability Model: Measuring Maintainability of Fine-Grained Code Changes

Marco di Biase, Ayushi Rastogi, Magiel Bruntink, Arie van Deursen
2019 2019 IEEE/ACM International Conference on Technical Debt (TechDebt)  
This paper proposes a new maintainability model -the Delta Maintainability Model (DMM) -to measure fine-grained code changes, such as commits, by adapting and extending the SIG Maintainability Model.  ...  The goal of the DMM is twofold: first, producing meaningful and actionable scores; second, compare and rank the maintainability of fine-grained modifications.  ...  RQ2: To what extent can the DMM Scores be used to rank and compare the maintainability of fine-grained code changes? Table VII contains the means and standard deviations for the DMM scores.  ... 
doi:10.1109/techdebt.2019.00030 dblp:conf/icse/BiaseRBD19 fatcat:fxdgjekztrcp3bp6mp2y4nofue

On the Adoption and Effects of Source Code Reuse on Defect Proneness and Maintenance Effort [article]

Giammaria Giordano, Gerardo Festa, Gemma Catolino, Fabio Palomba, Filomena Ferrucci, Carmine Gravino
2022 arXiv   pre-print
Previous work has traditionally employed source code reuse metrics for prediction purposes, e.g., in the context of defect prediction. Objective.  ...  ., by suggesting whether and how to use them for prediction purposes. Method.  ...  In the second place, we plan to conduct a fine-grained analysis where the evolution and impact of reusability will be investigated at commit-level.  ... 
arXiv:2208.07471v1 fatcat:sxpumf3ekbfspnvrd37s75ccfm

Studying high impact fix-inducing changes

Ayse Tosun Misirli, Emad Shihab, Yasukata Kamei
2015 Empirical Software Engineering  
Our measure of impact for a fix-inducing change uses the amount of churn, the number of files and the number of subsystems modified by developers during an associated fix of the fix-inducing change.  ...  We find that the lines of code added, the number of developers who worked on a change, and the number of prior modifications on the files modified during a change are the best indicators of HIFCs.  ...  Section 3 discusses related work on bug prediction at source code and change levels, change impact analysis techniques and emphasizes the novelty in this study.  ... 
doi:10.1007/s10664-015-9370-z fatcat:xxt356qyuve4hb6s4o77htuwmu

A hosting service of multi-language historage repositories

Kyohei Uemura, Yusuke Saito, Shin Fujiwara, Daiki Tanaka, Kenji Fujiwara, Hajimu Iida, Kenichi Matsumoto
2016 2016 IEEE/ACIS 15th International Conference on Computer and Information Science (ICIS)  
With this dataset, we will promote in-depth and fine-grained software evolution research with diversity of programming languages.  ...  In the research of Mining Software Repositories, source code repositories are one of the core sources since it contains the product and the process of software development.  ...  For example, by mining history of source code changes, we can predict the location of the bugs [12] , [18] , [31] , analyze source code evolution [4] , [27] , automatically generate patches of the  ... 
doi:10.1109/icis.2016.7550864 dblp:conf/ACISicis/UemuraSFTFIM16 fatcat:vnwfzfhd4jazhlxurhn3eretli
« Previous Showing results 1 — 15 out of 526 results