LDRArules programming rule checker assures standards compliance - Embedded.com

LDRArules programming rule checker assures standards compliance

DESIGN East – LDRArules is a programming rule checker that brings together a collection of rules from a broad spectrum of programming standards. Implemented by LDRA as a stand-alone product, LDRArules enables development teams to improve their software quality by selecting and adhering to relevant industry programming standards. Companies can easily configure LDRArules for a specific programming standard or choose to enforce in-house programming templates and improve their overall software development methodology.

LDRA offers programming standard conformance for more than a dozen programming standards, including MISRA-C:1998, MISRA-C:2004, MISRA AC, MISRA C++:2008, CERT C, CERT J, CWE, HIS, JPL, JSF++ AV, High Integrity C++, SPARK Ada subset and the Ravenscar Profile. The programming standards provide programming rules across the primary languages used in embedded design: C, C++, Ada and Java.

Click on image to enlarge.

Selection of the MISRA-C:2004 standard from within LDRArules

Developers can choose rules for a specific industry standard or they can select a combination of rules from a variety of standards, creating customized templates tailored for their company and projects. LDRArules documents which rules have been selected, ensuring complete transparency of what programming rules have been implemented.

LDRA states that by simply implementing a programming standard, companies can eradicate 70% of their software defects and significantly decrease overall development cost. By automating an immediate check of code as it’s being written, software defects are identified at their inception, saving the tremendous time and cost of identifying errors late in the development lifecycle.

Click on image to enlarge.

LDRArules MISRA-C:2004 Compliance Summary Report

Compliance with programming standards enables developers to:

  • Promote portability and avoid unexpected results
  • Ensure there is no reliance placed on compiler or platform-specific constructs
  • Identify unreachable or infeasible code which often indicates a defect that will, at the very least, impact software maintainability
  • Prohibit certain language constructs known to be a source of common errors
  • Measurably reduce program complexity
  • Improve program testability, easing standard compliance and certifiability

More information

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.