Towards a UML Profile for Domain-Driven Design of Microservice Architectures

Rademacher, Florian; Sachweh, Sabine; Zündorf, Albert

doi:10.1007/978-3-319-74781-1_17

Cited by 20 publications

(9 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We note that DDD uses the broad sense of domain model which means a conscious form of knowledge abstracted for solving the problem domain 2,16 . Yet typically, microservice practitioners (e.g., References 19 and 20) use diagrams to anchor discussions in design and refer to these diagrams as domain models in the narrow sense. It is noteworthy that this paper uses the narrow sense of domain model.…”

Section: Background and Related Workmentioning

confidence: 99%

DOMICO: Checking conformance between domain models and implementations

Zhong,

Zhang,

Huang

et al. 2023

Softw Pract Exp

View full text Add to dashboard Cite

As a predominant design method for microsservices architecture (MSA), domain‐driven design (DDD) utilizes a series of standard patterns in both models and implementations to effectively support the design of architectural elements. However, an implementation may deviate from its original domain model that uses certain patterns. The deviation between a domain model and its implementation is a type of architectural drift, which needs to be detected promptly. This paper proposes an approach, namely DOMICO, to check the conformance between the domain model and its implementation, by which the conformance is formalized by defining eight common structural patterns of domain modeling and their representations in both models and the corresponding source code. Based on the formalization, our approach can not only identify the discrepancies (e.g., divergence, absence, and modification) with respect to pattern elements, but also detect possible violations of 24 compliance rules imposed by the patterns. To validate DOMICO, we performed a case study to investigate its use in a supply chain project and its performance. The results show that DOMICO can accurately identify 100% inconsistency issues in the cases examined. As the first conformance checking approach for DDD, DOMICO can be integrated into the regular domain modeling process and help ensure the conformity of microservice implementations to models.

show abstract

Section: Background and Related Workmentioning

confidence: 99%

DOMICO: Checking conformance between domain models and implementations

Zhong,

Zhang,

Huang

et al. 2023

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…Their solutions are usually represented with UML class, object, and interaction diagrams, sometimes exemplified by concrete arrangements of objects. Some researchers have discussed techniques to represent these patterns directly using UML or using UML extensions for patterns (like UML profiles) [38], [39], and few directly with UML templates [40], [41]. For instance, Sunyé discussed the representation of patterns with a former version of UML in which templates were named ''parameterized collaborations'' [40] and Vanwormhoudt et al with the current version of UML [30], [42].…”

Section: E Related Conceptsmentioning

confidence: 99%

UML Templates Distilled

Farinha¹,

Silva

2022

IEEE Access

View full text Add to dashboard Cite

UML templates are possibly the most neglected and misused piece of knowledge in UML modelling. This subject has been disregarded in the research and practice literature and even by modelling tools providers. This paper suggests that such oblivion results from a general misunderstanding that UML templates are just graphical representations of genericity like it is found in programming languages, and from the insufficient support from the modelling tools, with a consequence of poor usage of UML templates in practice. Indeed, the capabilities and potential of UML templates are far-reaching. Increasing awareness around them could bring significant benefits for UML users, namely, higher-level abstraction and reuse. Therefore, this paper provides a distilling tutorial on UML templates to highlight their flexibility and advantages. That presentation follows a tutorial style and is supported by several illustrative examples, varying from simpler to more complex ones. This tutorial reviews the Template construct's core concepts and terminology, presents constraining classifiers and shows how to define properties and operations as template parameters. Then, it presents and discusses advanced aspects such as operation templates, parameter defaults, the relationship between binding and generalization, and the specific semantics of package templates. Furthermore, the paper discusses the related work and uncovers some of the UML templates' limitations and opportunities for improvement.INDEX TERMS Object-oriented modelling, genericity, UML, templates, UML templates.

show abstract

“…Arrow semantics follow those of UML for dependency specifications [55] correct usage of the patterns. Second, the language considers underspecification in DDD-based domain model construction [59], thereby facilitating model construction for domain experts. However, microservice developers may later resolve underspecification to enable automated model processing [61].…”

Section: Microservice Architecture Model Constructionmentioning

confidence: 99%

Applying Model-Driven Engineering to Stimulate the Adoption of DevOps Processes in Small and Medium-Sized Development Organizations

et al. 2021

Self Cite

View full text Add to dashboard Cite

Microservice architecture (MSA) denotes an increasingly popular architectural style in which business capabilities are wrapped into autonomously developable and deployable software components called microservices. Microservice applications are developed by multiple DevOps teams each owning one or more services. In this article, we explore the state of how DevOps teams in small and medium-sized organizations (SMOs) cope with MSA and how they can be supported. We show through a secondary analysis of an exploratory interview study comprising six cases, that the organizational and technological complexity resulting from MSA poses particular challenges for small and medium-sized organizations (SMOs). We apply model-driven engineering to address these challenges. As results of the second analysis, we identify the challenge areas of building and maintaining a common architectural understanding, and dealing with deployment technologies. To support DevOps teams of SMOs in coping with these challenges, we present a model-driven workflow based on LEMMA—the Language Ecosystem for Modeling Microservice Architecture. To implement the workflow, we extend LEMMA with the functionality to (i) generate models from API documentation; (ii) reference remote models owned by other teams; (iii) generate deployment specifications; and (iv) generate a visual representation of the overall architecture. We validate the model-driven workflow and our extensions to LEMMA through a case study showing that the added functionality to LEMMA can bring efficiency gains for DevOps teams. To develop best practices for applying our workflow to maximize efficiency in SMOs, we plan to conduct more empirical research in the field in the future.

show abstract

Towards a UML Profile for Domain-Driven Design of Microservice Architectures

Cited by 20 publications

References 10 publications

DOMICO: Checking conformance between domain models and implementations

DOMICO: Checking conformance between domain models and implementations

UML Templates Distilled

Applying Model-Driven Engineering to Stimulate the Adoption of DevOps Processes in Small and Medium-Sized Development Organizations

Contact Info

Product

Resources

About