“Congratulations on creating a great C++ standard! The first viable coding standard that incorporates advice on C++11!”
“The easier the tool is to use, the more people will want to use it, which means better code and ultimately less long-term costs for Presagis. The ability of QA·C++ to automate a significant portion of our coding standard means more time for developers to focus on product development instead of chasing problems”.
“QA·C++ offers seamlessly equivalent operation to QA·C, and contains an equally impressive level of compliance to the MISRA standard.”
“…code reviews have become more effective. Socionext’s process now requires analysis with QA·C prior to a code review. This stops the team from being distracted by careless or basic issues and enables the reviewers to focus on more important topics, such as logic errors. Socionext estimates that this has reduced the overall development time by 10%.”
“QA·C and QA·C++ are widely adopted by our development teams and proven to be highly effective.”
“QA·C and QA·C++ were already widely adopted by our development teams and already proven to be highly effective when used to analyze manually generated code. This [Rhapsody] integration was very important for us, and PRQA delivered an effective, pragmatic way to independently verify the quality of auto-generated code.“
“RT-RK is entering the automotive industry with full force. It is evident that PRQA provides the defacto solution in this market, and we have wholeheartedly adopted QA·C. The underlying changes to our development process are beneficial on many levels, the main one being more effective compliance with the coding rules, but also in up-skilling our engineers and streamlining our broader work-flow.”
“In the beginning we assumed that better quality software meant more overhead and longer delivery times. We found that if we used V&V to inject the quality at the end of the process, this is indeed the case. However, by having our developers produce quality code from the outset – by adopting coding standards and analyzing with QA·C – not only are we delivering consistently high-quality code, our delivery times have improved and so have our profits!”
“We quickly realized how good QA·C was at identifying coding issues, and that the automation and accuracy of the tool reduced our delivery overhead significantly. We also saw the huge potential for QA·C to drive further productivity improvements, but only if this analysis was fully integrated into our development process and not just used during the later stages of verification and the resulting rework.”
“Our approach has turned completely on its head! In the beginning we assumed there was a trade-off and that better quality software meant more overheads and longer delivery times. We found that if we used V&V to try to inject the quality at the end of the process, this is indeed the case. However, by having our developers produce quality code from the outset – by adopting coding standards and analyzing with QA·C – not only are we delivering consistently high quality code, our delivery times have improved and so have our profits!“.
“We are impressed by the performance of QA·C, it is very accurate and we see that it is finding issues that other tools have missed. We are particularly conscious of the dangers of false negatives and the false sense of confidence that can be created when tools fail to detect genuine issues”.
“When we looked at our customer base and the broader automotive supply chain, it is evident that QA·C is recognized by the industry as a highly effective tool when it comes to MISRA compliance and is also certified to ASIL D. This tallied with our own prior hands-on experience of the tool, and adopting QA·C was, therefore, an easy decision for Protean.”
“This is easily the best software I have seen to visualize, understand, and address complexity.”
“Projects and products depending on the PRQA solution now extend to braking systems through to comfort controls, engine and transmission management, infotainment equipment and displays.”
“Quality needs to be part of your process… if it’s not, you will have a problem. Start with checking your standards and managing your complexity. For this, there is static analysis.”
“Very useful is the feature of disabling some rules: not all the MISRA rules are applicable to all the projects.”
“Since we began using the QA·C MISRA Compliance Module, the quality and consistency of our first generation code has skyrocketed, and our final products have been virtually error-free.”