Prototyping and Composing Aspect Languages

Havinga, Wilke; Bergmans, Lodewijk; Akşit, Mehmet

doi:10.1007/978-3-540-70592-5_9

Cited by 15 publications

(6 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In other words, one aspect can also be woven to other aspects; this is also called advising advices or foreign advising in [50]. Consequently, ACSD approaches need to provide means for allowing and prohibiting, when needed, the execution of aspects on other aspects and to provide means to avoid infinite interception loops [49] if aspects on aspects are enabled.…”

Section: Support For Aspect Interaction Managementmentioning

confidence: 99%

“…In some other cases, we need to prohibit such interactions; the Safety feature of our example shows this phenomenon; in this particular case, the behaviour of the Bonus feature should not be applied for users that their plane is taking‐off otherwise the connection cannot be interrupted. This phenomenon is known in AO as aspects on aspects [49] and is defined by the ability to execute advice of one aspect when the advice of another aspect is executed. In other words, one aspect can also be woven to other aspects; this is also called advising advices or foreign advising in [50].…”

Section: Acsd Approaches: Domain Analysismentioning

confidence: 99%

See 1 more Smart Citation

Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

Hannousse

2019

IET softw.

View full text Add to dashboard Cite

Coping with crosscutting and dynamic features of software systems has significant impacts on software modularity, reusability, adaptability, and maintainability. However, dealing with such features is a tremendous challenge for different software paradigms, particularly component-based software development (CBSD) where components can be used as black box software units. Fortunately, dealing with crosscutting features is the main focus of aspect-orientation (AO). To compromise, a plethora of different AO and CBSD combinations are available. There is, however, little consensus on how AO and CBSD can be combined and what AO qualities need to be integrated for getting maximum benefits from the combination. In the aim to reach a consensus and increase the understanding of requirements for proper combinations that deal with crosscutting and dynamic features, the authors conduct a domain analysis study of existing combination endeavours; they first identify a set of requirements ought to be fulfilled for proper modelling of crosscutting and dynamic features in component software using AO; second, they group the identified requirements into an evaluation model; third, they check the capability of existing combinations to validate the evaluation model. The study highlighted mandatory requirements for proper combinations and revealed that none of the existing endeavours validates the evaluation model.

show abstract

Section: Support For Aspect Interaction Managementmentioning

confidence: 99%

Section: Acsd Approaches: Domain Analysismentioning

confidence: 99%

Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

Hannousse

2019

IET softw.

View full text Add to dashboard Cite

show abstract

“…The Java Aspect Metamodel Interpreter (JAMI) [HBA08] defines a meta-model, not unlike LIAM, to capture the semantics of features in aspect-oriented languages. But unlike LIAM, JAMI is tied to a specific execution strategy: interpretation.…”

Section: Runtime Mops For Dispatchingmentioning

confidence: 99%

An In-Depth Look at ALIA4J.

Bockisch¹,

Sewe²,

Yin³

et al. 2012

JOT

Self Cite

View full text Add to dashboard Cite

New programming languages supporting advanced modularization mechanisms are often implemented as transformations to the imperative intermediate representation of an already established language. But while their core constructs largely overlap in semantics, re-using the corresponding transformations requires re-using their syntax as well; this is limiting. In the ALIA4J approach, we identified dispatching as fundamental to most modularization mechanisms and provide a meta-model of dispatching as a rich, extensible intermediate language. Based on this meta-model, one can modularly implement the semantics of dispatchingrelated constructs. From said constructs a single execution model can then be derived which facilitates interpretation, bytecode generation, and even optimized machine-code generation. We show the suitability of our approach by mapping five popular languages to this meta-model and find that most of their constructs are shared across multiple languages. We furthermore present implementations of the three different execution strategies together with a generic visual debugger available to any ALIA4J-based language implementation. Intertwined with this paper is a tutorial-style running example that illustrates our approach.

show abstract

“…In this section, we propose our core composition model. This model can be seen as a generalization of prior work, related to the modeling and composition of (domain-specific) aspect languages [36]. It consists of a set of key concepts that work together to model composition operators.…”

Section: The Composition Modelmentioning

confidence: 99%

“…The Co-op/I language as well as the examples discussed in this paper, are implemented and available for download [3]. The current prototype is implemented on top of the Java Aspect Metamodel Interpreter (JAMI), which was presented in prior work [36].…”

Section: Implementation Of Co-op/imentioning

confidence: 99%

First-Class Compositions

Bergmans

Havinga

Akşit

2012

Transactions on Aspect-Oriented Software Development IX

Self Cite

View full text Add to dashboard Cite

A considerable amount of research, especially within the OO and AOSD communities, has focused on understanding the potential and limitations of various composition techniques. This has led to a large number of proposals for alternative composition techniques, including many variations of message dispatch, inheritance, and aspect mechanisms. This paper makes the case that there is no single perfect composition technique that suits every situation, since different techniques incur different trade-offs. The proper composition technique to use depends on the particular design problem and its requirements (such as the required adaptability, reusability, understandability and robustness). However, most programming languages limit the available composition techniques to a very few. To address this, we propose a novel composition model, called Co-op. The model provides dedicated abstractions that can be used to express a wide variety of object composition techniques ("composition operators"). Examples include various forms of inheritance, delegation, and aspects. The proposed model unifies objects (with encapsulated state and a message interface) and composition operators; composition operators are specified as first-class citizens. Multiple composition operators can be combined within the same application, and composition operators can even be used to compose new composition operators from existing ones. This opens new possibilities for developing domain-specific composition operators, taxonomies of composition operators, and for reuse and refinement of composition operators. To validate and experiment with the proposed model, we have designed and implemented a simple language, Co-op/I, that we also use in this paper to show concrete examples.

show abstract

Prototyping and Composing Aspect Languages

Cited by 15 publications

References 13 publications

Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

An In-Depth Look at ALIA4J.

First-Class Compositions

Contact Info

Product

Resources

About