Once you’ve determined severity, probability, and controllability, you can determine the ASIL. Table 4 of Part 3 (ISO 26262-3) provides guidance on this.
Use this chart to determine ASIL based on severity, exposure, and controllability.
Guide to ISO 26262 Software Compliance
Compliance with the safety standard is important, whether you’re developing traditional automotive components (e.g., integrated circuits) or virtual ones (e.g., automotive hypervisors). And it’s critical to maintain compliance throughout your software development lifecycle.
But complying can be difficult for development teams. Systems and codebases grow complex. And that makes it difficult to verify and validate software.
Establish Requirements Traceability
Fulfilling compliance requirements — and proving you met them — is a tedious process. You need to document the requirements and trace them to other artifacts — including tests, issues, and source code.
Establishing requirements traceability makes your verification process easier — especially with a tool like Helix ALM. And it helps you manage risk in the development process.
Storing your code in Helix Core — version control from Perforce — securely manages revision history for all your digital assets. You’ll get fine-grained access controls, high-visibility audit logs, strong password security, and secure replication. So, you can be confident in your code.
