Change happens. It‘s a fact of life.
This fact is nowhere more evident than in the software industry. Software products rarely remain unchanged for long. They are ever evolving, growing, and adapting as software developers in every shop hammer out product updates, enhancements, customizations, and fixes.

In the past, programs had a relatively modest set of modules and functionality, and change initiatives consisted of the addition of a few new functions by the program‘s original developers. Intimate with the program‘s internals, such programmers could reliably intuit how to avoid inadvertently breaking the older functions, and the size of the programs often allowed for exhaustive regression testing. More and more, however, software change initiatives are what are keeping managers up at night. This is because of a number of factors that have made them increasingly chaotic and difficult to manage.

Fill out the form to the right to download "The McCabe Recommended Approach to Software Change Analysis" to learn more.

Note: In order to view any of the white papers listed here you will need to have Adobe Acrobat Reader installed. Click here to download your free copy.