ISBN:
9780133065251
,
0133065251
,
0201485672
,
9780201485677
,
9780133065268
,
013306526X
,
9780134757681
,
0134757688
,
0201485672
Language:
English
Pages:
xx1, 431 p.
,
ill. ;
,
25 cm
Series Statement:
The Addison-Wesley object technology series
Keywords:
Software refactoring
;
Object-oriented programming (Computer science)
;
Electronic books ; local
;
Object-oriented programming (Computer science)
;
Software refactoring
;
COMPUTERS ; Programming ; Object Oriented
;
Logiciels ; Refactorisation
;
Programmation orientée objet (Informatique)
Abstract:
As the application of object technology--particularly the Java programming language--has become commonplace, a new problem has emerged to confront the software development community. Significant numbers of poorly designed programs have been created by less-experienced developers, resulting in applications that are inefficient and hard to maintain and extend. Increasingly, software system professionals are discovering just how difficult it is to work with these inherited, "non-optimal" applications. For several years, expert-level object programmers have employed a growing collection of techniques to improve the structural integrity and performance of such existing software programs. Referred to as "refactoring," these practices have remained in the domain of experts because no attempt has been made to transcribe the lore into a form that all developers could use. . .until now. In Refactoring: Improving the Design of Existing Code, renowned object technology mentor Martin Fowler breaks new ground, demystifying these master practices and demonstrating how software practitioners can realize the significant benefits of this new process. With proper training a skilled system designer can take a bad design and rework it into well-designed, robust code. In this book, Martin Fowler shows you where opportunities for refactoring typically can be found, and how to go about reworking a bad design into a good one. Each refactoring step is simple--seemingly too simple to be worth doing. Refactoring may involve moving a field from one class to another, or pulling some code out of a method to turn it into its own method, or even pushing some code up or down a hierarchy. While these individual steps may seem elementary, the cumulative effect of such small changes can radically improve the design. Refactoring is a proven way to prevent software decay. In addition to discussing the various techniques of refactoring, the author provides a detailed catalog of more than seventy proven refactorings with helpful pointers that teach you when to apply them; step-by-step instructions for applying each refactoring; and an example illustrating how the refactoring works. The illustrative examples are written in Java, but the ideas are applicable to any object-oriented programming language.
Note:
Includes bibliographical references
Permalink
