Refactoring Workbook

個数：

Refactoring Workbook

  • 在庫がございません。海外の書籍取次会社を通じて出版社等からお取り寄せいたします。
    通常6～9週間ほどで発送の見込みですが、商品によってはさらに時間がかかることもございます。
    【重要ご説明事項】
    1. 納期遅延や、ご入手不能となる場合がございます。
    2. 複数冊ご注文の場合、分割発送となる場合がございます。
    3. 美品のご指定は承りかねます。
  • 【入荷遅延について】
    世界情勢の影響により、海外からお取り寄せとなる洋書・洋古書の入荷が、表示している標準的な納期よりも遅延する場合がございます。
    おそれいりますが、あらかじめご了承くださいますようお願い申し上げます。
  • ◆画像の表紙や帯等は実物とは異なる場合があります。
  • ◆ウェブストアでの洋書販売価格は、弊社店舗等での販売価格とは異なります。
    また、洋書販売価格は、ご注文確定時点での日本円価格となります。
    ご注文確定後に、同じ洋書の販売価格が変動しても、それは反映されません。
  • 製本 Paperback:紙装版/ペーパーバック版／ページ数 256 p.
  • 言語 ENG
  • 商品コード 9780321109293
  • DDC分類 005.16

Full Description

Refactoring has gained widespread acceptance in the software engineering community as a proven means of improving software. Martin Fowler's seminal book on this topic, Refactoring, 0201485672, has been used in the classroom to explain that existing code could be improved and enhanced without significantly altering the fundamental structure of an application. But many find that this concept has a steep learning curve that inhibits its use. In this new book, William Wake offers a more introductory look at this important topic. The author outlines a proven workbook approach to learning and applying refactoring to "everyday" projects. This approach relies on examples that force the student to apply the main concepts of refactoring. As a result, readers gain thorough knowledge of how refactoring can help improve their software.

Contents

Preface.


1. Roadmap.


Overview. Section 1: Smells within Classes. Section 2: Smells between Classes. Section 3: Programs to Refactor. A Word on the Challenges.

I. SMELLS WITHIN CLASSES.

2. The Refactoring Cycle.


What Is Refactoring? Smells Are Problems. The Refactoring Cycle. When Are We Done? Inside a Refactoring. Challenges. Conclusion.

3. Measured Smells.


Smells Covered. Comments. Long Method. Large Class. Long Parameter List. More Challenges. Conclusion.

Interlude 1. Smells and Refactorings.
4. Names.


Smells Covered. Type Embedded in Name (Including Hungarian). Uncommunicative Name. Inconsistent Names.

5. Unnecessary Complexity.


Smells Covered. Dead Code. Speculative Generality.

Interlude 2. Inverses.
6. Duplication.


Smells Covered. Magic Number. Duplicated Code. Alternative Classes with Different Interfaces. Challenges.

7. Conditional Logic.


Smells Covered. Null Check. Complicated Boolean Expression. Special Case. Simulated Inheritance (Switch Statement).

Interlude 3. Design Patterns.
II. SMELLS BETWEEN CLASSES.

8. Data.


Smells Covered. Primitive Obsession. Data Class. Data Clump. Temporary Field.

9. Inheritance.


Smells Covered. Refused Bequest. Inappropriate Intimacy (Subclass Form). Lazy Class.

10. Responsibility.


Smells Covered. Feature Envy. Inappropriate Intimacy (General Form). Message Chains. Middle Man. Challenges.

11. Accommodating Change.


Smells Covered. Divergent Change. Shotgun Surgery. Parallel Inheritance Hierarchies. Combinatorial Explosion.

12. Library Classes.


Smells Covered. Incomplete Library Class. Challenges.

Interlude 4. Gen-A-Refactoring.
III. PROGRAMS TO REFACTOR.

13. A Database Example.


Course.java (Online at www.xp123.com/rwb). Offering.java. Schedule.java. Report.java. TestSchedule.java. TestReport.java.

14. A Simple Game.


Development Episodes.

15. Catalog.


Introduction. Path 1: Catalog.itemsMatching(query). Path 2: Query.matchesIn(catalog). Path 3: Process(catalog.data, query.data). Conclusion.

16. Planning Game Simulator.


Part 1: Original Code. Part 2: Redistributing Features. Removing Duplication, Selection Troubles, and a Few Burrs. Part 3: Pushing the Code Further.

17. Where to Go from Here.


Books. Admonitions. Exercises to Try. Web Sites.

IV. APPENDIXES.

A: Answers to Selected Questions.
B: Java Refactoring Tools.
C: Inverses for Refactorings.
D: Key Refactorings.
Bibliography.
Index.