Klocwork created an environment where the engineers have checks and balances as they develop and progress through our release process. The solution is not critical to our organized stations because we don't produce the end solutions. However, it allows us to reassure our customers that we're providing them with a solid basis they can build upon within their processes and procedures. 

Our customers have their own standards to follow. We don't use it to enforce coding standards because we take things from various places, and the standards change depending on the type of tech.

Our upgrade procedure is coarse, and it requires the client sites to be updated at the same time. We must upgrade in one step, and we're dealing with UK and NIS cybersecurity requirements. We must go through the certification each time, and it's becoming more difficult. 

The solution drives developers not to introduce any more errors. We use third-party software to decide whether to fix or analyze what Klocwork provides us. Engineers sometimes question what Klocwork flags, and they must go through that exercise. I like that because it prompts the engineers to think about development, and finding something to spark a discussion is often hard. The tool provides an interesting perspective.

It provides insights that can help new people who join the team. If they try to push code to the system with errors, Klocwork makes them pause and question what they're doing. Klocwork shortens the development cycle and process of third-party reviews by about five percent because the code is a little cleaner. Usually, it will go to review with more people involved. It eliminates some review work because Klocwork provides the individual engineer with insight.

The money saved would be difficult to quantify based on our current utilization of Klocwork. It helps at a fundamental level, reducing the time needed to get to the implementation phase.

It would be great if we could use Klocwork at the company. However, I work at a government facility, and I analyze government software. My company should also be using Klocwork, and they should be acquiring licenses which allow them to operate and use it on all their code.

The limitation that we have is that Klocwork is licensed to certain programs, and if you want to license them to other programs, you have to pay more money.

It saves a lot of time when it comes to finding defects, it's basically inputted in every access we do.

More and more departments are targeting static code analysis now, as they see the benefits. Klocwork with its capabilities is helping with this, providing the integration. The advantage is that while coding, developers see code violations.

This tool was already rolled out in our projects at Delphi Technical Center in Bangalore, India. Though we had a QAC tool for MISRA checks, Klocwork was preferred for complete code base static analysis before projects go to production.

For all GM projects, this tool is used to perform static analysis. It provides a nice report, so all manual efforts in analyzing the code base are completely removed.

It has helped our organization to produce the non-defective code right at the developer's desktop. So we were able to deliver releases on time.

• It has reduced the manual analysis for a lot of scenarios like checking for internal standards.
• It has saved a lot of time in developing a code through on the fly analysis mode.
• Klocwork team is regularly updating their checkers which is the good one where we can get more accurate and new kind of issues or bugs in our code can be identified.

As said earlier checking our industry standards is main burden which involves lot of manual work. Now Klocwork has completely removed this and we are very easily checking our internal standards.

One more is on-the-fly analysis which is the most important feature, and CI which Klocwork provides I believe.

We are very concerned about these issues for some of the critical projects which are very important for us. Using Klocwork, we have cleared all these issues without much difficulty.

The tool helps the team to think beforehand about corner cases or potential bugs that might arise in real-time. This, in turn, increases the efficiency of the project as well as the team.