2020
DOI: 10.48550/arxiv.2005.13299
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Machine Learning for Software Engineering: A Systematic Mapping

Saad Shafiq,
Atif Mashkoor,
Christoph Mayr-Dorn
et al.

Abstract: The software development industry is rapidly adopting machine learning for transitioning modern day software systems towards highly intelligent and self-learning systems. However, the full potential of machine learning for improving the software engineering life cycle itself is yet to be discovered, i.e., up to what extent machine learning can help reducing the effort/complexity of software engineering and improving the quality of resulting software systems. To date, no comprehensive study exists that explores… Show more

Help me understand this report
View published versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2021
2021
2023
2023

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 54 publications
0
4
0
Order By: Relevance
“…They conclude that software quality is the most frequent SWEBOK knowledge area target for both clusters (51%) and that ML is mainly used to make predictions in SE. A similar study by Shafiq et al 46 shows that based on 227 articles about ML for software engineering from 1991 to 2019, 21 were focusing on requirements, 39 on architecture and design, 21 on implementation, 119 on quality assurance and analytics and 9 on maintenance. Our study is richer and broader in the sense that we do not only focus on assistants empowered with ML techniques, and more specific in the sense that we are only interested in working assistants and ignore theoretical and unimplemented approaches.…”
Section: Previous Secondary Studies On Software Assistants In Sementioning
confidence: 85%
“…They conclude that software quality is the most frequent SWEBOK knowledge area target for both clusters (51%) and that ML is mainly used to make predictions in SE. A similar study by Shafiq et al 46 shows that based on 227 articles about ML for software engineering from 1991 to 2019, 21 were focusing on requirements, 39 on architecture and design, 21 on implementation, 119 on quality assurance and analytics and 9 on maintenance. Our study is richer and broader in the sense that we do not only focus on assistants empowered with ML techniques, and more specific in the sense that we are only interested in working assistants and ignore theoretical and unimplemented approaches.…”
Section: Previous Secondary Studies On Software Assistants In Sementioning
confidence: 85%
“…QA1 QA2 QA3 QA4 Total P1 Abdellatif et al [16] 1 0 0 1 2 P2 Khan et al [17] 1 1 1 0.5 3.5 P3 Shaikh et al [18] 0 1.5 1 0 2.5 P4 Zarembo et al [19] 0.5 0.5 0.5 0.5 2 P5 Cao et al [20] 1 0.5 0 0 1.5 P6 Yang et al [21] 1 0.5 1 0.5 3 P7 Cote et al [22] 1 1 1 1 4 P8 Xu et al [23] 0.5 1 1 0.5 3 P9 Dey et al [24] 1 1 0.5 0 2.5 P10 Zanca et al [25] 1 0 1 1 3 P11 Al-Dasuqi et al [26] 0.5 1 0.5 0.5 2.5 P12 O'Hare et al [27] 1 1 1 0.5 3.5 P13 Druffel et al [28] 0 0 1 1 2 P14 Perkusich et al [29] 0.5 1 1 1 3.5 P15 Vinsard et al [30] 0.5 0 0.5 1 2 P16 Beegle et al [31] 1 0 1 0.5 2.5 P17 Salahirad et al [32] 1 1 0.5 0.5 3 P18 Dlamini et al [33] 0.5 0.5 0.5 0.5 2 P19 Cross et al [34] 0.5 1 1 1 3.5 P20 Malamateniou et al [35] 0 0 1 1 2 P21 Lenarduzzi et al [7] 1 0.5 0.5 0.5 2.5 P22 Sikorska et al [36] 0 1 0 1 2 P23 Field et al [37] 1 1 0 1 3 P24 Gao et al [38] 0.5 0 0 0 0.5 P25 Khanagar et al [39] 1 0 0 1 2 P26 Shafiq et al [40] 1 0.5 1 1 3.5 P27 Waade et al [41] 1 1 1 0.5 3.5 P28 Felderer et al [42] 1 0 0 0 1 P29 Ji et al [43] 0 0 1 1 2 P30 Harman et al [44] 1 0.5 1 1 3.5 P31 Shehab et al [45] 0 0.5 0.5 0.5 1.5 P32 Rana et al [46] 1 1 1 0 3 P33 Huang et al [47] 1 0.5 0.5 0.5 2.5 P34 Shakeel et al [48] 1 0.5 1 1 3.5 P35 Zhou et al [49] 0.5 0.5 0 0 1 P36 Sayago-Heredia et al…”
Section: Appendix Scores -Quality Assessmentmentioning
confidence: 99%
“…Zhang et al [3] provides a comprehensive survey on ML testing considering 138 related papers on four aspects of MLSA testing such as what properties to test, what ML components to test, testing workflows and test scenario of different type of ML application. Shafiq et al [13] conducts a bibliometric study and provides an MLSA taxonomy of the adaptation of ML techniques across different SDLC phase. It focuses on the research attention at different SDLC of MLSA.…”
Section: Background and Related Workmentioning
confidence: 99%