This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Quality Time
November/December 2003 (vol. 20 no. 6)
pp. 90-93
ASCII Text
x 
 
Ramnivas Laddad, Roger Alexander, "Quality Time," IEEE Software, vol. 20, no. 6, pp. 90-93, November/December, 2003.
 
 
BibTex
x
 
@article{ 10.1109/MS.2003.1241372,
author = {Ramnivas Laddad and Roger Alexander},
title = {Quality Time},
journal ={IEEE Software},
volume = {20},
number = {6},
issn = {0740-7459},
year = {2003},
pages = {90-93},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2003.1241372},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Quality Time
IS - 6
SN - 0740-7459
SP90
EP93
EPD - 90-93
A1 - Ramnivas Laddad,
A1 - Roger Alexander,
PY - 2003
VL - 20
JA - IEEE Software
ER -
 

Aspect-Oriented Programming Will Improve Quality, Ramnivas Laddad

Software engineers arealways looking for ways to improve modularity in software. Recently, aspect-oriented programming emerged as a new modularity technique that aims to cleanly separatethe implementation of crosscutting concerns(requirements and design elements that affect multiple modules). Several characteristics of AOP work together to improve software quality.

Aspect-Oriented Programming: the Real Costs?, Roger Alexander

The essence of aspect-oriented programming is that crosscutting concerns are factored into distinct abstractions (that is, aspects) that are solely responsible for a particular crosscutting concern. This raises the system?s modularity and increases cohesion of the abstractions that are primary concerns. We must understand and address AOP's significant weaknesses before we can realize its benefits.

Citation:
Ramnivas Laddad, Roger Alexander, "Quality Time," IEEE Software, vol. 20, no. 6, pp. 90-93, Nov.-Dec. 2003, doi:10.1109/MS.2003.1241372
Usage of this product signifies your acceptance of the Terms of Use.