We propose a model to support aspect-oriented programming in object-oriented languages, expressing general purpose aspects. To apply this model, the developer should implement the abstraction and composition mechanisms as well as one or more strategies defined in it. It could be applied to regular OO languages.

In this paper, we present some of the problems we have found in distributed aspect models and introduce a set of criteria that we consider necessary for a robust distributed aspect system. We outline of a first version of model based on aspects and actors capable of meeting these criteria.

12

Simulation 4

In this paper we propose method families, i.e. equivalence classes of methods, together with operations to modify them as an important concept for the reusable definition of aspects. Usually different methods show the same behaviour seen under the perspective of an aspect. Hence it seems to be very natural to put additional structure on this interface between the basic functionality and the asp...

A spreadsheet usually starts as a simple and singleuser software artifact, but, as frequent as in other software systems, quickly evolves into a complex system developed by many actors. Often, different users work on different aspects of the same spreadsheet: while a secretary may be only involved in adding plain data to the spreadsheet, an accountant may define new business rules, while an eng...

Aspect-oriented systems claim to improve modularity by providing explicit mechanisms that allow modularization of concerns which crosscut the object-oriented decomposition of a system in terms of classes. However, by modularizing concerns which crosscut classes, at the same time the structure and functionality associated with the classes themselves becomes scattered across the implementation of...

Article history: Received 19 April 2012 Received in revised form 30 August 2013 Accepted 2 September 2013 Available online 16 September 2013