Compliance with ISO 26262
ISO 26262, Road Vehicles — Functional safety adapts IEC 61508 to road vehicle E/E systems, including software components (safety-related and otherwise).
While ISO 26262 does not specifically mandate a specific static analysis phase, incorporating static analysis can help simplify and improve the design, implementation, and testing stages of software development.
Simplifying ISO 26262 Compliance with CodeSonar
Sophisticated analyses in CodeSonar provide multiple points of leverage for supporting software development and improving the quality of the resulting system. CodeSonar’s extensive reporting and record-keeping mechanisms also assist with the documentation obligations imposed by the standard.
Several major themes cut across different parts of ISO 26262, that can be addressed by using CodeSonar. The major themes are outlined below.
ISO 26262 Themes Addressed by CodeSonar
Given the increased use of software in mission-critical and safety-critical applications (i.e., crash avoidance systems in the latest generation of automobiles, remote SCADA system updates, and more), it’s critical that software follows standards that specify how developers should write code to increase its readability and reliability. CodeSonar automates this task by delivering checkers for important coding standards:
Automotive Safety Integrity Level (ASIL) Management
- ASIL Tracking
- ASIL Decomposition
- ASIL Coexistence
Control and Data Flow
- Coexistence of Elements
- Order of Execution
- Supporting Safety Analyses
Architectural/Design/Coding Principles and Properties
- Avoiding Unnecessary Complexity
- Coding Guidelines
Configuration and Calibration
- Configuration Data
- Calibration Data
- Fault Injection
- Resource Usage
- Reachability and Test Coverage
- Compliance with Coding Guidelines
- Compatibility with Target Hardware
- Correctness and Consistency
- Impact analysis
- Baseline Management
- Problem Reporting and Tracking
- Change Control
- Change Review