An aspect-oriented design model consists of a set of aspect models and a primary model. Each of these models consists of a number of different kinds of UML diagrams. The models must be composed to identify conflicts and analyze the system as a whole. We have developed a systematic approach for composing class diagrams in which a default composition procedure based on name matching can be custom...

Aspect-orientation has been capturing researcher’s attention for the last few years. We have seen the birth of several aspect-oriented programming techniques and also the propagation of the aspect concept to the earlier stages of the software development process, such as requirements analysis and design. Our long-term goal is to extend aspect-orientation to the business modelling activity. This...

This paper discusses the representation and implementation of the Observer design pattern using aspect-oriented techniques.

Object oriented software measurement has been given a foundational, theoretical basis by the research of Chidamber and Kemerer, partly based on Wand and Weber’s interpretation of the ontology of Bunge. Aspect oriented software development lacks such a sound theoretical basis, with the result that there is some confusion over what constitutes an aspect and how best to measure and assess the prop...

Code and model generators that are employed in modeldriven engineering usually face challenges caused by complexity and tight coupling of generator implementations, particularly when multiple metamodels are involved. As a consequence maintenance, evolution and reuse of generators is expensive and error-prone. We address these challenges with a two fold approach for generator composition, called...

The often crosscutting characteristics of feature implementations make effective variability management a predominant engineering challenge in software product line engineering. Features can often hardly be modularized but are spread over several other modules. In this paper we propose XWeave, an approach that facilitates variability implementation, management, and tracing by using aspects to m...

This position paper investigates the possibilities of separation, modularization and reuse offered by aspect-orientation, concentrating not on the technical or syntactic problems, but on the inherent issues resulting from interaspect dependencies. An aspect is defined based on the services it provides, on the services it requires and on the services it removes from other aspects. A classificati...

The aspect-oriented programming approach claims to make it easier to reason about, develop, and maintain certain kinds of application code while maintaining highly e cient code. To better understand the usefulness and usability of the aspect-oriented approach, we have been conducting a series of experiments. These experiments are designed to investigate such characteristics of aspect-oriented d...

The different software modules (e.g., components) that constitute a system are not isolated entities. In fact, they need to interact according to a certain coordination protocol in order to achieve a common goal. This coordination protocol crosscuts the different software modules, hindering their reusability, independence, maintenance and evolution, but these drawbacks can be solved by separati...

These variability concerns affect both the service interface and the service provider implementation and hence are crosscutting in nature. In this paper, we use principles of aspect-oriented software development to modularize these variability concerns. We also provide an aspect specification scheme to specify these concerns. We propose an approach to create heavyweight service variants centere...