Aspectual templates in UML

Vanwormhoudt, Gilles; Caron, Olivier; Carré, Bernard

doi:10.1007/s10270-015-0463-3

Cited by 12 publications

(19 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Besides the UML, some other approaches follow the idea of binding templates. Examples include aspectual templates and templates from template metaprogramming [, p. 514] (e.g., C++ templates and Java generics). Alternative template approaches do not bind but instantiate whole models (initiator templates).…”

Section: Foundationsmentioning

confidence: 99%

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

Section: Foundationsmentioning

confidence: 99%

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

2017

View full text Add to dashboard Cite

show abstract

“…In this section, a reminder on UML templates and their aspectual enhancement [18] are presented to ground the study.…”

Section: Background On Uml Templatesmentioning

confidence: 99%

“…In our previous work [18], we deeply studied the aspectual interpretation of UML templates with the requirement that parameters have to form a well formed modeling structure to which candidate models must have to conform. Following this requirement, we stated a semantical enhancement of UML templates which consists in enforcing templates to have a full model as parameter.…”

Section: Parameters As a Modelmentioning

confidence: 99%

“…Partial binding is a powerful feature that allows modelers to obtain richer templates through the composition of templates. It was deeply studied in our preceding work [18] for aspectual templates. Following UML principles concerning parameter substitution and propagation of the unsubstituted parameters, partial instantiation can be offered to benefit from additional capacities.…”

Section: Partial Instantiationmentioning

confidence: 99%

“…This construct is general enough to support MBE reuse practices ranging from the representation at a model level of generic software components (such as C++ templates or Java generics) to the weaving of reusable functionalities into models, mainly the way aspect-, pattern-and view-oriented modeling do. In our prior work [18], we contributed to this research by enhancing the semantics of UML Templates for their aspectual interpretation. This leads to so called "aspectual templates" whose parameters must form a model of systems in which to inject the functionalities.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Isolating and Reusing Template Instances in UML

Allon

Vanwormhoudt

Carré

et al. 2016

Modelling Foundations and Applications

Self Cite

View full text Add to dashboard Cite

International audienceIn MBE, design of systems can be improved and accelerated thanks to reusable models which are made available in model repositories or libraries. One answer for designing reusable models is parameterization as o↵ered by UML templates and their binding relationship. The stan- dard aims at embracing under the same constructs two distinct kinds of template usages, namely template instantiation and aspectual binding. Template instantiation is concerned with the capacity of UML templates to model generic components (like C++ templates or Java generics) and produce new models from their binding. Aspectual binding is much more concerned with the capacity of UML templates to specify functionalities to inject into models of systems (contexts) which must conform to a required parameter model. In this paper, we focus on the generative in- terpretation of UML template binding. On the basis of a deep analysis of the standard, it will be shown that template binding consists in template instantiation plus context merging. This allows to isolate the capacity of instantiating templates (under their generative view) to get reusable models coming from applicative contexts. Then the possibility of partial instantiation inspired by partial binding as promoted by the standard is studied. At a practical level, related functionalities are o↵ered within Eclipse

show abstract