Writing code on an agile project is based on principles like simple design; ever wonder why you don’t have a process to write code that embraces these principles?
This session will explain the best practices of software change. It will refresh and reinvigorate those that write code and open the doors to the development process to those who work with developers everyday. You will learn how to change large applications quickly with a of minimum risk and only as-needed knowledge of the code and project domain.
Examples of the developer practices related to software change include ***feature location*** that locates the place in the existing code where a new feature is to be implemented, ***impact analysis*** that assesses how much the old code is going to be impacted if a new feature is added to it, ***refactoring*** that either prepares the code for the change or cleans up the aftermath, change propagation that traces where the secondary changes are to be made, verification that confirms both the new and the old code, and so forth. These practices are summarized in a ***phased model of software change.*** Hands-on examples will allow the participants to practice these topics.

You must be a Member to view this post and you are currently not logged in.

You can either log in below or sign up here.