Evolution of legacy system comprehensibility through automated refactoring

Abstract

Software engineering is a continually evolving discipline, wherein researchers and members of industry are working towards defining and refining what are known as "best practices." Best practices are the set of known correct engineering techniques that lead to quality software.When a software artifact is produced, it becomes temporally locked into a single instantiation of these best practices at a given point in time. If such software is not maintained in such a way as to keep it current with the evolution of practice, then there is a good chance that subsequent engineers may not understand the design choices made. There are known techniques, called refactorings, which allow for structural changes to software without altering the outward appearance and behavior, thus maintaining the intent of the original design. Unfortunately, refactoring requires an engineer to both understand the techniques to be applied and the code to which they are applied to. This is not always feasible.We have developed an automated system utilizing Evolutionary Algorithms to manipulate refactorings correctly without requiring an underlying understanding of the software. This then allows for sustained levels of quality of evolving software systems. The understandability, maintainability, and reusability of the software regenerate as best practices evolve.

GA-driven Automatic Refactoring based on Design Patterns

“…It applies some transformations to programs such as extracting interface for re-routing the access to a class via a newly created interface and pulling up members for moving members into a superclass. Griffith, et al [4] developed an automated system utilizing Evolutionary Algorithms to manipulate refactorings correctly without requiring an underlying understanding of the software.…”

On the Completeness of Composite Code Refactorings for Beneficial Smell Remova

“…Some studies [171,222] indicate that the notion of completeness can help one to reveal what refactorings are needed "to complete" a composite to achieve a specific structural goal. However, existing studies assume that composites often completely remove code smells even without empirical evidence [28,37,43,44]. On the other hand, other studies indicate that certain composites may be incomplete to eliminate code smells [43,47].…”