Refactoring is the process of rewriting written material to improve its readability or structure, with the explicit purpose of keeping its meaning or behavior.
Refactoring code
In software engineering, the term refactoring is often used to describe modifying source code without changing its external behavior, and is sometimes informally referred to as "cleaning it up". Refactoring is often practiced as part of the software development cycle: developers alternate between adding new tests and functionality and refactoring the code to improve its internal consistency and clarity. Testing ensures that refactoring does not change the behavior of the code.
Refactoring is the part of code maintenance which doesn't fix bugs or add new functionality . Rather it is designed to improve the understandability of the code or change its structure and design, to make it easier for human maintenance in the future. In particular, adding new behavior to a program might be difficult with the program's given structure, so a developer might refactor it first to make it easy, and then add the new behavior.
The term is by analogy with the factorization of numbers and polynomials. For example, x2 − 1 can be factored as (x + 1)(x − 1), revealing an internal structure that was previously not visible (such as the two roots at +1 and -1). Similarly, in software refactoring, the change in visible structure can often reveal the "hidden" internal structure of the original code.
Refactoring is done as a separate step, to simplify testing. At the end of the refactoring, any change in behavior is clearly a bug and can be fixed separately from the problem of debugging the new behavior.
An example of a trivial refactoring is to change a variable name into something more meaningful, such as from a single letter 'i' to 'interestRate'. A more complex refactoring is to turn the code within an if block into a subroutine. An even more complex refactoring is to replace an if conditional with polymorphism. While "cleaning up" code has happened for decades, the key insight in refactoring is to intentionally "clean up" code separately from adding new functionality, using a known catalogue of common useful refactoring methods, and then separately testing the code (knowing that any behavioral changes indicate a bug). The new aspect is explicitly wanting to improve an existing design without altering its intent or behavior.
Refactoring is an important aspect of extreme programming.
Martin Fowler's book Refactoring is the classic reference. Although refactoring code has been done informally for years, William F. Opdyke 's 1993 PhD dissertation is the first known paper to specifically examine refactoring. All of these resources provide a catalog of common methods for refactoring ; a refactoring method has a description of how to apply the method and indicators for when you should (or should not) apply the method.
Refactoring is such an important concept that it has been identified as one of the most important software innovations by author and commentator David A. Wheeler.
Common refactorings
- Change Method Signature
- Convert Local Variable to Field
-
Encapsulate Field
- Extract Class
-
Extract Interface
- Extract Local Variable
- Extract Method (to turn part of a larger method into a new method. By breaking down code in smaller pieces, it is more easily understandable)
- Generalize Type
- Inline
- Introduce Factory
- Introduce Parameter
- Pull Up
- Push Down
- Rename Method (changing the name of a method into a new one that better reveals its purpose).
- Break down large functions - Functions that grow in use also grow in size. After a certain point, it becomes clear that functions can benefit from using functions themselves. Your eyes probe the function looking for a likely candidate to relocate elsewhere. This candidate is chosen for being the largest stretch of code that really has nothing to do with the enclosing function. This lets us easily think up a name that explains what the new function does without having to resort to something contrived just to distinguish it from the original function. (This section is originally from Perl Design Patterns Book).
Forth
The term 'factoring' has been used in the Forth community since at least the early 1980s. Chapter Six of Brodie's book "Thinking Forth" (1984) is dedicated to the subject.
In Forth, factoring has essentially the same meaning that refactoring does in extreme programming -- to break down a function (a 'word' in Forth) into smaller, more easily maintained functions.
Refactoring other text
The term refactoring originated in computer programming, but the concept has also been applied when modifying any text.
On Wiki websites, refactoring refers to the process of rewriting and reorganizing text to shorten it while preserving content. This particularly applies to discussions , which thus can be made accessible to people who are interested in the arguments made in the discussion, and the information to be gleaned from it, rather than the history of the discussion itself. Refactoring can be difficult to do in such a way that it makes all participants of a discussion happy.
Etymology
The first known use of the term "refactoring" in the published literature was in the article, Refactoring: An Aid in Designing Application Frameworks and Evolving Object-Oriented Systems, Proceedings of the Symposium on Object Oriented Programming Emphasizing Practical Applications (SOOPPA) September, 1990, ACM by William F. Opdyke and Ralph E. Johnson [1]. William Opdyke's Ph.D. thesis on "Refactoring Object-Oriented Framework", University of Illinois, was published in 1992 [2]. The term "refactoring" was almost certainly used before then. Refactoring as a technique was definitely used before then.
As a neologism, it is clearly a reference to mathematical factoring.
Bibliography
See also
External links
Last updated: 08-19-2005 14:21:48
