Web services dramatically increase the reach of ebusiness. A homogeneous model that spans internal as well as external resources enables uniform solutions to complex business problems. Yet, the complexity of webservice-based systems increases exponentially with their scope. Separation of crosscutting concerns and active management of aspects are fundamental in web-servicebased solutions. In thi...

AOSD a recency domain in software development, which can be used to seek new modularization feature. aim to address crosscutting concerns by probiding means for their systematic identification, separetion, representation and composition [23] .

Traditionally, in software engineering, development happens for single products. This is a very inefficient approach in cases where groups of products are related. Software product line engineering [1] is about systematically developing families of related products together, as a product line. The products within a product line usually have many things in common, but also significant difference...

Virtual machine implementations are made up of intricately intertwined subsystems, coordinating largely through implicit dependencies. An analysis of several virtual machine implementations reveals the presence of crosscutting concerns—concerns that cannot be modularized through traditional means and whose implementation is scattered over and tangled with the source code of other modules. This ...

Runtime verification (RV) facilitates detecting the failures of software during its execution. Due to the complexity of RV techniques, there is an increasing interest in achieving abstractness, modularity, and compose-ability in their implementations by means of dedicated linguistic mechanisms. This paper defines a design space to evaluate the existing domain-specific languages for implementing...

The i* framework is a very popular approach in the Requirements Engineering community. However, crosscutting concerns are not handled explicitly in i*, compromising the modularity and consequently the complexity and evolution of such models. To deal with the complexity of i* models, the use of structuring mechanisms has been investigated. Moreover, the i* framework has been extended to incorpor...

Mechanisms in AOP (aspect-oriented programming) can be characterized by a JPM (join point model). AOP is effective in unanticipated software evolution because crosscutting concerns can be added or removed without making invasive modifications on original programs. However, the effectiveness would be restricted if new crosscutting concerns cannot be described with existing JPMs. Mechanisms for e...

We present an approach towards automatic component assembly based on aspect-oriented generative domain modeling. It involves the lifecycle covering the component specification generation, and subsequent assembly of implementation components to produce the final software system. Aspect-oriented techniques are applied to capture the crosscutting concerns that emerge during the assembly process. S...

In this paper we reflect upon the results of experiments that have attempted to use Metaobject Protocols to implement security as a crosscutting concern. As security is often cited as a crosscutting concern that could be implemented using Aspects we would like to point the way to some of the requirements that should be met by any aspect language used to implement security as a crosscutting conc...

Traditional protocol implementation approaches capture the structural aspects of protocols in a common base that can be used across layers. However, they are usually not very good at capturing the behavioral aspects. Two important implementation problems result, namely, reprogramming similar behavior and configuration of crosscutting concerns. In this paper, we present an approach to solve the ...