New Onboard is here — AI-guided, self-hosted onboarding for your codebase. Learn more
Features Code Navigation Static Analysis Graphs Compliance Metrics Custom API How it works Compliance FAQs Pricing Docs Start free trial
Certification

Understand is TÜV SÜD certified to ISO 26262, IEC 61508, and EN 50128

Confidently use Understand as a support tool for automobile, railway, and safety-related development.

Certificate No. Z10 120817 0001 Rev. 00 · Any ASIL · Any SIL

TÜV SÜD functional safety certification mark awarded to Understand.
About our certifications

A qualified software tool for safety-related development

Understand by SciTools is TÜV SÜD certified (Certificate No. Z10 120817 0001 Rev. 00) as a qualified software tool for safety-related development — tested to ISO 26262 (for any ASIL), IEC 61508 (for any SIL), and EN 50128 (for any SIL). Safety is our top priority at SciTools; our software is heavily tested and vetted before each release, providing your team with a safe and secure development environment.

TÜV SÜD
Certified by TÜV SÜD Product Service GmbH
Any ASIL
Tested to ISO 26262 for any ASIL
Any SIL
Tested to IEC 61508 and EN 50128 for any SIL
Certificate details

Exactly which standards and versions were tested

Certificate No. Z10 120817 0001 Rev. 00, issued by TÜV SÜD Product Service GmbH, valid until 2028-04-27.

To request a certified build, contact [email protected].
StandardVersion tested toQualified for
ISO 26262ISO 26262-2:2018, ISO 26262-8:2018Any ASIL
IEC 61508IEC 61508-3:2010Any SIL
EN 50128EN 50128:2011/A2:2020Any SIL

Certifying body

TÜV SÜD Product Service GmbH

Certificate number

Z10 120817 0001 Rev. 00

Valid until

2028-04-27

Scope

What features are certified?

Five parts of Understand fall inside the certified scope.

01 — Source code import and analysis

Import your source code in seconds — via a CMake compile command, our BuildSpy feature for GCC/G++, or manually.

Understand's New Project Wizard, importing source code into a project.

02 — Architectures

Define and export architectures, then analyze dependencies between architectures and source files to keep complex systems organized.

An architecture defined in Understand, showing dependencies between architecture groups.

03 — Metrics

Track key quality metrics, like cyclomatic complexity, to catch risk before it ships.

The Metrics Browser in Understand, listing metric values for a project.

04 — Static analysis

Run static analysis checks manually as you code, or automatically on every check-in, to stay compliant with industry standards like MISRA and AUTOSAR.

Static analysis results in Understand, grouped by file.

05 — Call graphs

Visualize Call Tree and Called-By Tree graphs to trace impact before you make a change.

A Called-By Tree graph in Understand, tracing the callers of a function.
Questions

Why these standards matter

Why ISO 26262?

ISO 26262 is an international standard for functional safety of road vehicles. It provides guidelines and recommendations for the development of safety-critical automotive systems and their components, including software. Following the ISO 26262 standard is important for the following reasons:

  • Safety. ISO 26262 sets guidelines for the development of software in safety-critical systems, such as automotive applications. By following this standard, software developers ensure that their software is designed and developed in a way that prioritizes safety.
  • Compliance. Many industries, such as the automotive industry, require compliance with ISO 26262 as a prerequisite for product release. Having ISO 26262 certified software ensures that your product meets the necessary regulatory requirements.
  • Liability. In the event of an accident or failure, having ISO 26262 certified software can help to protect against liability claims. By following the standard, you can demonstrate that you have taken all necessary precautions to ensure the safety of your product.
  • Quality. ISO 26262 also includes guidelines for quality management systems, which ensures that your software is developed in a consistent and reliable manner. This leads to better product quality and customer satisfaction.
  • Cost. Developing safety-critical software can be expensive. However, by following the guidelines set out in IEC 61508, software developers can reduce the risk of errors and failures, which can ultimately lead to cost savings.
Why IEC 61508?

Similarly to ISO 26262, IEC 61508 is important for software development because it ensures that safety-critical systems are developed in a way that prioritizes safety, meets regulatory requirements, protects against liability claims, ensures high product quality, and can lead to cost savings. Using a tool that follows this Functional Safety Management guideline ensures a higher quality product is received, and may be required for some projects.

Why EN 50128?

EN 50128 is a standard that provides guidelines for the development of software for railway control and protection systems. EN 50128 ensures that safety-critical railway systems are developed in a way that prioritizes safety, meets regulatory requirements, protects against liability claims, ensures high product quality, and can lead to cost savings. Using software tools that follow EN 50128 may be required for some projects.

How do we get a certified build?

Contact [email protected] to request a certified build, or to ask for a copy of the certificate and safety manual.

Which parts of Understand does the certificate cover?

Source code import and analysis, architectures, metrics, static analysis, and call graphs — the five features described above.

Do you also qualify Understand for airborne software?

DO-330 tool qualification for Understand is available separately through our qualification kits.

Get started

Use a certified tool in your safety process

Try Understand on your own code, then contact support for a certified build when you are ready to put it in your toolchain.

Certificate No. Z10 120817 0001 Rev. 00 · TÜV SÜD Product Service GmbH · Valid until 2028-04-27