Certainly, the ISO 26262 is a crucial standard for the functional integrity in the automotive industry, and incorporating its principles into the software development process ensures that the resulting system meets the stringent safety requirements necessary for the automotive application. Here is an example of how I integrate the functional integrity into a software development process. I was working on the development in the vehicle infotainment system with a multi-display setup running and footing on the system launcher using the overdrive network platform with the hypervisor, ensuring the functionality was paramount to the critical features of automotive system. Step 2, incorporate the functionality safety, so safety planning, the safety plans, where in safety plans, develop the comprehensive safety plans outlining the safety goals, activities to deliver and responsibilities of these plans are aligned with the ISO 26262 standard. Safety culture, so foster safety culture within the team by connecting the training session on ISO 26262 and emphasize the importance of safety functionality. Then a hazard analysis and risk assessment, so identify the hazard, kind of detailed hazard analysis to identify the potential safety hazard associated with the IBI system. Risk assessment, assist with the risk associated with each identified hazard considering the factors such as severity, exposure and controllability. Safety goals, so define the safety goal to mitigate the identified risk, for example, ensure that the displacement does not fail in the way that it could distract the driver. Safety, then safety insecures, in safety requirements specifications, driver safety requirements also drive safety requirements from the safety goals, ensure that each safety requirement was specific, measurable and attainable relevance and the time bounded. Then traceability, maintain the traceability between the safety goals, safety requirements and system requirements to ensure the comprehensive coverage and alignments. Then in the software architecture and design, safety mechanism incorporated the system mechanism into a software architecture such as worst-of-time or redundant system and error detection and correction algorithm. Partitioning, use the hypervisor to isolate safety criteria in component form, non-safety critical component, ensure the fault in non-critical parts do not affect the critical functionality is failed. Then in fail-safe design, ensure the system enters a safe state in the case of redacted failures. For example, critical display fails, the system might revert to the basic faulty level back-off display. Implementation, so in implementation coding standard adopted the strict coding standard and guidance to minimize the risk of introducing error during the development. Data analysis, utilize the static analysis tools to detect the potential issues early in the development cycle. Code review, so in conduct the rigorous code review focusing on safety critical code to ensure the compliance with the safety requirements. Then verification and validation, so unit testing, integrating, testing, faulting, detection, testing, safety validation. Then in safety case development, the safety case documentation compiled the safety case demonstrate that the system meets all the function of the safety requirement. This includes all the safety plans, HARA documentation, safety requirement design documentation, test result and validation reports. Review and approvals, the safety case review and approval by the relevant stakeholder in the safety engineer, project manager and electrical and external auditors.
