In addition to the value we get from the solution itself, we benefit significantly from working with the Klocwork team. When we require support and clarity on how to best use Klocwork in specific conditions and environments, their team advises us on how to use the solution optimally. 

The reporting helps us understand the trend of our results and whether we improve over time. We can see the history within Klocwork's server architecture and know that we're making things better. It creates a great story for our management. We can demonstrate value and how our software is developing over time. 

Klocwork adequately does what we need it to do. It hasn't performed as well as we would have liked in a few edge cases. We went to Klocwork and discussed those issues with them. Ultimately, it gives us confidence. That's what Klocwork is for.

Integrating Klocwork into our development cycle was relatively simple. It only took a few hours to get it to run and to analyze something for the first time. Klocwork can monitor what is built. It can see all the conditions that are compiled or defined within that build process and the files that have been utilized. 

The project is very easy to integrate into our development environment that we use to develop the code. It's very easy to integrate and run on your code. It doesn't take much time to set up. It finds all possible problems that can happen within your code. It helps develop better-quality software. 

It's also integrated into our CI, continuous integration. It can be automated as part of pushing the code onto the branch.

The most valuable feature of Klocwork is finding defects while you're doing the coding. For example, if you have an IDE plug-in of Klocwork on Visual Studio or Eclipse, you can find the faults; similar to using spell check on Word, you can find out defects during the development phase, which means that you don't have to wait till the development is over to find the flaws and address the deficiencies.

I also find language support in Klocwork good because it used to support only C, C++, C#, and Java, but now, it also supports Java scripts and Python.

The lack of false positives or low false positive rate; I like not having to dig through false positives. Chasing down a false positive can take anywhere from five minutes for a small easy one, then something that is complicated and goes through a whole bunch of different class cases, and it can take up to 45 minutes to an hour to find out if it is a false positive or not.

If you get several thousand findings in code, you want your false positive rate to be very low. If you wind up with 3,000 findings, and if you are going through and trying to determine if each one of those things is a true positive or a false positive, and you find out that a large portion of your findings are false positives, then you've averaged 30 minutes each to find out each one. That is 6,000 hours spent chasing down potentially false positives, which is three man years.

I can print reports out with several thousand findings.

Klocwork's most valuable feature is the static code analysis feature. It detects the potential problem earlier to allow the developer to receive feedback quickly and then address it before it becomes a problem.

The most valuable feature is the Incremental analysis.

• Good set of checkers for static code analysis, cyber security
• Possibility of creating custom checkers- Good and easy integration into continuous integration (CI)
• The whole package offers a lot of possibilities: add-ons for Eclipse, standalone clients, access via web site, support, documentation, command line.

There's a feature in Klocwork called 'on-the-fly analysis', which helps developers to find and fix the defects at the time of development itself. This means that you don't have to wait for the development to finish and waste that time. This provides efficiency. 

Klocwork also has various plugins available for development tools and they work seamlessly. Our clients often opt for Klocwork due to its accuracy of results and the continuous addition of new features. 

I really like Klocwork's server client build because it allows collaboration between the team members. It takes the ratios and it has a portal where one can justify the issues.

It is one of the best tools available for static analysis.

On-the-fly analysis and incremental analysis are the best parts of Klocwork. Currently, we are using both of these features very effectively.

The pre-checkin code review, industry standard checks, continuous integration (CI) and customized checkers are the most valuable features.

First will be the on the fly analysis as it is reducing the time for developing a code. One more best thing is the reports section which is very nice to understand. Also the support which is available for Industry Standards as well as we can also write our own internal standards and we can check during the analysis.

The ability to create custom checkers, which is an important part of most of the projects. Its on the fly capability is very good. 

• First will be the on-the-fly analysis as it is reducing the time for developing code and report generation.
• One more best thing is the reports section which is very nice to understand.

• Its vast checkers supportability
• Custom checker creation
• Industry standards supportability
• Support to a vast number of IDEs and so on.

We like using the static analysis and code refactoring, which are very valuable because of our requirements to meet safety critical levels and reliability.