Scheduling of conflicting refactorings to promote quality improvement

ABSTRACT

Software refactoring is to restructure object-oriented software to improve its quality, especially extensibility, reusability and maintainability while preserving its external behaviors. For a special software system, there are usually quite a few refactorings available at the same time. But these refactorings may conflict with each other. In other words, carrying out a refactoring may disable other refactorings. Consequently, only a subset of the available refactorings can be applied together, and which refactorings will be applied depends on the schedule (application order) of the refactorings. Furthermore, carrying out different subsets of the refactorings usually leads to different improvement of software quality. As a result, in order to promote the improvement of software quality, refactorings should be scheduled rationally. However, how to schedule refactorings is rarely discussed. Usually, software engineers carry out refactorings immediately when they are found out. They do not wait until all applicable refactorings are found out and scheduled. In other words, the refactorings are not scheduled explicitly, and conflicts among them are not taken into consideration. Though more and more refactorings are formalized and automated by refactoring tools, refactoring tools apply refactorings usually in a nondeterministic fashion (in random). In this paper, we propose a scheduling approach to schedule conflicting refactorings to promote the improvement of software quality achieved by refactorings. Conflicts among refactorings are detected, and then a scheduling model is presented. And then a heuristic algorithm is proposed to solve the scheduling model. Results of experiments suggest that the proposed scheduling approach is effective in promoting the improvement of software quality

REFERENCES

• 1: Salah Bouktif , Giuliano Antoniol , Ettore Merlo , Markus Neteler, A novel approach to optimize clone refactoring activity, Proceedings of the 8th annual conference on Genetic and evolutionary computation, July 08-12, 2006, Seattle, Washington, USA [doi>10.1145/1143997.1144312]
• 2: Refactoring: improving the design of existing code, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 3: T. Mens. On the use of graph transformations for model refactoring. Slides of a tutorial at the Summer School on Generative and Transformational Techniques in Software Engineering, 2005.
• 4: Tom Mens , Niels Van Eetvelde , Serge Demeyer , Dirk Janssens, Formalizing refactorings with graph transformations: Research Articles, Journal of Software Maintenance and Evolution: Research and Practice, v.17 n.4, p.247-276, July 2005 [doi>10.1002/smr.v17:4]
• 5: T. Mens, G. Taentzer, and O. Runge. Detecting structural refactoring conflicts using critical pair analysis. Electronic Notes in Theoretical Computer Science, 127(3):113--128, April 2005.
• 6: Tom Mens , Tom Tourwé, A Survey of Software Refactoring, IEEE Transactions on Software Engineering, v.30 n.2, p.126-139, February 2004 [doi>10.1109/TSE.2004.1265817]
• 7: William F. Opdyke, Refactoring object-oriented frameworks, University of Illinois at Urbana-Champaign, Champaign, IL, 1992
• 8: J. U. Pipka. Refactoring in a 'test first'-world. In M. Marchesi and G. Succi, editors, Third International Conference on eXtreme Programming and Flexible Processes in Software Engineering, pages 178--181, 2002.
• 9: Don Roberts , John Brant , Ralph Johnson, A refactoring tool for Smalltalk, Theory and Practice of Object Systems, v.3 n.4, p.253-263, 1997 [doi>10.1002/(SICI)1096-9942(1997)3:4<253::AID-TAPO3>3.3.CO;2-I]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.7 Distribution, Maintenance, and Enhancement

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques

General Terms:
Algorithms, Design

Keywords:
conflict, quality, schedule, software refactoring