Learning Actionable Analytics from Multiple Software Projects
Not on the map. Why?
Abstract (arXiv)
The current generation of software analytics tools are mostly prediction algorithms (e.g. support vector machines, naive bayes, logistic regression, etc). While prediction is useful, after prediction comes planning about what actions to take in order to improve quality. This research seeks methods that generate demonstrably useful guidance on "what to do" within the context of a specific software project. Specifically, we propose XTREE (for within-project planning) and BELLTREE (for cross-project planning) to generating plans that can improve software quality. Each such plan has the property that, if followed, it reduces the expected number of future defect reports. To find this expected number, planning was first applied to data from release x. Next, we looked for changes in release x+1 that conformed to our plans. This procedure was applied using a range of planners from the literature, as well as XTREE. In 10 open-source JAVA systems, several hundreds of defects were reduced in sections of the code that conformed to XTREE's plans. Further, when compared to other planners, XTREE's plans were found to be easier to implement (since they were shorter) and more effective at reducing the expected number of defects.
Key facts. Cited by 3 papers in the map (data through 7 Oct 2026). First posted on arXiv 17 Aug 2017.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2021: 2; 2022: 0; 2023: 0; 2024: 1.
3 papers.
- 2021Deep Learning for Android Malware Defenses: a Systematic Literature Reviewcited by 18
- 2021Fairer Software Made Easier (using "Keys")cited by 0
- 2024Mining Action Rules for Defect Reduction Planningcited by 0
- 2024Mining Action Rules for Defect Reduction Planning22 May 2024
- 2021Fairer Software Made Easier (using "Keys")11 Jul 2021
- 2021Deep Learning for Android Malware Defenses: a Systematic Literature Review9 Mar 2021