Research On Software Refactoring In AspectJ Programs

Recently, the Aspect-Oriented Programming (AOP) has been abroad concerned as the Object-Oriented Programming (OOP).Its main advantage is to offer a nicer modularization support and make the system easier to comprehending and maintenance. And the disadvantage of the OOP is that it can't resolve the problem of Crosscutting Concerns better. In the codes of OOP, which exist the phenomenon of codes decentralization and codes tangle because all of above. That will bring some disbennifit infection to the software maintenance. Compared with the OOP exemplification, the AOP exemplification offers the description of the Crosscutting Concerns mechanism and implements the modularization of Crosscutting Concerns, solving the problem of Crosscutting Concerns preferably. Besides, it is propitious to add new attention into the codes and then is propitious to the maintenance and expansion of programming. Based on the method of OOP, Crosscutting Concerns AOP offers a description of the Crosscutting Concerns mechanism to the developers. Under this mechanism, the Crosscutting Concerns is use the individual module called Aspect to describe, it allows the developer use the framework design and coding. This way can not only predigests the description(reducing the redundancy codes), but also get across the way of carving up the codes of Aspect Crosscutting Concerns, the developer can modify or insert or delete the system Aspect and even reuse the system Aspect. That improves the reusability and maintenance of the software. In the aspect of improving the configuration of programs, refactoring and the AOP can be used together. The final aim of them is able to improve the configuration of programs. The controlling way of them to the codes are similar that across the conversion of programs. The refactoring is crossing the conversion of the programs and the AOP mechanism is in virtue of mesh mechanism and the explainer; put the AOP coeds into OOP codes. But the two of them has different in the directness aim. The refactoring way is to show every changing of codes to the developer but the AOP makes the encapsulation of Crosscutting Concerns. If unchanging the behavior of the running programs then put the OOP codes into AOP codes under the AOP exemplification, it is called refactoring. There are different explanation in OOP and AOP refactoring. One of them is the whole program's conversion has been separated into two steps. The first step, put part of the basic programs into AOP mechanism, for example, the Aspect of AspectJ. The second step, putting up the interrelated conversion of this programs, such as AOP inter conversion. The other of the explanation is looking upon the basic programs into AOP codes. Every conversion steps are under the AOP exemplification and there's no rush in the transition of OOP to AOP. Above the last explanation, it is difficult to explain the occasion program preserving check. Because even thought it is a tiny modify can be a change of the program behaviour and it has no meaning to explain the occasion program preserving check to every program behaviour. Because the Aspect programs are composed of several parts, the inspection of it to the program is after its conformity. So, in the progress of describing its constitution, a whole Aspect program is founded on the...