A systematic gray literature review: The technologies and concerns of microservice application programming interfaces

Chen, Fangwei; Zhang, Li; Lian, Xiaoli

doi:10.1002/spe.2967

Cited by 7 publications

(2 citation statements)

References 47 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In daily practice, especially in the development of open-source projects, the programming job may start without drawing any detailed class diagrams. [11][12][13][14][15] Even if there exist some design diagrams, they may only represent some key parts of the software system (e.g., the main classes or objects). Therefore, the class diagrams resulting from those projects may only be in high-level abstraction, and the trace links between class diagrams and source code are often absent.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

CDTC: Automatically establishing the trace links between class diagrams in design phase and source code

Chen,

Zhang,

Lian

2023

Softw Pract Exp

Self Cite

View full text Add to dashboard Cite

ContextThe UML class diagram is commonly used to model functional structures and software code structures in both the preliminary and detailed design stages. And the abstraction level of UML class diagrams is usually higher than that of source code. Usually, there is a lack of trace links between these class diagrams and the source code, which may cause difficulties in understanding the source code, and affect the software evolution and maintenance.ObjectiveThe main goal of this article is to establish the trace links between highly abstracted UML class diagrams in the design phase and source code, and eventually help practitioners better understand source code.MethodWe propose an approach for the automated trace link establishment between UML class diagrams in the design phase and source code. To address the problem of abstraction level gap between them, we extend the UML class diagram by mining the synonymous phrases of class names and deducing the latent missing relationships between classes from multiple design documents. Then we build the trace links with a two‐phase approach including initial construction with fuzzy matching and further optimization by class relationship inference.ResultsExperiments on five open‐source projects show that the recalls of our approach are over 94%, and the F2‐scores are over 88%, with the gains of 30% to 60% than the four baselines.ConclusionOur work can be a reference for establishing the initial trace links between highly‐abstracted UML class diagrams and source code. Towards the higher abstraction of design diagrams, we extend UML class diagrams with the statistical analysis on multiple design documents. To guarantee the quality of trace links, we design a two‐phase approach by obtaining the “full but not good enough” trace links and filtering the “probably wrong” links. Experiments show that the main techniques of our approach behave as important role for tracing between high‐level class diagrams and source code.

show abstract

Section: Introductionmentioning

confidence: 99%

“…In daily practice, especially in the development of open‐source projects, the programming job may start without drawing any detailed class diagrams 11–15 . Even if there exist some design diagrams, they may only represent some key parts of the software system (e.g., the main classes or objects).…”

Section: Introductionmentioning

confidence: 99%

CDTC: Automatically establishing the trace links between class diagrams in design phase and source code

Chen,

Zhang,

Lian

2023

Softw Pract Exp

Self Cite

View full text Add to dashboard Cite

show abstract

Systematic scalability analysis for microservices granularity adaptation design decisions

2022

View full text Add to dashboard Cite

Microservices have gained wide recognition and acceptance in software industries as an emerging architectural style for autonomous, scalable, and more reliable computing. A critical problem related to microservices is reasoning about the suitable granularity level of a microservice (i.e. when and how to merge or decompose microservices). Although scalability is pronounced as one of the major factors for adoption of microservices, there is a general gap of approaches that systematically analyse the dimensions and metrics which are important for scalability-aware granularity adaptation decisions. To the best of our knowledge, the stateof-art in reasoning about microservice granularity adaptation is neither: 1) driven by microservice-specific scalability dimensions and metrics nor, 2) follow systematic scalability analysis to make scalability-aware adaptation decisions. In this paper, we address the aforementioned problems using a two-fold contribution.Firstly, we contribute to a working catalogue of microservice-specific scalability dimensions and metrics.Secondly, we describe a novel application of scalability goal-obstacle analysis for the context of reasoning about microservice granularity adaptation. We analyse both contributions by comparing their usage on a hypothetical microservice architecture against ad-hoc scalability assessment for the same architecture. This analysis shows how both contributions can aid making scalability-aware granularity adaptation decisions.

show abstract

Microservice API Evolution in Practice: A Study on Strategies and Challenges

Lercher,

Glock,

Macho

et al. 2024

Journal of Systems and Software

View full text Add to dashboard Cite

A systematic gray literature review: The technologies and concerns of microservice application programming interfaces

Cited by 7 publications

References 47 publications

CDTC: Automatically establishing the trace links between class diagrams in design phase and source code

CDTC: Automatically establishing the trace links between class diagrams in design phase and source code

Systematic scalability analysis for microservices granularity adaptation design decisions

Microservice API Evolution in Practice: A Study on Strategies and Challenges

Contact Info

Product

Resources

About