New .NET Static Analysis Article
Posted on Thu, Oct 06, 2011
Wouldn't it be nice to receive a gentle tap on the shoulder if you're about to add code that will come back and haunt you later—in the form of a bug that could take days to find and fix later in the development process, code that's virtually impossible for your team members to reuse and extend, or a defect that impacts security, reliability, or performance in the field?
Static analysis can give you that kind reminder . . . and it's very feasible to implement for .NET development.
Check out the .NET Static Analysis and Parasoft dotTest article by Parasoft's Arthur Hicken to learn practical tips for using static analysis to prevent defects in .NET and other programming languages (C, C++, Java, etc.).
This article discusses each of the following static analysis techniques, as well as where/when to use them and why they're helpful:
- Code beautification
- Peer review (a.k.a. manual code review and code inspection)
- Pattern-based static analysis (a.k.a static code analysis)
- Flow-based static analysis
- Metrics-based static analysis
- Compiler and other build-related output
You'll learn a proven way to achieve the following key software development benefits:
- Detect bugs or potential bugs that impact reliability, security, and performance.
- Enforce organizational guidelines—design guidelines and specifications (application-specific, use-specific, or platform-specific) and error-prevention guidelines abstracted from known specific bugs.
- Improve code maintainability by improving class design and code organization.
- Enhance code readability by applying common formatting, naming, and other stylistic conventions.
***
To explore additional static analysis white papers, articles, and videos/webinars, visit our Static Analysis Resource Center. Or, visit Parasoft's static analysis page.