To sum things up, AOP has the potential to change the way in which applications are developed, but it also introduces developers and project managers to a new tangle of issues surrounding application behavior. Also, it should be clear now that AOP is not a successor to OOP, but a new way of looking at object functionality: allowing the behavior of an object to be modularized and used across other componentswithout creating complex class hierarchies, but instead creating complex webs of AOP configuration. AOP is nothing new, but is now facing the heat and the attention of developers everywhere. Will it revolutionize software development as OOP did in the 1980s? Possibly, but, also like OOP, it'll take a long time to catch on.