Benjamin Ledel's research while affiliated with Institute for Software & Systems Engineering and other places
What is this page?
This page lists the scientific contributions of an author, who either does not have a ResearchGate profile, or has not yet added these contributions to their profile.
It was automatically created by ResearchGate to create a record of this author's body of work. We create such pages to advance our goal of creating and maintaining the most comprehensive scientific repository possible. In doing so, we process publicly available (personal) data relating to the author as a member of the scientific community.
If you're a ResearchGate member, you can follow this page to keep up with this author's work.
If you are this author, and you don't want us to display this page anymore, please let us know.
It was automatically created by ResearchGate to create a record of this author's body of work. We create such pages to advance our goal of creating and maintaining the most comprehensive scientific repository possible. In doing so, we process publicly available (personal) data relating to the author as a member of the scientific community.
If you're a ResearchGate member, you can follow this page to keep up with this author's work.
If you are this author, and you don't want us to display this page anymore, please let us know.
Publications (11)
Context: The identification of bugs within the reported issues in an issue tracker is crucial for the triage of issues. Machine learning models have shown promising results regarding the performance of automated issue type prediction. However, we have only limited knowledge beyond our assumptions how such models identify bugs. LIME and SHAP are pop...
Context
Tangled commits are changes to software that address multiple concerns at once. For researchers interested in bugs, tangled commits mean that they actually study not only bugs, but also other concerns irrelevant for the study of bugs.
Objective
We want to improve our understanding of the prevalence of tangling and the types of changes that...
Context
The SZZ algorithm is the de facto standard for labeling bug fixing commits and finding inducing changes for defect prediction data. Recent research uncovered potential problems in different parts of the SZZ algorithm. Most defect prediction data sets provide only static code metrics as features, while research indicates that other features...
Bug localization is a tedious activity in the bug fixing process in which a software developer tries to locate bugs in the source code described in a bug report. Since this process is time-consuming and sometimes requires additional knowledge about the software project, current literature proposes several information retrieval techniques which can...
Context: Tangled commits are changes to software that address multiple concerns at once. For researchers interested in bugs, tangled commits mean that they actually study not only bugs, but also other concerns irrelevant for the study of bugs. Objective: We want to improve our understanding of the prevalence of tangling and the types of changes tha...
Software repository mining is the foundation for many empirical software engineering studies. The collection and analysis of detailed data can be challenging, especially if data shall be shared to enable replicable research and open science practices. SmartSHARK is an ecosystem that supports replicable and reproducible research based on software re...
Citations
... For instance, should the caller of a vulnerable code snippet also be labelled as such? Herbold et al. [60] encountered similar problems in their investigation of tangled commits. Alternatively, the label source may not contain enough information in the bug report to properly trace it. ...
![[object Object]](https://i1.rgstatic.net/ii/profile.image/324959136616455-1454487703620_Q64/Steffen-Herbold.jpg)
![[object Object]](https://i1.rgstatic.net/ii/profile.image/1185185978683393-1659581765297_Q64/Alireza-Aghamohammadi.jpg)
![[object Object]](https://i1.rgstatic.net/ii/profile.image/746775413551104-1555056541095_Q64/Johannes-Erbel.jpg)
... We use defect prediction data by Herbold et al. (2022) that contains data for 398 releases of 38 Java projects Table 1. Each instance in a release represents a Java production file. ...
![[object Object]](https://i1.rgstatic.net/ii/profile.image/756610989318145-1557401525373_Q64/Fabian-Trautsch.jpg)
... We identify the following directions as future works to extend this study; i) integrate PreMOSA in a continuous integration environment, ii) adapt an appropriate test suite minimisation technique to address the generation of large test suites, iii) define and simulate acceptable defect predictors with respect to unbiased performance metrics like MCC, and iv) validate PreMOSA against other bug datasets [62,63,64]. ...
... Inaccurate ground truth may introduce * Yan Lei is the corresponding author. noise and bias into the assessment activities, and thus may further negatively impact the reliability of assessment results [31], [32]. Therefore, for each bug of datasets used in APR, the associated human-written patch is expected to exclude the irrelevant code changes to the bug that is exposed by the triggering tests. ...
... The inclusion of these counterparts results in computational effort as we need every metric for every file in every commit. However, we are able to provide this data via the SmartSHARK ecosystem (Trautsch et al. 2017(Trautsch et al. , 2020b. This additional effort allows us to infer if categories of changes are different when regarding all changes of a software project. ...
