CSC/ECE 517 Fall 2009/wiki1a 9 mk: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Research in Refactoring Tools= | =Research in Refactoring Tools= | ||
==Introduction== | ==Introduction== | ||
Refactoring is the process of modifying existing source codebase in a structured and incremental | |||
way while preserving its external behavior. This process preserves the functionality of the program | |||
without introducing new bugs. Refactoring also promotes reuse of the existing codebase for other | |||
purposes thus increasing code reusability. | |||
==Fundamentals== | ==Fundamentals== | ||
==Current Automated Refactoring Tools== | ==Current Automated Refactoring Tools== | ||
===Features of some Refactoring Tools=== | ===Features of some Refactoring Tools=== | ||
====Java Refactoring Tool, Eclipse==== | ====Java Refactoring Tool, Eclipse==== | ||
| Line 13: | Line 26: | ||
====.NET Refactoring Tool, Visual Studio IDE==== | ====.NET Refactoring Tool, Visual Studio IDE==== | ||
==Academic Underpinning== | ==Academic Underpinning== | ||
==Improvement for Current Refactoring Tools== | ==Improvement for Current Refactoring Tools== | ||
==Conclusion== | ==Conclusion== | ||
==See Also== | ==See Also== | ||
==References== | ==References== | ||
Revision as of 19:13, 6 September 2009
Research in Refactoring Tools
Introduction
Refactoring is the process of modifying existing source codebase in a structured and incremental way while preserving its external behavior. This process preserves the functionality of the program without introducing new bugs. Refactoring also promotes reuse of the existing codebase for other purposes thus increasing code reusability.
Fundamentals
Current Automated Refactoring Tools
Features of some Refactoring Tools
Java Refactoring Tool, Eclipse
Ruby Refactoring Tool, Aptana
hi