Refactoring for Software Design Smells: Managing Technical Debt

Refactoring for Software Design Smells: Managing Technical Debt cover

Download Refactoring for Software Design Smells: Managing Technical Debt PDF EPUB


Author: Author

Pages: 258

Size: 781,74 Kb

Publication Date: November 17,2014

Category: Testing



Download PDF  Download EPUB


Awareness of style smells – indicators of common design problems – helps programmers or software program engineers understand errors made while developing, what design concepts were overlooked or misapplied, and what principles have to be applied properly to handle those smells through refactoring.
  • Contains a thorough catalog of 25 structural style smells (arranged around four fundamental style principles) that donate to technical financial debt in software tasks
  • Presents a distinctive naming scheme for smells that assists understand the reason for a smell along with factors toward its potential refactoring
  • Includes illustrative good examples that showcase the indegent design procedures underlying a smell and the issues that result
  • Addresses pragmatic approaches for refactoring style smells to control technical debt also to create and keep maintaining high-quality software used
  • Presents insightful anecdotes and case research drawn from the trenches of real-world tasks
These smells have a tendency to contribute greatly to technical debt – additional time owed to repair projects regarded as complete – and have to be resolved via appropriate refactoring.

Refactoring for Software Style Smells presents 25 structural style smells, their function in identifying design problems, and potential refactoring solutions. On the way they recount anecdotes from real projects which the relevant smell helped address a style concern. The authors distill their study and knowledge as consultants and trainers, providing insights which have been used to boost refactoring and decrease the period and costs of controlling software tasks. Organized across common regions of software style, each smell is offered diagrams and good examples illustrating the indegent design methods and the issues that result, creating a catalog of nuggets of easily usable information that programmers or engineers can apply within their projects. Designers and software program engineers may “know” concepts and patterns, but have no idea of the “smells” which exist in their style due to wrong or mis-program of concepts or patterns.


See also