Aspect Oriented Programming

Kiczales, Gregor; Hugunin, James; Hilsdale, Erik; Kersten, Mik; Palm, Jeff

doi:10.21236/ada417906

Cited by 480 publications

(640 citation statements)

References 5 publications

Supporting

Mentioning

634

Contrasting

Unclassified

Order By: Relevance

“…AspectJ [13,14]) exhibit the same sort of problems. In particular, AspectJ has become a complex language due to the fact that it tries to solve=work around these issues.…”

Section: Composing Implementation Blocksmentioning

confidence: 89%

See 1 more Smart Citation

First class feature abstractions for product derivation

et al. 2004

View full text Add to dashboard Cite

Abstract:The authors have observed that large software systems are increasingly defined in terms of the features they implement. Consequently, there is a need to express the commonalities and variability between products of a product family in terms of features. Unfortunately, technology support for the early aspect of a feature is currently limited to the requirements level. There is a need to extend this support to the design and implementation level as well. Existing separation of concerns technologies, such as AOP and SOP, may be of use here. However, features are not first class citizens in these paradigms. To address this and to explore the problems and issues with respect to features and feature composition, the authors have formalised the notion of features in a feature model. The feature model relates features to a component role model. Using our model and a composition algorithm, a number of base components and a number of features may be selected from a software product family and a product derived. As a proof of concept, the authors have experimented extensively with a prototype Java implementation of their approach.

show abstract

“…AspectJ [13,14]) exhibit the same sort of problems. In particular, AspectJ has become a complex language due to the fact that it tries to solve=work around these issues.…”

Section: Composing Implementation Blocksmentioning

confidence: 89%

“…Aspect oriented programming (AOP) [13] uses the concept of aspects to capture functionality that is crosscut in normal object decomposition. So-called join points provide hooks to merge aspects with the objects.…”

Section: Separation Of Concernsmentioning

confidence: 99%

First class feature abstractions for product derivation

et al. 2004

View full text Add to dashboard Cite

show abstract

“…vLevels offers a simple declarative language to define visible objects. We opted to separate the specification of visible objects from the program source code to avoid mixing the two different aspects of program logic and visibility, which is inspired by aspect oriented programming [6] in general, and Declarative Tracepoints [2] and LIS [14] in particular.…”

Section: Visible Objectsmentioning

confidence: 99%

Visibility Levels: Managing the Tradeoff between Visibility and Resource Consumption

Römer

2010

Real-World Wireless Sensor Networks

View full text Add to dashboard Cite

Abstract. Pre-deployment tests of sensor networks in indoor testbeds can only deliver a very approximate view of the correctness and performance of a deployed sensor network and it is therefore common that after deployment problems and failures occur that could not be observed during pre-deployment tests. Finding and fixing such problems requires visibility of the system state, such that an engineer can identify causes of misbehavior. Unfortunately, exposing the internal state of sensor nodes requires resources such as communication bandwidth and energy: the better visibility of system state is required, the more resources are needed to extract that state from the sensor network. In this paper we propose a concept and tool that give the user explicit control over this tradeoff. Essentially, the user can specify a resource budget and our tool strives to provide best possible visibility while not exceeding the resource budget. We present the design of our vLevels framework and report the results of a case study demonstrating that the overhead of our approach is small and that visibility is automatically adjusted to meet the specified resource budget.

show abstract

“…Dans ce travail de recherche, un outil assurant la gestion implicite de la mémoire au sein de C++ sera proposé et évalué. La programmation par aspects [Kicsales et al, 1997], incarnant la séparation des préoccupations [Tarr et al, 1999] {Separation of concerns en anglais) et formant un support méthodologique de modélisation et de programmation, sera utilisée à cet effet. Dans le code source d'une classe écrite avec un langage orienté objet comme C++ ou Java, plusieurs lignes sont consacrées à la synchronisation des accès aux ressources, à la sauvegarde des données (la persistance), au traitement des exceptions, à la vérification des paramètres entrants, etc.…”

Section: Ont Intégré Ununclassified

Gestion de cycle de vie des objets par aspects pour C++ /

Sioud¹

2006

View full text Add to dashboard Cite

Aspect Oriented Programming

Cited by 480 publications

References 5 publications

First class feature abstractions for product derivation

First class feature abstractions for product derivation

Visibility Levels: Managing the Tradeoff between Visibility and Resource Consumption

Gestion de cycle de vie des objets par aspects pour C++ /

Contact Info

Product

Resources

About