PPT-Refactoring Code to a SOLID Foundation

Adnan Masood httpblogadnanmasoodcom adnanmasood adnanmasoodacmorg Presented at Inland Empire NET UG 12112012 Example App Before And After OR How to get from here to there Email Sending App. Spring 2011, Lecture 20. YoungSeok. Yoon. (. youngseok@cs.cmu.edu. ). Institute for Software Research. Carnegie Mellon University. Software Evolution. - Evolving and Improving Code -. 1. Mar 24. th. and . Fix . Anti-patterns. Ali Ouni. 1. , . Marouane. Kessentini. 2. , . Houari. Sahraoui. 3. , Mel Ó Cinnéide. 4. , . Kalyanmoy. Deb. 5. , . Katsuro. Inoue. 1. 1. Osaka . University, Japan; . 2. Refactoring and Code Smells. Where are we?. Over the semester we have talked about Software Engineering. . The overall goal of software engineering is to create high quality software efficiently.. What if you don’. Software Design II. Lecture 7. Emily Navarro. Duplication of course material for any commercial purpose without the explicit written permission of the professor is prohibited.. 1. Portions of the slides in this lecture are adapted from http://. (or how I learned to stop worrying and love failing tests) . Presented by Aaron Evans . <aarone@one-shore.com>. Refactoring for Testability. What is refactoring?. What is testability?. How do we do it?. Advanced Software Engineering. 603 492. Dr Nuha El-Khalili. What is Refactoring?. Refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior. . What is refactoring ?. In refactoring, you start with the basic code and make it better. . Change the internal structure of the existing code by changing the factoring without changing the external behaviour.. Severe Code Smells?. 1. Tsubasa. Saika. 1. , . Eunjong. . Choi. 1. , . Norihiro. . Yoshida. 2. , . Shusuke. . Haruna. 1. , . Katsuro. Inoue. 1. 1. Osaka . University, . Japan. 2. Nagoya . University, . into an Industrial Development Process. Yuki Yamanaka. 1. , . Eunjong. Choi. 1. , . Norihiro. Yoshida. 2. , . Katsuro. Inoue. 1. , . Tateki. Sano. 3. 1 Osaka . University, Japan. . 2. . Nara . Institute of Science and . ESaaS. §. 9.6). What Did . W. e . D. o?. Made date calculator easier to read and understand using simple . refactorings. Found a bug. Observation: if we had developed method using TDD, might have gone easier!. Refactoring Defined. A change made to the internal structure of software to make it easier to understand and cheaper to modify without changing its observable behavior. . — . Refactoring. , Martin Fowler. et. al. , page 53. Where are we?. Over the semester we have talked about Software Engineering. . The overall goal of software engineering is to create high quality software efficiently.. What if you don’. t though? There are always pressures and reasons that software isn’t great. (or how I learned to stop worrying and love failing tests) . Presented by Aaron Evans . <aarone@one-shore.com>. Refactoring for Testability. What is refactoring?. What is testability?. How do we do it?. Refactoring RPG What, Why and How Ted Holt Senior Software Developer, Profound Logic Software Senior Technical Editor, itjungle.com What is refactoring? ". . . a change made to the internal structure of the software to make it easier to understand and cheaper to modify without changing its observable behavior." - Martin Fowler, author of