RefactorIT

Refactoring starts with research, probing and understanding of an existing source base. This is particularly true when working with team-developed code, but it also applies when a developer comes back to a module that they haven't worked on in several months. The goal is to expose the functional hierarchy of methods and program elements.

The next phase involves isolating variables, methods, and classes which need to be moved, reorganized, or transformed. The code fragments are moved and merged into their new locations. Variables, file names, and other references must be globally converted or changed to maintain code integrity. The code of both the unchanged and modified files must be massaged and made ready to compile.

Almost immediately, a unit-testing phase must be done to make sure that the code migration has not hurt functionality. Quick refactoring-testing cycles facilitate incremental improvement and risk reduction.

Finally, code metrics are checked to detect unused methods, overloaded operators, code "hot spots", and other problem areas.

• RefactorIT Personal Edition: elementary refactorings, including e-mail support and bugfix updates.
• RefactorIT Developer Edition: full-set of automatic refactorings, analysis tools, metrics and audits and including e-mail support and bugfix updates.
• RefactorIT Enterprise Edition: full-set of automatic refactorings, analysis tools, metrics, audits command line interface (CLI) and Ant integration and including e-mail support and bugfix updates.