Review Efforts Reduction by Partitioning of Static Analysis Warnings

被引:0
|
作者
Muske, Tukaram B. [1 ]
Baid, Ankit [1 ]
Sanas, Tushar [1 ]
机构
[1] TRDDC, Pune 411013, MH, India
来源
2013 IEEE 13TH INTERNATIONAL WORKING CONFERENCE ON SOURCE CODE ANALYSIS AND MANIPULATION (SCAM) | 2013年
关键词
Static Analysis; Data Flow Analysis; Analysis Warnings; Review of Warnings; False Positives;
D O I
暂无
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
Static analysis has been successfully employed in software verification, however the number of generated warnings and cost incurred in their manual review is a major concern. In this paper we present a novel idea to reduce manual review efforts by identifying redundancy in this review process. We propose two partitioning techniques to identify redundant warnings - 1) partitioning of the warnings with each partition having one leader warning such that if the leader is a false positive, so are all the warnings in its partition which need not be reviewed and 2) further partitioning the leader warnings based on similarity of the modification points of variables referred to in their expressions. The second technique makes the review process faster by identifying further redundancies and it also makes the reviewing of a warning easier due to the associated information of modification points. Empirical results obtained with these grouping techniques indicate that, on an average, 60% of warnings are redundant in the review context and skipping their review would lead to a reduction of 50-60% in manual review efforts.
引用
收藏
页码:106 / 115
页数:10
相关论文
共 50 条
  • [21] Do Scratchers Fix Their Bugs? Detecting Fixes of Scratch Static Analysis Warnings
    Obermueller, Florian
    Fraser, Gordon
    PROCEEDINGS OF THE 19TH WIPSCE CONFERENCE IN PRIMARY AND SECONDARY COMPUTING EDUCATION RESEARCH, WIPSCE 2024, 2024,
  • [22] Ranking Source Code Static Analysis Warnings for Continuous Monitoring of FLOSS Repositories
    Ribeiro, Athos
    Meirelles, Paulo
    Lago, Nelson
    Kon, Fabio
    OPEN SOURCE SYSTEMS: ENTERPRISE SOFTWARE AND SOLUTIONS, OSS 2018, 2018, 525 : 90 - 101
  • [23] SpongeBugs: Automatically generating fix suggestions in response to static code analysis warnings
    Marcilio, Diego
    Furia, Carlo A.
    Bonifacio, Rodrigo
    Pinto, Gustavo
    JOURNAL OF SYSTEMS AND SOFTWARE, 2020, 168
  • [24] Investigating the Correspondence between Mutations and Static Warnings
    de Araujo, Caudio Antonio
    Delamaro, Marcio Eduardo
    Maldonado, Jose Carlos
    Rizzo Vincenzi, Auri Marcelo
    2015 29TH BRAZILIAN SYMPOSIUM ON SOFTWARE ENGINEERING, 2015, : 1 - 10
  • [25] StaticTracker: A Diff Tool for Static Code Warnings
    Li, Junjie
    Yang, Jinqiu
    2023 IEEE INTERNATIONAL CONFERENCE ON SOFTWARE MAINTENANCE AND EVOLUTION, ICSME, 2023, : 568 - 573
  • [26] Speech warnings: a review
    Noyes, J. M.
    Hellier, E.
    Edworthy, J.
    THEORETICAL ISSUES IN ERGONOMICS SCIENCE, 2006, 7 (06) : 551 - 571
  • [27] Typology of content warnings and trigger warnings: Systematic review
    Charles, Ashleigh
    Hare-Duke, Laurie
    Nudds, Hannah
    Franklin, Donna
    Llewellyn-Beardsley, Joy
    Rennick-Egglestone, Stefan
    Gust, Onni
    Ng, Fiona
    Evans, Elizabeth
    Knox, Emily
    Townsend, Ellen
    Yeo, Caroline
    Slade, Mike
    PLOS ONE, 2022, 17 (05):
  • [28] Using Machine Learning Techniques to Classify and Predict Static Code Analysis Tool Warnings
    Alikhashashneh, Enas A.
    Raje, Rajeev R.
    Hill, James H.
    2018 IEEE/ACS 15TH INTERNATIONAL CONFERENCE ON COMPUTER SYSTEMS AND APPLICATIONS (AICCSA), 2018,
  • [29] OASIS: Prioritizing Static Analysis Warnings for Android Apps Based on App User Reviews
    Wei, Lili
    Liu, Yepang
    Cheung, Shing-Chi
    ESEC/FSE 2017: PROCEEDINGS OF THE 2017 11TH JOINT MEETING ON FOUNDATIONS OF SOFTWARE ENGINEERING, 2017, : 672 - 682
  • [30] Static source code metrics and static analysis warnings for fine-grained just-in-time defect prediction
    Trautsch, Alexander
    Herbold, Steffen
    Grabowski, Jens
    2020 IEEE INTERNATIONAL CONFERENCE ON SOFTWARE MAINTENANCE AND EVOLUTION (ICSME 2020), 2020, : 127 - 138