A recent article by S. Tucker Taft and Robert B.K. Dewar begins:
"As static analysis tools have become more sophisticated, their role in the software development process has become a subject of debate. Can a project team use a static analysis tool instead of other, presumably more labor-intensive steps in the normal process of coding, testing, verifying, validating, and ultimately, certifying critical software? The answer is an unequivocal 'yes.'"
Read the complete Making Static Analysis a Part of Code Review article for their thoughts on how static analysis tools can ease the difficulty of reviewing unfamiliar code.
Friday, July 31, 2009
Using Static Analysis as Part of Code Review
Labels:
code review,
static analysis,
static code analysis
Subscribe to:
Post Comments (Atom)

No comments:
Post a Comment