It is argued that such modularisation makes it possible to establish early trade-offs between aspectual requirements hence providing support for negotiation and subsequent decision-making among stakeholders.
A framework can be used to characterize software change support tools and to identify the factors that impact on the use of these tools and the ultimate goal is to provide a framework that positions concrete tools, formalisms and methods within the domain of software evolution.
This work builds on recent work that has emerged from the aspect-oriented programming community to propose a general model for aspect oriented requirements engineering (AORE), arguing that early separation of crosscutting functional and non-functional properties at the requirements level supports effective determination of their mapping and influence on artefacts at later development stages.
A quantitative case study that evolves a real-life application to assess various facets of design stability of OO and AO implementations and includes an analysis of the application in terms of modularity, change propagation, concern interaction, identification of ripple-effects and adherence to well-known design principles.
This paper identifies and specify crosscutting concerns in separate modules, so that localization and hence, reusability and maintainability can be promoted and the UMLbased aspect-oriented requirements engineering mechanism has a two-fold impact.
This article describes how to identify and capture early aspects in requirements and architecture activities and how they're carried over from one phase to another.
This paper proposes a uniform treatment of concerns at the requirements engineering level, regardless of their functional, non-functional or crosscutting nature, and introduces the notion of a compositional intersection, which allows us to choose appropriate sets of concerns in the authors' multi-dimensional separation as a basis to observe trade-offs among other concerns.
An exploratory study to investigate the suitability of information retrieval techniques for scalable identification of commonalities and variabilities in requirement specifications for software product lines and proposes an initial framework, leveraging IR to systematically abstract requirements from existing specifications of a given domain into a feature model.
This paper presents the design of a set of mutation operators for AspectJ-based programs that model instances of fault types identified in an extensive survey and discusses the generalisation of the fault types to AO approaches other than Aspect J and the coverage that may be achieved with the application of the proposed operators.
It is argued that frames and aspects when used in isolation cannot overcome weaknesses effectively and can be addressed by using the respective strengths of both technologies in combination: the amalgamation of framing and aspect-oriented techniques can help in the integration of new features and thus reduce the risk of architectural erosion.