Testing legacy code with the right tool makes maintaining legacy code easy. Get started today with a free trial of Understand.
The right tools make everything easier. Here's what makes Understand an effective legacy code analysis tool:
Writing tests is key to maintaining legacy code. Understand runs automated tests to ensure your new code is compatible with the intended behavior of the legacy code.
Lack of documentation is one reason understanding legacy code is so challenging. Use Understand to overcome this obstacle by tagging and annotating your code. This feature ensures continuity between you and other engineers working on the same legacy code.
Understand's bottom-up architecture structures legacy code in a way that helps you understand it.
Understand's CodeCheck feature provides comprehensive coverage of your legacy code, so you know exactly what's working and what's not. Check for mistakes, identify bugs, and resolve errors using this feature for legacy code analysis.
“What would have previously taken me several days (or weeks) can now be accomplished in a matter of hours… It’s the Swiss army knife of static analysis tools.”
“[Understand] is good for discovering the structure of the code dependencies and call-paths... it would have taken me hours to generate the same thing on my own.”
“Understand accelerates my understanding of large source code repositories.”
Chris Rhodes, Senior Software Engineer
Dell Inc.
“[Understand] has great graphing tools, metrics, reporting, data dictionary… and is customizable and extensible. It also helps you to find compile time and parsing errors.”
– USAF Software Developer
“Understand can take existing code and basically generate any design information or view you would want to see, in addition to performing several useful types of analyses.”
– Jason Bold, Sr. Software Eng.
“Understand is a tremendous reverse engineering tool... with excellent metrics reporting and evolving standards verification capability.”
– Pratt & Whitney Software Developer
“Understand™ is good for discovering the structure of the code dependencies and call-paths... it would have taken me hours to generate the same thing on my own, and I would not have had near as much confidence in my own work (assurance that I understood the code correctly).”
– Paul Hyland, Software Engineer, Lockheed Martin
