An Aspect Oriented Model Driven Framework

Simmonds, Devon; Solberg, Arnor; Reddy, Raghu; Ghosh, Sudipto

doi:10.1109/edoc.2005.5

Cited by 33 publications

(27 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…From a component-based standpoint some projects [2][3][4] try to satisfy system NFRs through a model-driven process for selecting components to achieve systemic NFRs, and later configuring and deploying the selected components. Other projects from a more design-oriented approach [5][6][7][8] aim to generate implementations that satisfy multiples NFRs at once, starting out from design description at platform-independent (PIM) level; thus, NFRs must be modeled and solved at prior stages.…”

Section: Mda Nfrs and Component-based Developmentmentioning

confidence: 99%

“…The platform-independent model P IM v for each concern v may also be implemented with a MDA approach for NFRs [5][6][7][8], or may be mapped to selected COTS. In the former case, each P IM v generates a P SM v as encoded in the P M v .…”

Section: Treatment Of Policies-specific Pimsmentioning

confidence: 99%

“…Some recent projects [2][3][4][5][6][7][8][9] have addressed explicit mechanisms to satisfy NFRs through MDA transformations. From a component-based standpoint some projects [2][3][4] try to satisfy system NFRs through a model-driven process for selecting components to achieve systemic NFRs, and later configuring and deploying the selected components.…”

Section: Mda Nfrs and Component-based Developmentmentioning

confidence: 99%

“…Some proposals [2][3][4][5][6][7][8][9] extend MDA to deal explicitly with NFRs, especially from a perspective of components more than from detailed software design. Yet remains much work to be done: there is no traceability of decisions from NFRs to architecture to design and to final implementation, nor techniques to generate hybrid solutions that combine pre-existing components and ad-hoc development.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Explicit Architectural Policies to Satisfy NFRs Using COTS

López

Astudillo

2006

Satellite Events at the MoDELS 2005 Conference

View full text Add to dashboard Cite

Abstract. Software architecture decisions hinge more on non-functional requirements (NFRs) than on functional ones, since the architecture stipulates which software to build. Model-Driven Architecture (MDA) aims to automate the derivation/generation of software from high level architectural specifications, but most current MDA implementations start from software design (i.e. how to build a software piece) rather than software architecture. This article presents an approach to extend MDA through the concepts of architectural policies and mechanisms. The key ideas are representation of NFRs through architectural concerns using architectural policies, systematic reification of policies into mechanisms, and multi-dimensional description of components as implementators of mechanisms. A detailed illustrative example is provided. Azimut framework realizes these ideas, supports larger-scale work through catalogs of policies and components, and allows traceability and reuse of architecture by enabling enabling these architecture-level descriptions and reasoning.

show abstract

Section: Mda Nfrs and Component-based Developmentmentioning

confidence: 99%

Section: Treatment Of Policies-specific Pimsmentioning

confidence: 99%

Section: Mda Nfrs and Component-based Developmentmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Explicit Architectural Policies to Satisfy NFRs Using COTS

López

Astudillo

2006

Satellite Events at the MoDELS 2005 Conference

View full text Add to dashboard Cite

show abstract

“…AOM [1] is a recent development paradigm that aims at providing support for separation of concerns at higher levels of abstraction by using ModelDriven Engineering (MDE) techniques [2]. The main goal of AOM approaches is to enable both vertical and horizontal separation of concerns [3].…”

Section: Introductionmentioning

confidence: 99%

Specifying and Composing Concerns Expressed in Domain-Specific Modeling Languages

Hovsepyan

Baelen

Berbers

et al. 2009

Objects, Components, Models and Patterns

View full text Add to dashboard Cite

Summary. Separation of concerns and levels of abstraction are key software engineering principles that can help master the increasing complexity of software applications. Aspect-oriented modeling (AOM) and domain-specific modeling languages (DSML) are two important and promising approaches in this context. However, little research is done to investigate the synergy between AOM and DSMLs. In this paper we present an asymmetric approach to compose modularized concerns expressed in different DSMLs with an application base model expressed in a general-purpose modeling language (GPML). This allows to specify each concern in the most appropriate modeling language. We introduce the concept of a concern interface, expressed in a GPML, that serves as a common language between a specific concern and the application base. In addition, we use an explicit composition model to specify the syntactic and the semantic links between entities from the different concerns. We explore these concepts using an application where we modularize the user interface modeled in WebML and the access control specified in XACML. The modularized concerns are then composed with an application base that has been specified in UML.

show abstract

Construction and Execution of Adaptable Applications Using an Aspect-Oriented and Model Driven Approach

Lundesgaard

Solberg

Oldevik

et al. 2007

Distributed Applications and Interoperable Systems

View full text Add to dashboard Cite

Abstract. Constructing and executing distributed applications that can adapt to their current operating context, in order to maintain or enhance Quality of Service (QoS) attribute levels, are complex tasks. Managing multiple, interacting QoS features is particularly difficult since these features tend to be distributed across the system and tangled with other features. The crosscutting nature of QoS features can make them difficult to evolve, and it can make it complicated to dynamically optimize with respect to provided QoS during execution. Furthermore, it complicates efficient construction of application variants that differ in their QoS characteristics to suit various execution contexts. This paper presents an aspect-oriented and model driven approach for constructing and a QoSaware middleware for execution of QoS-sensitive applications. Aspect-oriented modeling techniques are used to separate QoS features from primary application logic, and for efficient specification of alternative application variants. Model driven engineering techniques are used to derive run-time representations of application variants from platform independent models. The developed middleware chooses the best variant according to the current operating context and the available resources.

show abstract

An Aspect Oriented Model Driven Framework

Abstract: In model driven development (MDD)

Cited by 33 publications

References 12 publications

Explicit Architectural Policies to Satisfy NFRs Using COTS

Explicit Architectural Policies to Satisfy NFRs Using COTS

Specifying and Composing Concerns Expressed in Domain-Specific Modeling Languages

Construction and Execution of Adaptable Applications Using an Aspect-Oriented and Model Driven Approach

Contact Info

Product

Resources

About