In-House Coding Standards

Configure your own coding standard drawing from your own style guide, and other coding standards such as MISRA, JSF or CERT

  • Draw from established, peer-reviewed standards to
    form your own
  • Configure the rules you would like to apply based on your project’s needs
  • Use PRQA to automatically enforce, report, audit,
    and prove compliance to your internal standard

 

Overlaps Between Coding Standards

PRQA-white-paper-overlap-between-coding-standards

 

A study of rule overlaps and effective compliance that considers HICPP, JSF++ and MISRA C++ standards.

Related Article:

V4.0 High Integrity C++ Coding Standard (HIC++), One Year On Reviews V4.0

  • Reviews V4.0,
  • Identify rules which have been most frequently referenced
  • See feedback from the user community
  • Expert discussions on the best way to use Modern C++.

Read Full Article >

Why create your own standard?

Independent research by VDC shows that more than ⅓ of software projects use their own internal coding standard. However, creating your own standard from scratch makes little sense when there are well-established and peer-reviewed standards you can borrow from.

Instead, it is safer and faster to use an existing coding standard as your foundation and then modify it as needed. PRQA can accommodate your internal coding standards, providing the same automated testing it does to MISRA, HIC++, and other standards.

How to leverage existing standards with PRQA

1.Add tailored guidance to complement an established standard

Add your own rules and guidelines to an established coding standard to support your specific workflows and use cases.

This gives you the safety of a peer-reviewed standard and the flexibility required to make it work for your organization.

1.Add-tailored- guidance-to- complement-an -established- standard

2-Create-a-hybrid- standard

2.Create a hybrid standard

Take the best of two or more established coding standards such as MISRA C++ and JSF AV++ to create your own.

You can add your own modifications on top of this hybrid.

3.Combine general language and project-specific rules

Combine and enforce a subset of a comprehensive standard such as MISRA and any project-specific rules because your end-user customer requests it, or because it’s important for your application domain.

3.Combine-general-language- and-project-specific-rules

4-Train-new-hires and-inexperienced -developers-faster

4. Train new hires and inexperienced developers faster

With a well-documented coding standard and a tool to automatically enforce it, you reduce the need for existing team members to supervise new hires, inexperienced developers, and graduates.

By highlighting the parts of your internal coding standard that are specific to your company and project, you help this group become familiar with your processes and practices faster.

Who is this product for:

Software development teams that need to adopt and enforce an in-house standard.

QA managers, compliance managers, and team leaders who need their developers to produce compliant code with a tool that only flags relevant issues.

Engineering leaders who need their developers to produce compliant software code in the most effective and efficient manner, reducing lead times and the cost of development.

"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!"

Samir Kulkarni Head of Productivity and Functional Excellence
KPIT Technologies
See full story: From Compliance to Exploitation: Defect Prevention is  Better than Cure >