Conclusion

As we saw, the "traditional" programming paradigms (procedural programming, OOP) reach their limits when it's a question of integrating transverse functionalities in an application. They propose mechanisms making it possible to isolate these problems but none makes it possible to gather all the calls to these functionalities. The code is thus dispersed in all the application. The concepts of aspect, join point, crosscut and code advice issued from the AOP allow to address these problematics and thus to reduce even more the coupling.

However, AOP is a relatively recent concept, not having real experience feedbacks from the developers and is consequently only little employed in the big software projects. But its use tends to spread little by little.