Reading Time: 5 minutes Difficulty: AdvancedThe design and verification of ADAS systems according to ISO 26262 guidelines, follow a systematic and rigorous approach. Here’s an in-depth advice at the main phases.
The design and verification of ADAS systems according to ISO 26262 guidelines, follow a systematic and rigorous approach. Here’s an in-depth advice at the main phases.
How to design an ADAS system
The design process always begins with four key phases for ADAS systems:
1. Defining Requirements in terms of Functional Safety Concept
- Functional Requirements: it’s helpful to determine what the system should do (e.g., automatic braking, lane-keeping).
- Safety Requirements: let’s identify specific risks, based on hazard analysis (ASIL), to ensure the system does not encourage dangerous situations.
2. Risk Analysis using precise methodologies
- HARA (Hazard Analysis and Risk Assessment) determines the necessary safety integrity levels for each requirement.
- FMEA (Failure Mode and Effects Analysis) identifies potential failures and consequences.
3. System Architecture
- It consists in the design of the system architecture with redundancy and fail-safe mechanisms to ensure safe operation even in the event of a failure.
4. Detailed Design
- It’s fundamental to define hardware and software components, by specifying interfaces and communications between modules.
- Implement safety measures, such as encryption for communication and integrity checks, is also essential.
How to verify an ADAS System
The next phase focuses on rigorously testing the system through structured actions:
1. Requirements Verification
- It ensures that functional and safety requirements are correctly implemented in the system using traceability processes.
2. Unit Testing
- Tests on individual modules or components confirm they function as intended and meet safety requirements.
3. Integration Testing
- The verification of the interactions between different system modules, including communication and interface tests, ensures that components work together in a safe manner.
4. System Testing
- Conducting full-scale testing is useful to validate that the whole ADAS system performs as expected in real-world scenarios, including simulation and on-road testing.
5. Compliance Verification
- At the end, manufacturers must confirm that the system meets all ISO 26262 standards, including the necessary documentation to demonstrate compliance.
To conclude our schematic guide on designing and verifying ADAS systems, some additional actions are essential to maintain state-of-the-art in system performance:
• Continuous iteration, since design and verification processes should be iterative. After each test phase, identified issues may require design modifications.
• Feedback and updates from tests and real-world usage help continuously improve the system and ensure it remains compliant with the standards over time.
Recommended in-depth study
How to manage ADAS System UpdatesLooking for guidance on increasing compliance with the standards?
Go back to the blog
