Preserving architectural decisions through architectural patterns

That, Minh Tu Ton; Sadou, Salah; Oquendo, Flávio; Fleurquin, Régis

doi:10.1007/s10515-014-0172-0

Cited by 4 publications

(8 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Moreover, this paper focuses on the structural part in supporting the conformance checking, because those related to the architectural structure affect the system on the highest-level of abstraction and have the highest potential to be automatically checked. 17 We note that it does not mean other parts of a domain model (such as the concerns) are not important. Instead, together they make a complete structure of a domain model that supports both the implementation and the automatic conformance checking.…”

Section: Pattern Conformance Checking With Domicomentioning

confidence: 99%

“…Designing the Cargo object as an Entity is a pattern‐related architectural decision that needs to be kept throughout the evolution of this system. The verification of a pattern‐related decision should focus on two aspects: 17 (1) the existence of pattern‐related elements and (2) the conformance of pattern constraints. Specifically, from the viewpoint of the first aspect, the above decision is considered to be preserved as long as a Cargo element designed as an Entity exists in the code.…”

Section: Pattern Conformance Checking With Domicomentioning

confidence: 99%

“…The non‐conformance on a pattern indicates the missing or violation of certain design decisions in source codes. Given that DDD patterns concern some of the most significant architectural decisions, checking pattern conformance is critical to ensure that the implemented software (microservices) addresses the expected quality requirements 17 …”

Section: Introductionmentioning

confidence: 99%

“…Given that DDD patterns concern some of the most significant architectural decisions, checking pattern conformance is critical to ensure that the implemented software (microservices) addresses the expected quality requirements. 17 The objective of this paper is to provide a methodological support for automatically checking DDD pattern conformance between domain models and implementations. To this end, a tool-supported approach called DOMICO (DOmain Model & Implementation COnformance) is proposed.…”

Section: Introductionmentioning

confidence: 99%

“…DOMICO applies two fundamental principles for preserving pattern-related architectural decisions. 17 First, the existence of pattern-related elements that were previously used in an intended domain model needs to be verified. Thus, it becomes possible to discover whether a pattern (design decision) is implemented.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

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: Pattern Conformance Checking With Domicomentioning

confidence: 99%

Section: Pattern Conformance Checking With Domicomentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

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

The architectural template method: templating architectural knowledge to efficiently conduct quality‐of‐service analyses

2017

View full text Add to dashboard Cite

Software architects plan the realization of software systems by assessing design decisions on the basis of architectural models. Using these models as input, architectural analyses assess the impact of architects' decisions on quality-of-service properties. While the creation of suitable architectural models requires software architects to apply complex architectural knowledge, for example, in the form of established architectural styles and patterns, current architectural analyses lack support for directly reusing such knowledge. This lack points to an unused potential to make the work of software architects more effective and efficient.To use this potential, we introduce the architectural template (AT) method, an engineering method that makes design-time analyses of quality-of-service properties of software systems more efficient. The AT method allows to quantify quality-of-service properties on the basis of reusable modeling templates that capture recurring architectural knowledge. Architects just need to customize such templates with system-specific parts. In a case study, we illustrate the applicability of the AT method in the domains of distributed and cloud computing and its suitability for the quality-of-service properties performance, scalability, elasticity, and cost-efficiency. TEMPLATING ARCHITECTURAL KNOWLEDGE TO EFFICIENTLY CONDUCT QOS ANALYSES 269 which may be used by clients to judge service quality' [9]. Architectural analyses quantify QoS properties on the basis ofS architectural models of a targeted system. These quantifications enable early evaluations and, thus, inexpensive revisions of disadvantageous design decisions. However, the creation of suitable architectural models for architectural analyses has formerly required a high modeling effort [10, p. 458]-even in recurring modeling situations [11].To approach this problem, this paper contributes the architectural template (AT) method as an extension to architectural analyses and illustrates its application in the cloud computing domain. The AT method provides software architects with templates that formally capture reusable architectural knowledge (such as architectural styles and architectural patterns) for recurring modeling and analysis situations. By applying such templates to architectural models, software architects become more effective and efficient because captured design decisions can automatically be integrated into architectural models, checked for consistency, and be analyzed.In the following, this introductory section refines this motivation and idea behind the AT method and gives an overview of this paper. Analyzing quality-of-serviceA concrete category of engineering approaches are architectural analyses [2, p. 291]. In Koziolek's process for architectural analyses [12, p. 3] (see 'QoS analysis model' and 'analysis results' of Figure 1), software architects quantify a system's QoS properties on the basis of architectural models that (semi-)formally capture taken decisions, for example, the structure of the planned software. ...

show abstract

Pathways for statically mining the Model-View-Controller software architecture on mobile applications

Dobrean

Dioşan

2022

Soft Comput

View full text Add to dashboard Cite

Preserving architectural decisions through architectural patterns

Cited by 4 publications

References 34 publications

DOMICO: Checking conformance between domain models and implementations

DOMICO: Checking conformance between domain models and implementations

The architectural template method: templating architectural knowledge to efficiently conduct quality‐of‐service analyses

Pathways for statically mining the Model-View-Controller software architecture on mobile applications

Contact Info

Product

Resources

About