Skip to main content

Experience the Perforce Difference: Access Your Free Trial

Prove Compliance and Reduce Time-to-Market with Helix QAC and Klocwork

Perforce Helix QAC Perforce Klocwork

Perforce Static Analysis Powers Mission-Critical Projects

Trusted by Industry Leaders

  • Motorola logo.
  • Raytheon logo.
  • Johns Hopkins Medicine logo.
  • Honda logo.
  • NASA logo.
  • US Army logo.
  • Mitsubishi Motors
  • Toshiba
  • Continental
  • Nissan

How Does Perforce Static Analysis Support Embedded Software Development?

Why Static Analysis?

Automotive, compliance, and safety illustration.

Meet ISO 26262 Functional Safety Compliance Requirements

ISO 26262, titled “Road vehicles — functional safety”, is a risk-based functional safety standard that is critical to the automotive industry. Carmakers, their suppliers, and developers of automotive components are required to comply with the functional safety standard. However, meeting all the compliance requirements can be time consuming and difficult. That is why we make meeting compliance and traceability requirements easy.

One of the requirements for software compliance is the use of coding guidelines. While the most commonly used coding standards are MISRA C and C++, the AUTOSAR C++14 coding guidelines have been growing in popularity.  

Using a certified static code analysis tool — such as Helix QAC and Klocwork — makes compliance to functional safety standards, coding standards, and writing error-free code easier. In addition, both Helix QAC and Klocwork are certified by TÜV-SÜD for the use for safety-related software development, including ISO 26262.

Health, software, and compliance illustration.

Meet IEC 81001-5-1 Compliance Requirements for Health Software Security

IEC 81001-5-1, titled "Health software and health IT systems safety, effectiveness, and security - Part 5-1: Security - Activities in the product lifecycle" is a cybersecurity standard that is critical to the medical technology industry. Organizations developing health software can use IEC 81001-5-1 to consider security in each phase of the software development lifecycle.

IEC 81001-5-1 also recommends coding standards such as MISRA and CERT, and databases such as the Common Weakness Enumeration (CWE) to give developers access to known issues so they can be incorporated into code inspection and testing strategies.

Applying coding standards can be time-consuming when carried out manually, so IEC 81001-5-1 recommends using a static analysis tool to automatically check the code for defects and vulnerabilities. Using a certified static analysis tool like Helix QAC and Klocwork makes it easy to accelerate compliance and ensure security.

Military, requirements, and graph software illustration.

Meet DISA STIG Security Compliance Requirements

DISA STIGs are IT security configurations designed by the U.S. Department of Defense that specify a set of policies, security controls, and best practices for securing operating systems, applications, and more.

Government agencies and defense contractors must comply with relevant STIGs, or else they could face large fines and heavy scrutiny — but it can be easy to fall out of compliance, as the DoD regularly updates 100s of STIGs.

Perforce Static Analysis and SAST tools Helix QAC and Klocwork automate compliance with DISA STIGs, helping organizations stay up-to-date and better manage security software. Our static code analyzers enforce coding rules and flag security violations. They can also check your code against the security weakness list, plus report on how well your code complies with DISA STIGs.

Benefits of Perforce Static Analysis