Integrating Static Code Analysis Toolchains
- URL: http://arxiv.org/abs/2403.05986v1
- Date: Sat, 9 Mar 2024 18:59:50 GMT
- Title: Integrating Static Code Analysis Toolchains
- Authors: Matthias Kern, Ferhat Erata, Markus Iser, Carsten Sinz, Frederic
Loiret, Stefan Otten, Eric Sax
- Abstract summary: State of the art toolchains support features for either test execution and build automation or traceability between tests, requirements and design information.
Our approach combines all those features and extends traceability to the source code level, incorporating static code analysis.
- Score: 0.8246494848934447
- License: http://arxiv.org/licenses/nonexclusive-distrib/1.0/
- Abstract: This paper proposes an approach for a tool-agnostic and heterogeneous static
code analysis toolchain in combination with an exchange format. This approach
enhances both traceability and comparability of analysis results. State of the
art toolchains support features for either test execution and build automation
or traceability between tests, requirements and design information. Our
approach combines all those features and extends traceability to the source
code level, incorporating static code analysis. As part of our approach we
introduce the "ASSUME Static Code Analysis tool exchange format" that
facilitates the comparability of different static code analysis results. We
demonstrate how this approach enhances the usability and efficiency of static
code analysis in a development process. On the one hand, our approach enables
the exchange of results and evaluations between static code analysis tools. On
the other hand, it enables a complete traceability between requirements,
designs, implementation, and the results of static code analysis. Within our
approach we also propose an OSLC specification for static code analysis tools
and an OSLC communication framework.
Related papers
Err
This list is automatically generated from the titles and abstracts of the papers in this site.
This site does not guarantee the quality of this site (including all information) and is not responsible for any consequences.