The term “crosscutting concern” describes a piece of system that cannot be cleanly modularized because of the limited abstractions offered by the traditional programming paradigms. Symptoms of implementing crosscutting concerns in the languages like C, C# or Java are “code scattering” and “code tangling” that both degrade software modularity. Aspect-oriented programming (AOP) was proposed as a ...

A number of concerns in Multiagent Systems (MAS) have a broadly-scoped impact on the system architectural decomposition, which in turn hinder the design of modular MAS architectures. Typical examples of crosscutting concerns in MAS architectures include learning, mobility, coordination, and autonomy. Nowadays there are some architectural proposals that envisage an emerging aspect-oriented archi...

Aspect Oriented Programming (AOP) is a new programming paradigm that offers a novel modularization unit for the crosscutting concerns. Functionalities originally spread across several modules and tangled with each other can be factored out into a single, separate unit, called an aspect. We investigated automated techniques that can be used to support the migration of existing Object Oriented Pr...

Crosscutting is usually described in terms of scattering and tangling. However, the distinction between these three concepts is vague. Precise definitions are mandatory for certain research areas such as the identification of crosscutting concerns at phases of the software life cycle. We propose a conceptual framework for crosscutting where crosscutting is defined in terms of trace relations. T...

The Communications-based train control(CBTC) system has gradually become the first choice for signal systems of urban mass transit. However, how to guarantee its safety has become a research hotspot in safety fields. The generic test system with high efficiency has become the main means to verify the function and performance of CBTC system. This paper discusses a composable modeling method for ...

The goal of aspect-oriented programming is to modularize crosscutting concerns (or aspects) at the code level. These aspects can be defined in either a general-purpose language or in a language that is fine-tuned to a specific aspect in consideration. Aspect-specific languages provide more concise and more readable aspect declarations but are limited to a specific domain. Moreover, multiple asp...

Aspect orientation is important not only at the programming-level but also at the modeling-level. We previously proposed an aspect-oriented modeling language called AspectM for managing modeling-level aspects. Although AspectM provides basic modeling facilities for a modeler, the language constructs cannot be extended. In this paper, we propose a mechanism called metamodel access protocol (MMAP...

Features are increments in program functionality and are the building blocks of product lines. Typical implementation of features using Object Oriented techniques commonly crosscuts several classes and interfaces. There exist many techniques that implement crosscuts, of which Aspect Oriented ones distinguish themselves by their support of dynamic crosscuts expressed with advice. Despite being a...

CrossMDA is a framework that encompasses a transformation process to integrate crosscutting concerns in model-oriented systems. Such integration is accomplished by combining the capacities of separation of concerns currently existent in MDA and AOP approaches. CrossMDA uses the concepts of horizontal separation of concerns from AOP to create independent business and aspect models, integrating t...

Advanced techniques in separation of concerns such as AspectOriented Programming, help to develop more maintainable and more efficient applications by providing means for modularizing crosscutting concerns. However, conflicts may appear when several concerns need to be composed for the same application, especially when dealing with around advice. We call this problem the Aspect Composition Issu...