PPT-Maintenance 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 t though There are always pressures and reasons that software isnt great. 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’. CSSE 575: Session 1, Part . 3. Bad Smells in Code - 1. Steve Chenoweth. Office Phone. : (812) . 877-8974. Cell: (937) 657-3885. Email: chenowet@rose-hulman.edu. http://hidefdetail.com/blog1/?page_id=117. 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://. 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.. A guide to smelling another developer’s source code. How much should you review?. Option 1 – All the Code. Read through every single line. Attempt to understand the general structure of everything. 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, . CSSE 575: Session 1, Part . 3. Bad Smells in Code - 1. Steve Chenoweth. Office Phone. : (812) . 877-8974. Cell: (937) 657-3885. Email: chenowet@rose-hulman.edu. http://hidefdetail.com/blog1/?page_id=117. 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. (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 Mark Ridgley. Owner, Radius Teknologies, LLC. About the Session Author. Mark Ridgley. CLD, CTA, CPI, LabVIEW Champion. Owner, Radius Teknologies, LLC. What’s in it for me?. What a code smell is. What the most common code smells are.