No abstract available.
The Technical Debt Dataset
Technical Debt analysis is increasing in popularity as nowadays researchers and industry are adopting various tools for static code analysis to evaluate the quality of their code. Despite this, empirical studies on software projects are expensive ...
Which Refactoring Reduces Bug Rate?
We present a methodology to identify refactoring operations that reduce the bug rate in the code. The methodology is based on comparing the bug fixing rate in certain time windows before and after the refactoring. We analyzed 61,331 refactor commits ...
On Usefulness of the Deep-Learning-Based Bug Localization Models to Practitioners
Background: Developers spend a significant amount of time and effort to localize bugs. In the literature, many researchers proposed state-of-the-art bug localization models to help developers localize bugs easily. The practitioners, on the other hand, ...
An Evaluation of Parameter Pruning Approaches for Software Estimation
Model-based estimation often uses impact factors and historical data to predict the effort of new projects. Estimation accuracy of this approach is highly dependent on how well impact factors are selected. This paper comparatively assesses six methods ...
Patterns of Effort Contribution and Demand and User Classification based on Participation Patterns in NPM Ecosystem
Background: Open source requires participation of volunteer and commercial developers (users) in order to deliver functional high-quality components. Developers both contribute effort in the form of patches and demand effort from the component ...
Leveraging Change Intents for Characterizing and Identifying Large-Review-Effort Changes
Code changes to software occur due to various reasons such as bug fixing, new feature addition, and code refactoring. In most existing studies, the intent of the change is rarely leveraged to provide more specific, context aware analysis.
In this paper, ...
Prioritizing automated user interface tests using reinforcement learning
User interface testing validates the correctness of an application through visual cues and interactive events emitted in real world usages. Performing user interface tests is a time-consuming process, and thus, many studies have focused on prioritizing ...
Reviewer Recommendation using Software Artifact Traceability Graphs
Various types of artifacts (requirements, source code, test cases, documents, etc.) are produced throughout the lifecycle of a software. These artifacts are often related with each other via traceability links that are stored in modern application ...
Applying Cross Project Defect Prediction Approaches to Cross-Company Effort Estimation
BACKGROUND: Prediction systems in software engineering often suffer from the shortage of suitable data within a project. A promising solution is transfer learning that utilizes data from outside the project. Many transfer learning approaches have been ...
From Reports to Bug-Fix Commits: A 10 Years Dataset of Bug-Fixing Activity from 55 Apache's Open Source Projects
Bugs appear in almost any software development. Solving all or at least a large part of them requires a great deal of time, effort, and budget. Software projects typically use issue tracking systems as a way to report and monitor bug-fixing tasks. In ...
Does chronology matter in JIT defect prediction?: A Partial Replication Study
BACKGROUND: Just-In-Time (JIT) models, unlike the traditional defect prediction models, detect the fix-inducing changes (or defect inducing changes). These models are designed based on the assumption that past code change properties are similar to ...
Recommendations
Acceptance Rates
| Year | Submitted | Accepted | Rate |
|---|---|---|---|
| PROMISE | 25 | 12 | 48% |
| PROMISE 2016 | 23 | 10 | 43% |
| PROMISE '15 | 16 | 8 | 50% |
| PROMISE '14 | 21 | 9 | 43% |
| PROMISE '12 | 24 | 12 | 50% |
| PROMISE '08 | 16 | 13 | 81% |
| Overall | 125 | 64 | 51% |




