Abstract

This chapter discusses how Aspect-Oriented Programming (AOP) can be used to increase productivity. The key difference between Object-Oriented Programming (OOP) and AOP is in the allocation of power to change and augment the behavior of a code. With an AOP solution, the power to extend the code lies with the user. An end user can change the behavior of someone else's code without writing any new classes and asking for permission from the original designer. As a user of code, one has the flexibility to mold a code to fit the verification environment. As a writer of code, one can relax and stop worrying about adding enough functionality or not having written everything correctly. AOP permits the user to stay focused on getting the verification environment in order to work and find bugs on a project. This shift in power and control from the writer to the user shows that there are a number of potential blocking points and time-wasting situations that disappear with the use of AOP. Productivity is further improved with the use of AOP over OOP because for certain tasks, AOP requires less language overhead, allows addition of problem-specific functionality, defers class complexity, and handles workarounds.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.