Understand (software)

From Wikipedia, the free encyclopedia

Page Module:Infobox/styles.css has no content.

Understand
[[Programmer|DeveloperTemplate:Pluralize from text]]Scientific Toolworks, Inc.
Template:Infobox software/simple
Operating systemWindows, Mac OS X, Linux
Available inAda, Assembly, C#, FORTRAN, Java, Jovial, Pascal, Python, VHDL, Objective C, Objective C++, Visual Basic[.NET], HTML, PHP, JavaScript, XML
TypeStatic program analysis
LicenceProprietary commercial software
Websitescitools.com

Script error: No such module "Check for conflicting parameters".

Understand is a customizable integrated development environment (IDE) that enables static code analysis through an array of visuals, documentation, and metric tools.[2] It was built to help software developers comprehend, maintain, and document their source code.[3] It enables code comprehension by providing flow charts of relationships and building a dictionary of variables and procedures from a provided source code.[4][5]

Features

Understand Call Tree
A Call Tree in Understand by Scitools

In addition to functioning as an integrated development environment, Understand provides tools for metrics and reports, standards testing, documentation, searching, graphing, and code knowledge. It is capable of analyzing projects with millions of lines of code and works with code bases written in multiple languages.[6] Developed originally for Ada, it now supports development in several common programming languages.[7]

Applications

Understand has been used globally for government, commercial, and academic use. It is used in many different industries to both analyze and develop software. Specific uses include a variety of applications: code validation for embedded systems,[4] software litigation consulting,[8] reverse engineering and documentation,[9] and source code change analysis.[10]

References

Page Template:Reflist/styles.css has no content.

  1. ^ Page Module:Citation/CS1/styles.css has no content."Announcements".
  2. ^ Page Module:Citation/CS1/styles.css has no content.Dragomir, Mircea (1 December 2015). "Understand". Softpedia.com. Softpedia. Retrieved 7 December 2015.
  3. ^ Page Module:Citation/CS1/styles.css has no content.D'Ambros, Marco (2008). "Analysing Software Repositories to Understand Software Evolution" (PDF). Software Evolution. pp. 37–67. doi:10.1007/978-3-540-76440-3_3. ISBN 978-3-540-76439-7.
  4. ^ a b Page Module:Citation/CS1/styles.css has no content.Martin, George (March 2011). "The Project-Ready Designer". No. 248. Circuit Cellar. p. 57. Retrieved 8 December 2015. {{cite magazine}}: Cite magazine requires |magazine= (help)
  5. ^ Page Module:Citation/CS1/styles.css has no content."Source Code Analysis Tools". Retrieved 30 August 2022.
  6. ^ Page Module:Citation/CS1/styles.css has no content.Adkins, Francis; Jones, Luke (24 April 2015). "Machine Assisted Semantic Understanding" (PDF). INSuRE. Northeastern University. Retrieved 4 December 2015.
  7. ^ Page Module:Citation/CS1/styles.css has no content.Richard, Brett (24 May 2013). "Source Code Analyzers as a Development Tool". Flurry.com. Yahoo Developer Tools. Retrieved 7 December 2015.
  8. ^ Page Module:Citation/CS1/styles.css has no content.Loren, Lydia; Johnson-Laird, Andy. "Computer Software-Related Litigation" (PDF). FCLR.org. Federal Courts Law Review. Retrieved 7 December 2015.
  9. ^ Page Module:Citation/CS1/styles.css has no content.Phillips, Michael; Mok, Amy. "Spacecraft Flight Software Design Pattern Discovery" (PDF). Johns Hopkins Applied Physics Laboratory. Lockheed Martin Corporation. Retrieved 7 December 2015.
  10. ^ Page Module:Citation/CS1/styles.css has no content.Eshow, Michelle (1 June 2014). "RTMA Source Code Change Analysis" (PDF). Aviation Systems Division. NASA. Archived from the original (PDF) on 10 December 2015. Retrieved 7 December 2015.