cut across multiple components in a system.

AOSD makes it possible to modularize and separate these services and then apply them declaratively to the components and we can focus on our own specific concerns. For instance if we talk of spring framework, there aspects are wired into objects in the spring XML file in the same way as JavaBean does. This process is also known as ‘Weaving’.

 In a typical object-oriented development approach the developer might implement logging functionality by putting logger statements in all your methods and Java classes. In an AOP approach you would instead modularize the logging services and apply them declaratively to the components that required logging. The advantage, of course, is that the Java class doesn’t need to know about the existence of the logging service or concern itself with any related code. As a result, application code written with Spring AOP is loosely coupled. 

Lets do a comparison of OOP’s model with an AOP model, diagrammatically:

Here, the OOPs model shows that a source codeis directly compiled to an executable form. On the other hand, the AOP model depicts the flow such that the source code in the OOP model gets compiled with the aspects such that it modifies the behavior of the OOPs model and modularizes the crosscutting concerns.

Among the most OOPs languages, Java is a true Object-Oriented Programming language with a best support for AOP techniques. There are multiple tools available to support AOP with Java, few of them are shown below: