Retourner à la page d'accueil

Photo 1/1

Refactoring : Améliorer la conception du code existant - Photo 1/1
Vous en avez un à vendre ?
Vendez le vôtre

Refactoring : Améliorer la conception du code existant

by Fowler, Martin; Beck, Kent; Brant, John | HC | Good
ThriftBooks
(3944779)
Inscrit comme vendeur professionnel
Autres objets du vendeur
Contacter le vendeur
5,94 USD
Environ5,11 EUR
État :
Bon état
“Missing dust jacket; Pages can have notes/highlighting. Spine may show signs of wear. ~ ”... En savoir plusà propos de l'état
Pas d'inquiétude ! La livraison et les retours sont gratuits.
Livraison :
Gratuit Economy Shipping.
Lieu où se trouve l'objet : Aurora, Illinois, États-Unis
Délai de livraison :
Estimé entre le ven. 15 août et le mer. 20 août à 94104
Les dates de livraison estimées - la page s'ouvre dans une nouvelle fenêtre ou un nouvel onglet prennent en compte le délai d'expédition indiqué par le vendeur, le code postal de l'expéditeur, le code postal du destinataire et la date d'acceptation de l'offre. Elles dépendent du service de livraison sélectionné et de la date de réception du paiementréception du paiement - la page s'ouvre dans une nouvelle fenêtre ou un nouvel onglet. Les délais de livraison peuvent varier, notamment pendant les périodes de pointe.
Retours :
Retour sous 30 jours. Le vendeur paie les frais de retour.
Paiements :
     Diners Club

Achetez en toute confiance

Garantie client eBay
Obtenez un remboursement si vous ne recevez pas l'objet que vous avez commandé. En savoir plusGarantie client eBay - la page s'ouvre dans une nouvelle fenêtre ou un nouvel onglet
Le vendeur assume l'entière responsabilité de cette annonce.
Numéro de l'objet eBay :146043714021
Dernière mise à jour le 24 mai 2025 09:16:52 CEST. Afficher toutes les modificationsAfficher toutes les modifications

Caractéristiques de l'objet

État
Bon état
Livre ayant déjà été lu, mais qui est toujours en bon état. La couverture présente des dommages mineurs, comme des éraflures, mais n'est ni trouée ni déchirée. Pour les couvertures rigides, la jaquette n'est pas nécessairement incluse. La reliure présente des marques d'usure mineures. La majorité des pages sont intactes. Pliures et déchirures mineures. Soulignement de texte mineur au crayon. Aucun surlignement de texte. Aucune note dans les marges. Aucune page manquante. Consulter l'annonce du vendeur pour avoir plus de détails et voir la description des défauts. Afficher toutes les définitions des étatsla page s'ouvre dans une nouvelle fenêtre ou un nouvel onglet
Commentaires du vendeur
“Missing dust jacket; Pages can have notes/highlighting. Spine may show signs of wear. ~ ...
Binding
Hardcover
Book Title
Refactoring
Weight
2 lbs
Product Group
Book
IsTextBook
Yes
ISBN
9780201485677

À propos de ce produit

Product Identifiers

Publisher
Addison Wesley Professional
ISBN-10
0201485672
ISBN-13
9780201485677
eBay Product ID (ePID)
573331

Product Key Features

Number of Pages
464 Pages
Language
English
Publication Name
Refactoring : Improving the Design of Existing Code
Subject
General, Programming / Object Oriented
Publication Year
1999
Type
Textbook
Author
John Brant, Martin Fowler, William Opdyke, Kent Beck
Subject Area
Computers
Series
Addison-Wesley Object Technology Ser.
Format
Hardcover

Dimensions

Item Height
1.2 in
Item Weight
32 Oz
Item Length
9.2 in
Item Width
7.5 in

Additional Product Features

Intended Audience
Scholarly & Professional
LCCN
99-020765
Dewey Edition
23
Illustrated
Yes
Dewey Decimal
005.14
Table Of Content
1. Refactoring, a First Example. The Starting Point. The First Step in Refactoring. Decomposing and Redistributing the Statement Method. Replacing the Conditional Logic on Price Code with Polymorphism. Final Thoughts. 2. Principles in Refactoring. Defining Refactoring. Why Should You Refactor? When Should You Refactor? What Do I Tell My Manager? Problems with Refactoring. Refactoring and Design. Refactoring and Performance. Where Did Refactoring Come From? 3. Bad Smells in Code. Duplicated Code. Long Method. Large Class. Long Parameter List. Divergent Change. Shotgun Surgery. Feature Envy. Data Clumps. Primitive Obsession. Switch Statements. Parallel Inheritance Hierarchies. Lazy Class. Speculative Generality. Temporary Field. Message Chains. Middle Man. Inappropriate Intimacy. Alternative Classes with Different Interfaces. Incomplete Library Class. Data Class. Refused Bequest. Comments. 4. Building Tests. The Value of Self-testing Code. The JUnit Testing Framework. Adding More Tests. 5. Toward a Catalog of Refactorings. Format of the Refactorings. Finding References. How Mature Are These Refactorings? 6. Composing Methods. Extract Method. Inline Method. Inline Temp. Replace Temp with Query. Introduce Explaining Variable. Split Temporary Variable. Remove Assignments to Parameters. Replace Method with Method Object. Substitute Algorithm. 7. Moving Features Between Objects. Move Method. Move Field. Extract Class. Inline Class. Hide Delegate. Remove Middle Man. Introduce Foreign Method. Introduce Local Extension. 8. Organizing Data. Self Encapsulate Field. Replace Data Value with Object. Change Value to Reference. Change Reference to Value. Replace Array with Object. Duplicate Observed Data. Change Unidirectional Association to Bidirectional. Change Bidirectional Association to Unidirectional. Replace Magic Number with Symbolic Constant. Encapsulate Field. Encapsulate Collection. Replace Record with Data Class. Replace Type Code with Class. Replace Type Code with Subclasses. Replace Type Code with State/Strategy. Replace Subclass with Fields. 9. Simplifying Conditional Expressions. Decompose Conditional. Consolidate Conditional Expression. Consolidate Duplicate Conditional Fragments. Remove Control Flag. Replace Nested Conditional with Guard Clauses. Replace Conditional with Polymorphism. Introduce Null Object. Introduce Assertion. 10. Making Method Calls Simpler. Rename Method. Add Parameter. Remove Parameter. Separate Query from Modifier. Parameterize Method. Replace Parameter with Explicit Methods. Preserve Whole Object. Replace Parameter with Method. Introduce Parameter Object. Remove Setting Method. Hide Method. Replace Constructor with Factory Method. Encapsulate Downcast. Replace Error Code with Exception. Replace Exception with Test. 11. Dealing with Generalization. Pull Up Field. Pull Up Method. Pull Up Constructor Body. Push Down Method. Push Down Field. Extract Subclass. Extract Superclass. Extract Interface. Collapse Hierarchy. Form Template Method. Replace Inheritance with Delegation. Replace Delegation with Inheritance. 12. Big Refactorings. Tease Apart Inheritance. Convert Procedural Design to Objects. Separate Domain from Presentation. Extract Hierarchy. 13. Refactoring, Reuse, and Reality. A Reality Check. Why Are Developers Reluctant to Refactor Their Programs? A Reality Check (Revisited). Resources and References for Refactoring. Implications Regarding Software Reuse and Technology Transfer. A Final Note. References. 14. Refactoring Tools. Refactoring with a Tool. Technical Criteria for a Refactoring Tool. Practical Criteria for a Refactoring Tool. Wrap Up. 15. Putting It All Together. References. List of Soundbites. List of Refactorings. Index. 0201485672T04062001
Synopsis
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 Software, 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 designe, Refactoring is about improving the design of existing code. It is the process of changing a software system in such a way that it does not alter the external behavior of the code, yet improves its internal structure. With refactoring you can even take a bad design and rework it into a good one. This book offers a thorough discussion of the principles of refactoring, including where to spot opportunities for refactoring, and how to set up the required tests. There is also a catalog of more than 40 proven refactorings with details as to when and why to use the refactoring, step by step instructions for implementing it, and an example illustrating how it works The book is written using Java as its principle language, but the ideas are applicable to any OO language.
LC Classification Number
QA76.76.R42F69 1999

Description de l'objet fournie par le vendeur

Informations sur le vendeur professionnel

Je certifie que toutes mes activités de vente seront conformes à toutes les lois et réglementations de l'UE.
À propos de ce vendeur

ThriftBooks

98,9% d'évaluations positives•19,7 millions objets vendus

Membre depuis mars 2015
Inscrit comme vendeur professionnel
Just Voted on Newsweek - ThriftBooks ranks #1 America's Best Online Shops 2025 in Office, Electronics & Media sector, Media category!!ThriftBooks is a fully independent seller of used books, having ...
Plus
Visiter la BoutiqueContacter

Évaluations détaillées du vendeur

Moyenne pour les 12 derniers mois
Description exacte
4.9
Frais de livraison raisonnables
5.0
Livraison rapide
5.0
Communication
4.9

Évaluations du vendeur (5.703.075)

Toutes les évaluations
Positives
Neutres
Négatives
Afficher toutes les évaluations