REVIEW 2 cited by
Comparison of Static Analysis Architecture Recovery Tools for Microservice Applications
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Architecture recovery tools help software engineers obtain an overview of their software systems during all phases of the software development lifecycle. This is especially important for microservice applications because their distributed nature makes it more challenging to oversee the architecture. Various tools and techniques for this task are presented in academic and grey literature sources. Practitioners and researchers can benefit from a comprehensive overview of these tools and their abilities. However, no such overview exists that is based on executing the identified tools and assessing their outputs regarding effectiveness. With the study described in this paper, we plan to first identify static analysis architecture recovery tools for microservice applications via a multi-vocal literature review, and then execute them on a common dataset and compare the measured effectiveness in architecture recovery. We will focus on static approaches because they are also suitable for integration into fast-paced CI/CD pipelines.
Forward citations
Cited by 2 Pith papers
-
Comparison of Static Analysis Architecture Recovery Tools for Microservice Applications
Across 17 microservice applications, Code2DFD achieved the highest individual F1-score of 0.86 among nine static architecture recovery tools, with an in-sample four-tool combination reaching 0.91.
-
Network Centrality as a New Perspective on Microservice Architecture
Centrality metrics calculated on service dependency graphs are only weakly to moderately correlated with traditional size, complexity, and quality metrics across 53 microservices, suggesting they capture a distinct ar...
Discussion (0). Continue with ORCID to comment.