Best Tools for Software Maintenance Engineering

Question

Yes, the dreaded 'M' word. You've got a workstation, source control and half a million lines of source code that you didn't write. The documentation was out of date the moment that it was approved and published. The original developers are LTAO, at the next project/startup/loony bin and not answering email. What are you going to do? {favourite editor} and Grep will get you started on your spelunking through the gnarling guts of the code base but what other tools should be in the maintenance engineers toolbox? To start the ball-rolling; I don't think I could live without source-insight for C/C++ spelunking. (DISCLAIMER: I don't work for 'em). JavaScript questions and answers, JavaScript questions pdf, JavaScript question bank, JavaScript questions and answers pdf, mcq on JavaScript pdf, JavaScript questions and solutions, JavaScript mcq Test , Interview JavaScript questions, JavaScript Questions for Interview, JavaScript MCQ (Multiple Choice Questions)

Answer 1

Just like eating the elephant - one bite at a time :) Sometimes the big picture can be a real demotivator, and you need to pick a spot and tackle it piece by piece. Of course, you still need to choose the bit to start on. Typically this is driven mostly by the users/business with top priority specific changes required (yesterday) but if you have a little flexibility or familiarization time, metrics are often useful. Tools here vary with the technology and language, but tools like NDepend and JDepend, any built in Code Metrics (like in in Visual Studio Team System, or the various available Eclipse plugins) or a tool like Simian to get a feel for the size of the copy and paste problem. Hopefully the number of unit tests and coverage is greater than zero, and so a good first step is to always get whatever tests you can running in a Continuous Integration environment, as a foundation for adding more tests as you learn. And as others have said - assuming options are available for the language - a good IDE with code navigation and automated refactoring is a must (Eclipse, Visual Studio with or without ReSharper). A couple of morale-boosting books: Michael C. Feathers: Working Effectively with Legacy Code Martin Fowler: Refactoring: Improving the Design of Existing Code Good luck :)