I rate Klocwork a seven out of ten. I rate Klocwork a seven because of the way we use it. We do not use all the capabilities. It's more solution-oriented, and that's not how we leverage it. 

It's designed to meet different standards and provide specific capabilities depending on what each business hopes to get out of it. That flexibility is what makes me lean toward an eight rating. If you know exactly what you want to achieve and your marketplace, then that would be great. However, the process of getting the tool to be what you want it to be is why I rate it as a seven. It can do whatever you need if you invest in it.

I like static code analysis and think it's suitable for development teams. It's like an impartial third party providing you with insight and information. In this day and age, it's good to have some insight and to question what you're doing. I'd recommend it from the point of view that it provides the insights you need. 

You must understand what your business needs are to compare Klocwork with competing products. The Klocwork infrastructure offers flexibility and historical knowledge of trends and changes in the build. 

Understanding the problems you are trying to solve and engaging Klocwork's technical team about how the solution can work for you is critical. Klocwork knows how to solve your concerns, and they will give you confidence in the tool itself.

We are end-users. 

I'd advise users to remember that they need to analyze the static analysis. Just because the product flags something doesn't mean something is wrong. You have to be mindful. If you try to fix all the findings you might have other problems.

I'd rate the solution eight out of ten. 

I have hands-on experience with Klocwork.

I've been heading the Klocwork operations in India since 2007, so I know the product inside out.

My company has a team of fifteen to twenty users of Klocwork, but the actual count differs at any point in time, but I can say there's a team of six to ten people, including myself, actively involved in the product.

As there's always room for improvement, my rating for Klocwork is nine out of ten.

My company is a partner of Perforce, the parent company of Klocwork.

Make sure before you go to a new major upgrade of Klocwork that you copy your database. Shut down Klocwork and all of its services. Then, back up the database before you decide to migrate, or before you decide to run the JavaScript that checks databases. Back it up first, before you do anything. Otherwise, you could lose everything. The databases are finicky.

We use Klocwork in two different configurations, on-prem and cloud. Basically we can summarize on-premises. We connect the client directly to the server on-premises remotely. But for certain products and features, we also use a local server that is on-premise but with different configurations. In this case, the server is deployed with some rule set and configured in a certain manner locally with the second option of redirecting the connection directly to our headquarter.

I would recommend the latest version. In the roadmap of the product, a lot of improvements have been made. We are currently on hold with moving over to this tool because of the license but once we're able to, we'll import our profiles from the previous version to the new one.

The previous version was not compatible with the .NET framework. 4.7.2 it didn't fully consider the retargeting option of C++

I would rate Klocwork seven out of ten.

When we first purchased Klocwork I would have rated it a nine or ten out of ten. However, because of the performance of the execution and cost, I would no longer rate it that high.

I rate Klocwork a six out of ten.

We are currently using SonarQube for other languages, those of Python and Android.

At present, we make use of both the Klocwork and SonarQube tools. However, as we wish to have a combined tool, we are planning to switch to Kuiwan.

I rate Klocwork as a seven out of 10. 

I would recommend, first creating a baseline of their source code with all of the issues, and then handling the new issues on a daily basis while gradually resolving the old ones.

I would rate Klocwork a nine out of ten.

A good thing is that you are rapidly ramped up and can use the tool.

I would rate this solution a nine out of ten. 

My advice to others would be that they should determine their use case before buying the program. If they have many codes, I would not recommend it. If they have a separate project where not many codes are shared between projects, I will recommend it. 

I would like to see better codes between projects and a more user-friendly desktop in the next release. 

On a scale from one to 10, I rate this product a seven.

I recommend this tool as one of the best to be used for static analysis and should at least be tried.

If your source code is in C or C++, you should be using Klocwork. We have compared the results of different tools like SonarQube and Coverity with Klocwork. Klocwork was able to find a better number of defects in the source code than SonarQube and Coverity. At times, both Coverity and SonarQube missed some of the defects such as null pointer dereference, memory leak issues, etc. The detection rate of Klocwork is very high for C and C++.

I would rate Klocwork an eight out of ten.

Unlike other static code analysis tools, Klocwork integrates seamlessly into desktop IDEs, build systems, continuous integration tools, and any team's natural workflow. Mirroring how code is developed at any stage, Klocwork prevents defects and finds vulnerabilities on-the-fly, as code is being written.

Klocwork also helps prioritize work with SmartRank, the revolutionary new recommendation engine that prioritizes issues and helps select which ones to work on first.

Take prioritized, corrective action immediately to deliver more secure and reliable code.

Not much as of now.

Support for more languages would be helpful since this is my trustworthy tool. One more advice from my side would be to do some webinars on Klocwork will be helpful for some new users.

Klocwork is a good product, but keep in mind that before building the code you have to get a report. Then you use the code. If you don't need to get a report after building the source code then this is a good solution for you. I prefer this tool.

I would rate Klocwork as eight out of ten.