Automotive Electronics-Functional Safety Compliances-Trinity Technologies

Contact number:

+886 2 77182788

SOLUTIONS
Functional Safety Compliances

Automotive Electronics

Provide the software development and testing solution to satisfy ISO 26262 and ASPICE standards

With the rapid development of technologies such as intelligent driving, new energy vehicles, and vehicle-to-everything (V2X) connectivity, “software-defined vehicles” have become an inevitable trend. Compared to the period before 2010, the research and development (R&D) technologies and methods for automobiles have undergone and continue to undergo significant changes, with software now becoming one of the most critical components in automotive R&D. It is foreseeable that in the near future, emerging technologies such as autonomous driving and V2X will even surpass traditional automotive electronics, occupying a more central position in the automotive software field. As a result, the reliability and security of software will become a top priority for vehicle safety.

Fortunately, major vehicle manufacturers, parts suppliers, and industry associations both domestically and internationally have already anticipated this trend and, under this backdrop, have successively released relevant industry standards. From the earliest version of the MISRA C coding standard released in 1998, to the Automotive Software Process Improvement and Capability Determination (ASPICE) standard released in 2005, to the Functional Safety standard ISO 26262 released in 2011, to the 2020 release of the ISO/SAE 21434 standard for cybersecurity in road vehicles, and the upcoming ISO 21448 standard specifically targeting the safety of intended functionality (SOTIF) for autonomous vehicles. These industry standards regulate the development of automotive critical systems and software from multiple perspectives, including software coding, R&D maturity processes, functional safety, information security, and intended safety, to ensure vehicle safety and reliability while R&D technology continues to advance rapidly.

In addition to meeting the functional safety and process integrity requirements of ISO 26262 and ASPICE compliance, R&D teams will face more complex issues and demands in actual product development processes.

汽车电子小水印.png

Demands and Challenges

What specific requirements do standards such as ISO 26262, ASPICE, and SOTIF impose on software development processes and testing?
How to balance efficiency, quality, and compliance? This is a controversial issue...
Manual or automated, open source or commercial tools—how to choose?
Which aspects of black-box testing, gray-box testing, and white-box testing required by ISO 26262 and ASPICE can be automated?
What are the key differences between embedded software and host computer software in terms of testing requirements and methods?
Have you spent a lot of money on testing tools that you haven't used or haven't seen results from?
What requirements do standards such as ISO 26262 and ASPICE place on automated development and testing tools?

Solutions

Code static analysis, using the authoritative static analysis tool QAC to meet common coding standards in the automotive electronics industry, such as MISRA C/C++ and AutoSAR C++14, and perfectly complying with ISO 26262 and ASPICE standards for code static analysis.
Unit testing and integration testing, using VectorCAST to verify the reliability and correctness of software unit modules, quickly meeting the requirements of ISO 26262 and ASPICE for unit testing.
Gray box testing, DT10 supports system tracking execution, complex defect tracing, performance testing, and long-term reliability verification.
Software-in-the-Loop testing, CANoe4SW provides a software simulation system testing platform for automotive electronics.
Hardware-in-the-Loop testing, provided by Vector's HiL system test platform integrated with “VT System + vTESTstudio + CANoe,” offers physical hardware simulation and system testing solutions for automotive electronic systems..
Test coverage analysis throughout the software development life cycle to meet the audit requirements for test integrity specified in ISO 26262 and ASPICE at all levels.
Use Visure Requirements to manage requirements and establish traceability throughout the software lifecycle.
Complete toolchain for CAN bus verification, diagnostics, and calibration.
The commonly used tools provided have been certified and verified by third-party authoritative institutions as complying with ISO 26262 and ASPICE standards.
Automotive software R&D engineering consulting and testing services that comply with ISO 26262 and ASPICE requirements, etc.

Particularly Noteworthy

Code Static Analysis
Unit Testing
Performance Testing
Hardware-in-the-loop Testing
Software-in-the-loop Testing
Traceability

Code Static Analysis

A unified coding standard is the top priority for vehicle manufacturers and their downstream suppliers when conducting code-level testing, and it is also one of the fundamental audit points for ISO 26262 and ASPICE compliance certification. MISRA C, MISRA C++, AUTOSAR C++14, CERT C/C++, and CWE C/C++ are among the most commonly used standards in the automotive electronics industry. QAC static analysis tools provide the most comprehensive and authoritative automated code static analysis solutions, enabling users to quickly and accurately identify non-compliant code and hidden code defects, ensuring code compliance, and addressing common code errors from the outset of development. QAC is also the preferred static analysis tool for the majority of automotive OEMs, Tier 1, and Tier 2 suppliers when meeting ISO 26262 and ASPICE compliance requirements.
Unit Testing

ISO 26262 and ASPICE require testing of underlying design requirements, which is typically accomplished through unit testing. Verification of the reliability and correctness of individual functions or modules composed of multiple functions can all be categorized under unit testing. Compared to system-level testing of software, unit testing is more cumbersome, time-consuming, and labor-intensive. For embedded software with ISO 26262, ASPICE compliance requirements, unit testing is particularly challenging due to difficulties in test-driven development, execution environments, and coverage statistics, making it nearly impossible to perform manually. VectorCAST's embedded software dynamic testing tools offer specialized automated solutions for ISO 26262, ASPICE, and other standards. By leveraging automated test environment creation, automatic test case generation, a graphical test case design platform, flexible management mechanisms, comprehensive coverage statistics, and robust support for over 40 common development environments, VectorCAST effectively boosts unit testing efficiency by 70-80%. VectorCAST has also been certified by international authoritative institutions, fully complying with the requirements of ISO 26262 functional safety and ASPICE certification.
Performance Testing

Using the DT10 dynamic testing and tracking debugging tool, you can track the execution process of automotive electronic software over a long period of time and measure and analyze the execution performance of various functions, modules, tasks, code blocks, CPU load, and other dimensions of the software in real time. Compared with traditional performance testing using oscilloscopes, the performance testing solution provided by DT10 is more efficient and makes it easier to locate performance anomalies and identify the root cause of problems in the source code.
Hardware-in-the-loop Testing

The Vector HiL system hardware-in-the-loop (HIL) test platform, consisting of “VT System + vTESTstudio + CANoe,” provides automotive electronic systems with an integrated physical simulation and testing solution that includes test design, test execution, network analysis, I/O interfaces, and stimulus hardware boards. It helps users accelerate the establishment of test environments, test automation, and automatic regression testing, significantly improving test efficiency and reducing labor costs.
Software-in-the-loop Testing

Using the next-generation CANoe4SW software-in-the-loop (SIL) testing tool, automotive electronics R&D teams can verify software interfaces and logic before the hardware environment is ready. The test cases designed and executed during software-in-the-loop testing can be seamlessly reused in hardware-in-the-loop testing, enabling system testing to begin earlier and defects or errors in system functionality to be identified sooner. Additionally, due to its purely software-based implementation, test case automation and testing efficiency are higher, thereby shortening the project cycle.
Traceability

Using the Visure Requirements Management System, manage the design process at all levels, from high-level product design to high-level design to low-level detailed design, and integrate with commonly used development and testing systems to meet the ISO 26262 functional safety standards and ASPICE requirements for software requirement traceability. More specifically, achieve bidirectional traceability between all stages of the R&D process, including:

• Between software system requirements and high-level design

• Between high-level design and detailed design

• Between software requirements and test cases

• Between test cases and defects

Ultimately, this forms the Requirements Traceability Matrix . The primary purpose of the traceability requirements in standards such as ISO 26262 and ASPICE is to ensure consistency and accuracy of information across all stages of the R&D process, as well as efficient change impact analysis, thereby ensuring that the final deliverables do not deviate from the intended objectives.