Static program analysis: Difference between revisions

Revision as of 06:06, 21 October 2003

Revision as of 14:14, 12 January 2004

Line 1:

'''Static code analysis''' is a set of methods for analysing [[software]] [[source code]] in an effort to gain [[understanding]] and to target areas for [[review]] and/or [[rewrite]]. The number of metrics[[metric]]s (''measures'') that can be applied are numerous. One of the crudest measurmentsmeasurements, for example, is the size of code, usually expressed in kLOC's (1000 lines of code). Defining a consistent definition of a ''[[line of code]]'' has long been an item for debate.

One common metric in static analysis is ''[[McCabes Cyclomatic Complexity Metric]]'' which measures the number of choices a function makes. Functions with a high number of conditional statements (if's, while etc.) will have a high [[complexity]]. Such functions therefore can be considered more likely to contain bugs[[bug]]s and be harder to maintain.

==See also==

* [[AntiC]]

* [[SPlint]]

* [[Broadway]]

* [[DAEDALUS]]

==External links==

* [http://yunus.hun.edu.tr/~sencer/research.html information of software management]

* [http://citeseer.org/cs?q=static+and+code+and+analysis Citations from CiteSeer]