ISO 26262 Compliant Testing And Verification Of Automotive Control Units
Partner with us for ISO 26262 compliant testing and validation of automotive control units. Our ECU verification and validation services are based on Part 6.9, 6.10 and 6.11 of the ISO 26262 standard.
In our endeavor to help Automotive OEMs’ and Suppliers achieve the required ASIL for their products, we have partnered with global brands from USA, Europe, China/Taiwan, and India.
ISO 26262 Compliant Testing: The Process Flowchart
Expertise in ECU Testing Tools Certified by ISO 26262
We have expertise in the following Testing and Verification tools. These include tools certified by ISO 26262 standard and others.
- CANTATA– Ideal to automate unit and integration testing and verification of the ISO 26262 compliant code. It is an ISO 26262 certified tool.
- RTRT– An Automation tool for unit testing, developed by IBM. It is a widely used testing tool and is certified by ISO 26262
- Polyspace: This tool uses formal techniques to test run-time errors. It checks for security vulnerability, coding guidelines and other classes of bugs. It is used for static verification process
- MX-Suite: This is one of the most comprehensive automated testing tools for software verification of embedded systems.
Testing Services for Automotive Control Units: Complaint with the Functional Safety Standard
Unit Testing Services for Automotive Software
Expertise in Requirement-based testing, Interface Testing and Fault-injection testing methods, in accordance with the assigned ASIL for your automotive product
Support for executing testing on the target environment as well as simulators
Derivation of the Test cases, based on the analysis of Requirements, Equivalence Classes, and Boundary Values
Support for determination of coverage of requirements at Unit Level
Statement coverage, branch coverage and MC/DC coverage
ISO 26262 Compliant Integration Testing Services
Analysis of requirements at architectural levels, in order to perform requirement-based testing
Verification of safety mechanism by fault-injection testing
Fulfilment of requirements that may be impacted by hardware design (storage usage, min/max execution time etc.)
Simulation of Models and Codes to compare the results
Structural coverage measures, in terms of Function Coverage and Call coverage
Expertise in integration testing tool such as CANTATA, MX-Suite and LDRA
ISO 26262 Compliant Static Verification Services
Support for different static verification techniques as per ISO 26262 standard
Control Flow analysis
Data flow analysis
Static code analysis
Model-level verification of software unit design and implementation
The following design principles mandated by ISO 26262 standard are taken care of:
One entry/exit point in functions
Avoiding global variables
Limited use of pointers
No recursions, etc.
MISRA check of all the modules under test
Expertise in static analysis tools like QA-C (CANTATA) and PolySpace
Meet Our Automotive Leaders
FAQs Regarding ISO 26262 Compliant Testing Services
Ans. Primarily, we partner with the customers based on the “Time and Material” business model. The billing is charged based on the actual man hours and cost of equipment (3rd party tools etc.) for the project.
However, once the project and relationship mature and we gain deeper understanding of the code complexities, tool requirements and future changes, the business model can be changed to “fixed price model”.
Ans. The following is the indicative list of the testing tools that we have worked with, during ISO 26262 testing projects are as follows:
- CANTATA for Unit and Integration Testing
- MX-Suite for unit testing and software verification of embedded system
- RTRT for Unit Testing
- Polyspace to check coding guidelines and static verification process
Our hands-on experience of working on these tools include projects on different ECUs. We can share more details once we sign the NDA.
Ans. The security and integrity of the code is our number one priority, as per the NDA signed with our customers.
We adhere to the GDPR and ISO 27001 guidelines for the code safety and integrity.
Secure FTP is also always made available, to ensure that code is transferred in a secure environment.
Ans. When you partner with Embitel, for ISO 26262 compliant testing services, you collaborate with an expert core team of:
- Functional Safety Consultants
- Project Managers
- Testing Engineers.
Here is the team hierarchy that is most commonly followed in the ISO 26262 Testing Projects:
Functional Safety Manager: Ensures that the ISO 26262 testing guidelines are followed in letter and spirit, during the testing processes. For all the technical discussions, the Functional Safety Manager will be your SPOC.
Project Manager: Manages the entire project execution and coordinate between the team and the customers.
Testing Engineers: Collaborate for Unit Testing, Integration Testing and Validation activities
Ans. We do have an onsite/offshore business model, in which we provide resources to our customers for testing projects.
Our engineers travel to the customer’s location to perform software testing. This is usually opted when the customers have certain tools or environments specific to the project.
Alternatively, the customers can also set up an off-shore development center (ODC), where they can send the work-products for testing, under a secure environment.
We will perform the tests and share the report within a stipulated span of time. We will ensure that a secure communication infrastructure is created to protect the integrity of the code.
Ans. Following reports will be provided, as deliverables of ISO 26262 Testing Project:
- Unit Test Reports, Integration Testing Reports, etc.
- Tool reports from tools like CANTATA, MX-Suite etc.
If the customers require the reports in any specific test template, we can support for the same.
Ans. We share weekly or monthly Timesheets with the customers to keep them apprised of the developments in the project. The timesheet covers the completed processes, pending activities, health of the project etc.
The project managers also have regular calls with the customers to give the heads-up on the project. This is how the communication channel is maintained and project is supervised.