CITI has stopped operations in 2014, to co-launch NOVA LINCS THIS SITE IS NOT BEING UPDATED SINCE 2013
citi banner
  Home  \  External Talks & Seminars  \  External Talk Page Login  
banner bottom
File Top
Aspect Oriented RE with Scenarios
(Research Talk)

By: Ana Moreira, João Araújo

Requirements should be specified and structured in such a way that their inherent changes must be coped with efficiently. However, requirements that cut across other requirements may result in tangled representations. Consequently, the reaction to requirements change is more difficult, since the impact of the change is more complicated to handle and more costly to rectify. Hence, it is necessary at the requirements stage to have both a means of modelling crosscutting concerns independently but also a means of composing crosscutting concerns (aspects) with other requirements in a way that will allow the entire set of requirements to be validated. In this tutorial, we consider aspects at the requirements level. In particular, we concentrate on scenario-based requirements. A scenario is an example trace of desired or existing system behavior. Scenarios are commonly used in requirements engineering because they are easily understood by all stakeholders. Among other applications, we can use scenario-based aspect-oriented requirements engineering to model volatile requirements. A rapidly changing market leads to software systems with highly volatile requirements. These must be managed in a way that reduces the time and costs associated with updating a system to meet these new requirements. By externalizing volatile concerns, we can build a stepping-stone for future management of unanticipated requirements change. The key insight is that aspect-oriented techniques can be applied to modularize volatility and to weave volatile concerns into the base software artefacts.

Date: 15 Oct 2007

Location/Event: Dehli, India/International Conference on Requirements Engineering

url: http://

File Bottom