Awais Rashid

TL;DR: 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.

TL;DR: 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.

TL;DR: In this paper, the authors propose a general model for aspect oriented requirements engineering (AORE), which supports separation of crosscutting functional and non-functional properties at the requirements level, and argue that early separation of such crosscutting properties supports effective determination of their mapping and influence on artefacts at later development stages.

TL;DR: 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.

TL;DR: 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.