Frequently asked questions about static source code analysis

• What is static source code analysis?
• Why is static source code analysis necessary?
• Is there anything wrong with having my expert coders manually analyze their own code?
• Can static source code analysis aid my quality practices?
• How is static source code analysis done?
• Is it possible to produce bug-free code?
• Why should I invest in a static source code analysis tool?
• What are the key long term benefits associated with automating static source code analysis?
• Doesn't my compiler already do syntax checking?
• Doesn't ANSI C make lint obsolete?
• There's a free lint utility that comes with UNIX, why should I want to pay for a commercial static source analysis tool?
• Are you saying my debugger isn't enough?
• How much time will I save by conducting automated static source analysis?
• Can't I have my programmers generate the reports manually?
• When do we stop testing software?
• We have an established testing program with automated testing tools, what good will it do to add pre-compile analysis step to our software development process?
• What is dynamic analysis, and why isn't it enough?
• What is Cleanscape LintPlus?
• What is Cleanscape FortranLint?
• Who can benefit from Cleanscape static source code analysis?
• Why should I choose Cleanscape's lint tools?