Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Dataset . 2024
License: CC BY
Data sources: ZENODO
addClaim

Replication Kit - What the Fix? A Study of ASATs Rule Documentation

Authors: Latappy, Corentin; Degueule, Thomas; Falleri, Jean-Rémy; Robbes, Romain; Blanc, Xavier; Teyton, Cedric;

Replication Kit - What the Fix? A Study of ASATs Rule Documentation

Abstract

Contains all artefacts for our publication: What the Fix? A Study of ASATs Rule Documentation @ ICPC 2024Content survey: Archive from LimeSurvey, rules annotated used and raw results taxonomy_validation: Rules annotated by the authors to validate the taxonomy and notebook computing kappa values website: Build of the companion webpage (currently hosted at https://icpc2024-asats.github.io) Paper abstractAutomatic Static Analysis Tools (ASATs) are widely used by software developers to diffuse and enforce coding practices. Yet, we know little about the documentation of ASATs, despite it being critical to learn about the coding practices in the first place. We shed light on this through a two-phase study. First, we analyze the documentation of more than 100 rules of 16 ASATs for multiple programming languages, and distill a taxonomy of the goals of the documentation and its types of contents. Then, we conduct a survey to assess the effectiveness of the documentation in terms of its goals and types of contents. We highlight opportunities for improvement in ASAT documentation.

Keywords

software quality, documentation, linters, automatic static analysis tools

Powered by OpenAIRE graph
Found an issue? Give us feedback