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.
Tag Your Legacy Code for Clarity
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.
Use Understand's Architectural Design Structure to Make Sense of Legacy Code
Understand's bottom-up architecture structures legacy code in a way that helps you understand it.
Get Full Coverage with Legacy Code Testing
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.
Save Time with Understand
“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.”
Randall Landaiche
Intuity
“[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.”
Paul Hyland
Lockheed Martin
“Understand accelerates my understanding of large source code repositories.”
Chris Rhodes
Dell
Trusted by over 20,000 developers
Customer Case Studies
Learn how software developers across different industries use Understand to accelerate their workflows.
“[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.”
“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.”
“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
Try Understand for Free Today!
Our free trial enables all features that can be used on a sample code base