Model Refactoring Operations Based-on Class Diagram And Procedure Blueprint

The requirement of software changes constantly. For the software which has already been developed, when the clients change their demands or when its environment changes, it must be modified. In fact, programming is not the most difficult thing, however, the maintenance cost always occupies more than 60 percent of the total cost, and to maintain software is both boring and time-consuming. To solve that problem, scholars came up with the concept of refactoring in Object-Oriented field, and a lot of research has been carried out.At the beginning, refactoring research was mainly based on source code. Nevertheless, Researchers came to know that there were many shortages about refactorings based on source code, and the efficiency was also very low. As a result, they turned to carry out refactorings on high levels, for example design patterns, class diagrams, etc. Although the efficiency of refactorings based on such high levels is very high, there are methods in every class, and the arithmetic is implemented inside methods. For a given class, the most important part is arithmetic. In that condition, if we could combine refactorings based on high levels and methods, the effect of refactorings will be more obvious.The refactorings based on procedure blueprint is a kind of method refactorings, furthermore, its abstract implementation structure diagram contains the same semantic with source code. In this article, we combine the refactorings based on class diagram and procedure blueprint, high level refactorings are carried on class diagrams while method refactorings are carried out on procedure blueprint. The object of this essay is the refactoring operations based on class diagram and procedure blueprint, and these new operations establish the base of the implementation of automatic refactoring tools.