Capers Jones conducted a study in 2012 across five large corporations and found that the number of software defects that can be traced back to errors in software design was as high as64%! Hence, ensuring a high quality of software design is critical for developing high-quality software. However, as Fred Brooks observes in his book “The Mythical Man Month”, software design is an inherently complex activity; the intangible nature of software makes it difficult for humans to envision, develop, and reason about its design. 

This talk proposes a unique approach towards developing high-quality software design. Borrowing a phrase from the healthcare domain “a good doctor is one who knows the medicines but a great doctor is one who knows the disease”, the proposed approach is grounded on the philosophy that “a good designer is one who knows about the design principles but a great designer is one who understands the problems (or smells) with the design, their cause, and how they can be addressed by applying proven and sound design principles”. This talk focuses on the “disease”, i.e. the design smells, its different types with the help of a comprehensive catalog, its impact on the software, and actionable suggestions to refactor them in real-world settings.

 
1 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Design smells classification and catalog - 2 minutes
  • Examples of design smells and their impact on software quality - 15 minutes
  • Conclusion and Q&A - 3 minutes

Learning Outcome

  • Understanding the importance of software design quality
  • Design smells and their impact on software quality
  • Design smells classification and catalog
  • Refactoring strategies to repay design debt

Target Audience

software developers, software designers, architects, technical leads, and project/program managers

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Pramod Sadalage
    By Pramod Sadalage  ~  2 years ago
    reply Reply

    Tushar,

     

    I understand where you are coming from in this proposal. Would you be willing change your proposal to take 4-5 design smells and show the code before and after and talk about why its important to deal with the smells.

     

    Thanks

    • Tushar Sharma
      By Tushar Sharma  ~  2 years ago
      reply Reply

      Yes, in fact when I mentioned "Examples of design smells and their impact on software quality - 20 minutes" in the outline of my talk, the intention is to show examples of design smells, talk about their impact on quality, and how these smells can be refactored.

      Thanks.

      • Naresh Jain
        By Naresh Jain  ~  2 years ago
        reply Reply

        We believe this is an important topic. However, we only have a 20 mins slot left. Hence we request that you change your proposal to a total of 20 mins and use that 20 mins to do a demo of 3-5 design smells. Just focus on those and remove all the theory. If you agree, please update the proposal, post which we'll be able to accept the proposal.

  • Naresh Jain
    By Naresh Jain  ~  2 years ago
    reply Reply

    Thanks for the proposal Tushar.

    60 mins talk on Design Smells can get very boring. Can you shortern the time? For ex: You could safely skip the intro, most people know that.

    Also can you please share a video of your past presentation? We would like to see you presentation style.

    • Tushar Sharma
      By Tushar Sharma  ~  2 years ago
      reply Reply

      Hi Naresh,

      I can make it as a 45 minute session by shortening the introduction and other sections.

      I have not recorded any of my past presentations, so I am unable to provide you the videos. However, I have presented in many national/international conferences and I can provide you the past presentations if you are interested.

      A note about my presentation style - I like to use "Prezi" as my presentation tool and I tend to rely on examples/anecdotes rather than being theoritical.

      Thanks and regards,

      -Tushar