@inproceedings{MendoncaK20,
  author    = {Diogo S. Mendon\c{c}a and Marcos Kalinowski},
  title     = {Towards Pratical Reuse of Custom Static Analysis Rules for Defect Localization},
  abstract  = {[Context] Several static analysis tools allow the development of custom rules for locating application-specific defects. Although this feature is powerful and commonly available, it is not well explored in practice. Custom static analysis rules can check design and policies that are shared between applications, allowing the reuse of rules. However, the benefits, scope, and concerns that software engineers should have on reusing custom static analysis rules are unknown. [Goal] In this preliminary study, we investigate the reuse of custom static analysis rules produced by applying Pattern-Driven Maintenance (PDM). PDM is a method to locate defect patterns in web applications that produces custom static analysis rules as output. [Method] We selected a set of rules produced by a previous usage of the PDM method and applied them to other three applications in two contexts, within the same company where the rules were produced, and in other companies. [Results] We successfully reused some rules in both scenarios with minor adjustments, finding new defects to be fixed. The reuse of rules could discard from 58-90% of source code locations found by a naive search for the defects, reducing verification effort. However, the reused rules need adjustments to improve precision for defect localization, as precision ranged from 40-75%. Finally, we identified factors that have an impact on reusing custom rules. [Conclusions] We put forward that reusing customized static analysis rules can be beneficial, in particular when similarities in the architecture and programming style are observed. However, adjustment of the rules might be needed to enable effective reuse. We shared our insights and methodology on how to reuse custom static analysis rules properly.},
  booktitle = {Proceedings of the XIX Brazilian Symposium on Software Quality, {SBQS'20}, Brazil, December 1st - December 4th},
  pages     = {24:1-24:10},
  note      = {},
  year      = {2020},
  urlAuthor_version       = {http://www.inf.puc-rio.br/~kalinowski/publications/MendoncaK20.pdf},
  doi       = {},
}

{"_id":"g4GP4EAGD67AmfhrK","bibbaseid":"mendona-kalinowski-towardspraticalreuseofcustomstaticanalysisrulesfordefectlocalization-2020","authorIDs":["2QsG9mfJnwX6MTuoJ"],"author_short":["Mendonça, D. S.","Kalinowski, M."],"bibdata":{"bibtype":"inproceedings","type":"inproceedings","author":[{"firstnames":["Diogo","S."],"propositions":[],"lastnames":["Mendonça"],"suffixes":[]},{"firstnames":["Marcos"],"propositions":[],"lastnames":["Kalinowski"],"suffixes":[]}],"title":"Towards Pratical Reuse of Custom Static Analysis Rules for Defect Localization","abstract":"[Context] Several static analysis tools allow the development of custom rules for locating application-specific defects. Although this feature is powerful and commonly available, it is not well explored in practice. Custom static analysis rules can check design and policies that are shared between applications, allowing the reuse of rules. However, the benefits, scope, and concerns that software engineers should have on reusing custom static analysis rules are unknown. [Goal] In this preliminary study, we investigate the reuse of custom static analysis rules produced by applying Pattern-Driven Maintenance (PDM). PDM is a method to locate defect patterns in web applications that produces custom static analysis rules as output. [Method] We selected a set of rules produced by a previous usage of the PDM method and applied them to other three applications in two contexts, within the same company where the rules were produced, and in other companies. [Results] We successfully reused some rules in both scenarios with minor adjustments, finding new defects to be fixed. The reuse of rules could discard from 58-90% of source code locations found by a naive search for the defects, reducing verification effort. However, the reused rules need adjustments to improve precision for defect localization, as precision ranged from 40-75%. Finally, we identified factors that have an impact on reusing custom rules. [Conclusions] We put forward that reusing customized static analysis rules can be beneficial, in particular when similarities in the architecture and programming style are observed. However, adjustment of the rules might be needed to enable effective reuse. We shared our insights and methodology on how to reuse custom static analysis rules properly.","booktitle":"Proceedings of the XIX Brazilian Symposium on Software Quality, SBQS'20, Brazil, December 1st - December 4th","pages":"24:1-24:10","note":"","year":"2020","urlauthor_version":"http://www.inf.puc-rio.br/~kalinowski/publications/MendoncaK20.pdf","doi":"","bibtex":"@inproceedings{MendoncaK20,\r\n author = {Diogo S. Mendon\\c{c}a and Marcos Kalinowski},\r\n title = {Towards Pratical Reuse of Custom Static Analysis Rules for Defect Localization},\r\n abstract = {[Context] Several static analysis tools allow the development of custom rules for locating application-specific defects. Although this feature is powerful and commonly available, it is not well explored in practice. Custom static analysis rules can check design and policies that are shared between applications, allowing the reuse of rules. However, the benefits, scope, and concerns that software engineers should have on reusing custom static analysis rules are unknown. [Goal] In this preliminary study, we investigate the reuse of custom static analysis rules produced by applying Pattern-Driven Maintenance (PDM). PDM is a method to locate defect patterns in web applications that produces custom static analysis rules as output. [Method] We selected a set of rules produced by a previous usage of the PDM method and applied them to other three applications in two contexts, within the same company where the rules were produced, and in other companies. [Results] We successfully reused some rules in both scenarios with minor adjustments, finding new defects to be fixed. The reuse of rules could discard from 58-90% of source code locations found by a naive search for the defects, reducing verification effort. However, the reused rules need adjustments to improve precision for defect localization, as precision ranged from 40-75%. Finally, we identified factors that have an impact on reusing custom rules. [Conclusions] We put forward that reusing customized static analysis rules can be beneficial, in particular when similarities in the architecture and programming style are observed. However, adjustment of the rules might be needed to enable effective reuse. We shared our insights and methodology on how to reuse custom static analysis rules properly.},\r\n booktitle = {Proceedings of the XIX Brazilian Symposium on Software Quality, {SBQS'20}, Brazil, December 1st - December 4th},\r\n pages = {24:1-24:10},\r\n note = {},\r\n year = {2020},\r\n urlAuthor_version = {http://www.inf.puc-rio.br/~kalinowski/publications/MendoncaK20.pdf},\r\n doi = {},\r\n}\r\n\r\n","author_short":["Mendonça, D. S.","Kalinowski, M."],"key":"MendoncaK20","id":"MendoncaK20","bibbaseid":"mendona-kalinowski-towardspraticalreuseofcustomstaticanalysisrulesfordefectlocalization-2020","role":"author","urls":{"Author version":"http://www.inf.puc-rio.br/~kalinowski/publications/MendoncaK20.pdf"},"metadata":{"authorlinks":{"kalinowski, m":"https://www-di.inf.puc-rio.br/~kalinowski/publications.html"}},"downloads":0,"html":""},"bibtype":"inproceedings","biburl":"https://bibbase.org/f/2Gq6bNPQ845THHiMW/KalinowskiPapers.bib","creationDate":"2020-11-03T21:57:22.311Z","downloads":0,"keywords":[],"search_terms":["towards","pratical","reuse","custom","static","analysis","rules","defect","localization","mendonça","kalinowski"],"title":"Towards Pratical Reuse of Custom Static Analysis Rules for Defect Localization","year":2020,"dataSources":["JhEx5LqjNuowkDTYw","vp6ff9ZJkhXGDuh9E","FPdHx2YNMWt6KHbaS","oL8GbjE74fizfjkxY","Wbj3iHa4hGsGjEGJE","q7rgFjFgwoTSGkm3G","aKfxcyv7C9p9ytdpG","9pAzChfPy53GguqQk","B8Jierr7smZsGa7Jb","tvqztEQv84agmtPEB","FGDKYBjH9upApdKoL"]}