Zurück zur Startseite
|Eingestellt in Kategorie:

Bild 1 von 1

Refactoring: Verbesserung des Designs bestehenden Codes - Bild 1 von 1
Ähnlichen Artikel verkaufen?
Selbst verkaufen

Refactoring: Verbesserung des Designs bestehenden Codes

by Fowler, Martin; Beck, Kent; Brant, John | HC | Good
ThriftBooks
(3933506)
Angemeldet als gewerblicher Verkäufer
Mehr Artikel des Verkäufers
Verkäufer kontaktieren
US $5,94
Ca.CHF 4,71
Artikelzustand:
Gut
“Missing dust jacket; Pages can have notes/highlighting. Spine may show signs of wear. ~ ”... Mehr erfahrenÜber den Artikelzustand
Ganz entspannt. Kostenloser Versand & Rückversand.
Versand:
Kostenlos Economy Shipping.
Standort: Aurora, Illinois, USA
Lieferung:
Lieferung zwischen Mo, 28. Jul und Fr, 1. Aug nach 94104 bei heutigem Zahlungseingang
Liefertermine - wird in neuem Fenster oder Tab geöffnet berücksichtigen die Bearbeitungszeit des Verkäufers, die PLZ des Artikelstandorts und des Zielorts sowie den Annahmezeitpunkt und sind abhängig vom gewählten Versandservice und dem ZahlungseingangZahlungseingang - wird ein neuem Fenster oder Tab geöffnet. Insbesondere während saisonaler Spitzenzeiten können die Lieferzeiten abweichen.
Rücknahme:
30 Tage Rückgabe. Verkäufer zahlt Rückversand.
Zahlungen:
     Diners Club

Sicher einkaufen

eBay-Käuferschutz
Geld zurück, wenn etwas mit diesem Artikel nicht stimmt. Mehr erfahreneBay-Käuferschutz - wird in neuem Fenster oder Tab geöffnet
Der Verkäufer ist für dieses Angebot verantwortlich.
eBay-Artikelnr.:146043714021
Zuletzt aktualisiert am 24. Mai. 2025 09:16:52 MESZAlle Änderungen ansehenAlle Änderungen ansehen

Artikelmerkmale

Artikelzustand
Gut
Buch, das gelesen wurde, sich aber in einem guten Zustand befindet. Der Einband weist nur sehr geringfügige Beschädigungen auf, wie z.B. kleinere Schrammen, er hat aber weder Löcher, noch ist er eingerissen. Bei gebundenen Büchern ist der Schutzumschlag möglicherweise nicht mehr vorhanden. Die Bindung weist geringfügige Gebrauchsspuren auf. Die Mehrzahl der Seiten ist unbeschädigt, das heißt, es gibt kaum Knitter oder Einrisse, es wurden nur in geringem Maße Bleistiftunterstreichungen im Text vorgenommen, es gibt keine Textmarkierungen und die Randbereiche sind nicht beschrieben. Alle Seiten sind vollständig vorhanden. Genauere Einzelheiten sowie eine Beschreibung eventueller Mängel entnehmen Sie bitte dem Angebot des Verkäufers. Alle Zustandsdefinitionen ansehenwird in neuem Fenster oder Tab geöffnet
Hinweise des Verkäufers
“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

Über dieses Produkt

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

Artikelbeschreibung des Verkäufers

Info zu diesem Verkäufer

ThriftBooks

98,9% positive Bewertungen•19.7 Mio. Artikel verkauft

Mitglied seit Mär 2015
Angemeldet als gewerblicher Verkäufer
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 ...
Mehr anzeigen
Shop besuchenKontakt

Detaillierte Verkäuferbewertungen

Durchschnitt in den letzten 12 Monaten
Genaue Beschreibung
4.9
Angemessene Versandkosten
5.0
Lieferzeit
5.0
Kommunikation
4.9

Verkäuferbewertungen (5'686'913)

Alle Bewertungen
Positiv
Neutral
Negativ
Alle Bewertungen ansehen

Noch mehr entdecken: