This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Discovering Early Aspects
January/February 2006 (vol. 23 no. 1)
pp. 61-70
Elisa Baniassad, Chinese University of Hong Kong
Paul C. Clements, Carnegie Mellon University
Joao Araújo, New University of Lisbon
Ana Moreira, New University of Lisbon
Awais Rashid, Lancaster University
Bedir Tekinerdogan, University of Twente
Traditionally, aspect-oriented software development (AOSD) has focused on the software life cycle's implementation phase: aspects are identified and captured mainly in code. But aspects are evident earlier in the life cycle, such as during requirements gathering and architecture development. Identifying these early aspects ensures that you can appropriately capture aspects related to the problem domain (as opposed to merely the implementation). Additionally, it offers opportunities for early recognition and negotiation of trade-offs and allows forward and backward aspect traceability. This makes requirements, architecture, and implementation more seamless and lets you apply aspects more systematically. Many techniques exist for dealing with early aspects in practice, but a holistic approach is lacking.

This article is an overview of how to exploit early aspects and charts aspects as they move from project inception to development.

Index Terms:
aspect orientation, requirements, architecture, design, life cycle
Citation:
Elisa Baniassad, Paul C. Clements, Joao Araújo, Ana Moreira, Awais Rashid, Bedir Tekinerdogan, "Discovering Early Aspects," IEEE Software, vol. 23, no. 1, pp. 61-70, Jan.-Feb. 2006, doi:10.1109/MS.2006.8
Usage of this product signifies your acceptance of the Terms of Use.