Generating CAM aspect-oriented architectures using Model-Driven Development

Fuentes, Lidia; Pinto, Mónica; Sánchez, Pablo

doi:10.1016/j.infsof.2007.10.020

Cited by 6 publications

(5 citation statements)

References 40 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Most of the conclusions has been obtained after applying aspect-orientation and executable modelling to different case-studies and domains, such as a tool gate system [40], an online book store system [16] or an auction system [14]. These results also apply to pervasive applications, since typical concerns of this domain, such as concerns contextawareness [46], have been demonstrated to be crosscutting concerns.…”

Section: Discussionmentioning

confidence: 93%

Aspect-oriented design and implementation of context-aware pervasive applications

Fuentes

Gámez

Sánchez

2009

Innovations Syst Softw Eng

Self Cite

View full text Add to dashboard Cite

Pervasive applications must be aware of the contexts where they are executed. These contexts may vary greatly and change quickly. Two main problems are associated with this issue: (1) context-awareness is a crosscutting concern that cannot be well-encapsulated in a single module using traditional technologies, thus hindering software maintenance and reusability; and (2) reasoning about application design correctness can be complex due to the number and diversity of potential contexts where a pervasive application could be executed. In order to overcome these problems, we present a process for the design and implementation of context-aware pervasive applications that uses aspect-orientation and executable modelling in order to overcome these shortcomings. Aspect-oriented techniques contribute to the encapsulation of crosscutting concerns, such as context-awareness, into well-localized modules. Executable modelling helps engineers to reason about application design by executing the design models in different contexts and situations. Pervasive applications are modelled using the aspect-oriented executable modelling UML 2.0 profile, executed at the modelling level for testing purposes, and then mapped into an aspect-oriented middleware platform for pervasive applications. This process is illustrated using a

show abstract

Section: Discussionmentioning

confidence: 93%

Aspect-oriented design and implementation of context-aware pervasive applications

Fuentes

Gámez

Sánchez

2009

Innovations Syst Softw Eng

Self Cite

View full text Add to dashboard Cite

show abstract

“…This way, the pointcut is expressed by pattern matching. In [79] it is based on explicitly marking the UML models involved. In our case we use both a programmatic and annotation-based approach.…”

Section: Aspect-oriented Modellingmentioning

confidence: 99%

Open meta-modelling frameworks via meta-object protocols

Cuadrado

Lara

2018

Journal of Systems and Software

View full text Add to dashboard Cite

Meta-modelling is central to Model-Driven Engineering. Many meta-modelling notations, approaches and tools have been proposed along the years, which widely vary regarding their supported modelling features. However, current approaches tend to be closed and rigid with respect to the supported concepts and semantics. Moreover, extending the environment with features beyond those natively supported requires highly technical knowledge. This situation hampers flexibility and interoperability of meta-modelling environments. In order to alleviate this situation, we propose open meta-modelling frameworks, which can be extended and configured via meta-object protocols (MOPs). Such environments offer extension points on events like element instantiation, model loading or property access, and enable selecting particular model elements over which the extensions are to be executed. We show how MOP-based mechanisms permit extending meta-modelling frameworks in a flexible way, and allow describing a wide range of meta-modelling concepts. As a proof of concept, we show and compare an implementation in the MetaDepth tool and an aspectbased implementation atop the Eclipse Modelling Framework (EMF). We have evaluated our approach by extending EMF and MetaDepth with modelling services not foreseen initially when they were created. The evaluation shows that MOP-based mechanisms permit extending meta-modelling frameworks in a flexible way, and are powerful enough to support the specification of a broad variety of meta-modelling features.

show abstract

“…In the latter case, the designer or developer would need to manually weave the aspectual components with the components they crosscut and the benefits achieved by the aspect-oriented decomposition will lose, so this option is not recommended at least it is strictly required. (2) The CAM aspect-oriented architecture can be used to automatically generate (see [44]a,2008b)) a DAOP-ADL description, which is used to run an application on the DAOP platform [85,43]. The DAOP platform is a distributed component and aspect based platform, where aspects and components are dynamically composed at runtime using the information provided by the DAOP-ADL aspect-oriented architectural description language [84].…”

Section: Step 4: Transformation Executionmentioning

confidence: 99%

“…Table 3 explains how these metrics work. The architecture designs for two of the case studies (the Auction System and the Online Book Store) can be found in our previous work [44,41] and the architecture for the Toll Gate system is the contained in this paper.…”

Section: Aosd Improves Modularisationmentioning

confidence: 99%

“…Our approach generates as output an aspect-oriented software architecture that is expressed in the UML 2.0 Profile for CAM. This software architecture description language has been used for expressing a wide range of systems [85,25,43,90,44], but it is unrealistic to think it can be used to express the architecture of any existing software system. So, if, for any reason, the architecture of a software system cannot be adequately expressed in the UML 2.0 Profile for CAM, our approach would be not applicable.…”

Section: Applicability: Threats To Validitymentioning

confidence: 99%

See 1 more Smart Citation