Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

Getting started with reports in Klocwork Static Code Analysis

Default reports provide an ideal starting point to gauge the health of your project. If default reports don’t provide enough information, you can edit them or create new ones.

Once you become more familiar with the reporting capabilities of Klocwork Static Code Analysis, you may want to adjust your checker configuration to make sure Static Code Analysis is detecting issues that you really care about and that are in line with your organization’s coding standards.

You may also want to check out advanced reporting options, such as the ability to track file owners in reports, customize metrics, and add your own external documents to Static Code Analysis. See Advanced reporting for the integration build for more details.