Awareness of design smells – indicators of common design problems – helps developers or software engineers understand mistakes made while designing, what design principles were overlooked or misapplied, and what principles need to be applied properly to address those smells through refactoring. Developers and software engineers may "know" principles and patterns, but are not aware of the "smells" that exist in their design because of wrong or mis-application of principles or patterns. These smells tend to contribute heavily to technical debt – further time owed to fix projects thought to be complete – and need to be addressed via proper refactoring. Refactoring for Software Design Smells presents 25 structural design smells, their role in identifying design issues, and potential refactoring solutions. Organized across common areas of software design, each smell is presented with diagrams and examples illustrating the poor design practices and the problems that result, creating a catalog of nuggets of readily usable information that developers or engineers can apply in their projects. The authors distill their research and experience as consultants and trainers, providing insights that have been used to improve refactoring and reduce the time and costs of managing software projects. Along the way they recount anecdotes from actual projects on which the relevant smell helped address a design issue.

Contains a comprehensive catalog of 25 structural design smells (organized around four fundamental designprinciples) that contribute to technical debt in software projects
Presents a unique naming scheme for smells that helps understand the cause of a smell as well as pointstoward its potential refactoring
Includes illustrative examples that showcase the poor design practices underlying a smell and the problemsthat result
Covers pragmatic techniques for refactoring design smells to manage technical debt and to create and maintainhigh-quality software in practice
Presents insightful anecdotes and case studies drawn from the trenches of real-world projects

Frequently asked questions

Simply head over to the account section in settings and click on “Cancel Subscription” - it’s as simple as that. After you cancel, your membership will stay active for the remainder of the time you’ve paid for. Learn more here.

At the moment all of our mobile-responsive ePub books are available to download via the app. Most of our PDFs are also available to download and we're working on making the final remaining ones downloadable now. Learn more here.

Both plans give you full access to the library and all of Perlego’s features. The only differences are the price and subscription period: With the annual plan you’ll save around 30% compared to 12 months on the monthly plan.

We are an online textbook subscription service, where you can get access to an entire online library for less than the price of a single book per month. With over 1 million books across 1000+ topics, we’ve got you covered! Learn more here.

Look out for the read-aloud symbol on your next book to see if you can listen to it. The read-aloud tool reads text aloud for you, highlighting the text as it is being read. You can pause it, speed it up and slow it down. Learn more here.

Yes, you can access Refactoring for Software Design Smells by Girish Suryanarayana,Ganesh Samarthyam,Tushar Sharma in PDF and/or ePUB format, as well as other popular books in Computer Science & Programming Languages. We have over one million books available in our catalogue for you to explore.

Information

Publisher

Morgan Kaufmann

Year

2014

ISBN

9780128016466

Topic

Computer Science

Subtopic

Programming Languages

Index

Computer Science

Cover image
Title page
Table of Contents
Copyright
Dedication
Foreword by Grady Booch
Foreword by Dr. Stéphane Ducasse
Preface
Acknowledgments
Chapter 1. Technical Debt
Chapter 2. Design Smells
Chapter 3. Abstraction Smells
Chapter 4. Encapsulation Smells
Chapter 5. Modularization Smells
Chapter 6. Hierarchy Smells
Chapter 7. The Smell Ecosystem
Chapter 8. Repaying Technical Debt in Practice
Appendix A. Software Design Principles
Appendix B. Tools for Repaying Technical Debt
Appendix C. Notations for Figures
Appendix D. Suggested Reading
Bibliography
Index