Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

Abstract

Coping with crosscutting and dynamic features of software systems has significant impacts on software modularity, reusability, adaptability, and maintainability. However, dealing with such features is a tremendous challenge for different software paradigms, particularly component-based software development (CBSD) where components can be used as black box software units. Fortunately, dealing with crosscutting features is the main focus of aspect-orientation (AO). To compromise, a plethora of different AO and CBSD combinations are available. There is, however, little consensus on how AO and CBSD can be combined and what AO qualities need to be integrated for getting maximum benefits from the combination. In the aim to reach a consensus and increase the understanding of requirements for proper combinations that deal with crosscutting and dynamic features, the authors conduct a domain analysis study of existing combination endeavours; they first identify a set of requirements ought to be fulfilled for proper modelling of crosscutting and dynamic features in component software using AO; second, they group the identified requirements into an evaluation model; third, they check the capability of existing combinations to validate the evaluation model. The study highlighted mandatory requirements for proper combinations and revealed that none of the existing endeavours validates the evaluation model.

A Framework for Aspectual Requirements Validation: an Experimental Study

“…In addition, there are many approaches to identify aspects by use-case [14][15] [16]. Domain analysis of existing component and aspect approaches for crosscutting concerns is described in [39]. They identify a set of requirements to be fulfilled for modeling of dynamic and crosscutting features using aspect-oriented.…”