Get the latest critical update information for Log4j vulnerability. See how to address the issue with Parasoft guidance. Learn More >>
ISO 26262 (the international standard for functional safety) is an automotive functional safety standard that covers the entire automotive product development process. ISO 26262 inherited or is an adaptation of safety requirements standard IEC 61508 for the industrial automation industry, but tailored specifically for the automotive industry. The latest version is ISO 26262-1:2018.
It includes activities such as requirements analysis , safety analysis, quality management, design, implementation, integration, verification, validation, and configuration. This applies to road vehicles such as motorcycles, traditional oil-powered cars and trucks, hybrids, and autonomous vehicles.
The standard provides guidance on automotive safety lifecycle activities for OEMs and other suppliers by specifying the following requirements:
Overall, ISO 26262 is separated into 12 parts to ISO that can be broken down simply using the above diagram.
Part 6 of the standard specifically addresses product development at the software level, and Parasoft users can save time and effort adhering to this part of the standard. Sections 6.9, 6.10, and 6.11 represent the testing or formal verification and validation of the software.
This includes the multiple verification methods (unit testing, static analysis, structural code coverage, requirements traceability, and more) recommended or highly recommended based on the assigned automotive safety integrity levels (ASIL). As with safety concepts and safety-related systems, the margin for error in hardware and software is thin.
Satisfy ISO 26262 compliance objectives by automating verification and validation methods like code reviews, requirements traceability, static analysis, unit testing, code coverage, and more, while also reducing the amount of labor costs and time to market.
“MISRA”, “MISRA C” and the triangle logo are registered trademarks of The MISRA Consortium Limited. ©The MISRA Consortium Limited, 2021. All rights reserved.
Adopt an automated software testing solution that will support and take you through the entire ISO 26262 software development life cycle. The Parasoft ISO 26262 compliance dashboard puts everything at your fingertips.
Parasoft’s tool suite provides a complete verification and validation framework with static analysis, unit testing, integration testing, system testing, structural code coverage, and more for the delivery of safe, secure, and reliable software, compliant to any ASIL level, satisfying ISO 26262.
Something else that’s extremely important to note is that C/C++test integrates right into your developers’ IDE. This dramatically shortens the learning curve, simplifies adoption, improves productivity and costs.
Begin by implementing your code to requirements. As the code is written, run the static analysis often to identify and fix any coding violations identified. This prevents defects in safety, security, and quality at the earliest and least expensive phase in software development agnostic of methodology, Agile, Waterfall, Spiral, and more.
As you move into and up the software verification phases (unit, integration, and system testing), strongly consider integrating your testing into your build process. Automation into a modern continuous integration and continuous delivery (CI/CD) workflow has shown to be very beneficial in many ways.
Defects are found quicker and often, the products improve rapidly, more features are introduced, release cycles are shorter, and much more. C/C++test easily integrates into modern CI/CD development ecosystems, offering the most value and cost-effective automated software tools and testing solutions.
There are many unique advantages that Parasoft brings to the table. Since many of our clients span across industries ranging from medical devices to defense systems, our tools must be dynamic and robust. Parasoft solutions perform a variety of tasks from offering development tools to life cycle management. Here are some of the ways Parasoft solutions help embedded software teams comply with ISO 26262.
One key Parasoft C/C++test benefit is its dedicated integrations with embedded IDEs and debuggers. Supported IDE environments include Eclipse, VS Code, Green Hills Multi, Wind River Workbench, IAR EW, ARM MDK, ARM DS-5, TI CCS, Visual Studio, and many others.
C/C++test can also be used to execute unit, integration, and system tests on the host platform, simulator, or on the embedded target hardware. The fully integrated solution can be optimized to take minimal additional overhead for the binary footprint of process cycles.
One other huge benefit Parasoft brings to the table is its unique tool suite offering to address today’s automotive needs in terms of automotive testing and confirmation measures.
Parasoft SOAtest and Virtualize are well suited for network-based system-level testing of various types. Virtualize allows developers to build integrations earlier, stabilize dependencies, and gain full control of their test data. Teams can move forward quickly without waiting for access to dependent services that are either incomplete or unavailable.
SOAtest delivers fully integrated API and web service testing tools that automate end-to-end functional API testing. Teams can streamline automated testing with advanced functional test creation capabilities for applications with multiple interfaces and protocols.
Parasoft test automation solutions provide considerable time and cost savings. We strive to make it as painless as possible with as much hand-holding as needed for your safety goals in achieving ISO 26262 compliance. Our educational materials like webinars, whitepapers, and our blog act as ongoing supplemental tools, as well.
A functional safety standard like ISO 26262 is needed because automobiles have evolved into a complex electrical and electronic architecture, containing multiple interconnected ECUs with millions of lines of code.
Assurance that these systems are equipped to address the possible hazards caused by malfunctioning behavior is crucial. ISO 26262 lays out a set of objectives throughout the entire automobile product life cycle that helps address safety in the development of electronic systems.
Automotive Software Performance Improvement and Capability dEtermination (ASPICE) is a standard that defines the process for the development of software in the automotive industry.
ASPICE addresses practices in how teams should organize their projects and manage deliverables. It builds on each of the phases of the V-model to ensure continuous innovation and product development at every stage, to help the automotive supplier become more efficient.
It’s a standard that incorporates safety functions or a fail-safe function to provide a way for the electronic system to function correctly or fail in a predictable safe manner. Hardware failures and software failures can both have catastrophic effects. Your tool confidence levels increase by using tools with TÜV certification.
An example would be the thermal heat sensor in your vehicle’s engine to detect overheating so that the engine controller would not just notify the driver of its increasing hazard condition. Ultimately, this forces the shutdown of the vehicle to prevent a fire hazard and potential loss of life.