Understand by Scitools is certified for use as a support tool for all projects requiring ISO 26262, IEC 61508, and EN 50128 compliance. 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.
Please contact [email protected] for additional certification information and to acquire a certified build.
Interested in purchasing an Understand License?See Pricing
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 is a standard that 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.
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.
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.
Import source code using a cmake compile command, our Buildspy feature for gcc/g++, or manually.
Define architectures, export architectures, export dependencies between architectures, and analyze dependencies between architectures and source files.
View and track useful metrics like cyclomatic complexity.
Perform static analysis checks to check your code. These checks can be executed manually while you code or automatically with every code check-in. Ensure your code is complying with industry standards like MISRSA automotive and AUTOSAR software.
Create Call Tree and Called by Tree graphs.
Chris Rhodes, Senior Software Engineer