Road vehicles - Functional safety audit and assessment method - Part 3: Software level
1 Scope
This document specifies the requirements and methods for conducting functional safety audits and assessments for functional safety-related activities and work results of safety-related electrical/electronic (E/E) systems at the software level to check and judge the impact of the development process and work results on functional safety compliance.
This document is applicable to safety-related systems including one or more electrical/electronic (E/E) systems installed on mass production road vehicles other than mopeds.
This document is not applicable to specific electrical/electronic (E/E) systems on special purpose vehicles, for example, vehicle systems designed for drivers with disabilities.
2 Normative references
The following documents contain provisions which, through reference in this text, constitute provisions of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
GB/T 43253.1-2023 Road vehicle functional safety audit and assessment methods - Part 1: General requirements
3 Terms and definitions
For the purposes of this document, the terms and definitions given in GB/T 34590.1-2022 apply.
4 General requirements
For the purpose of this document, the terms and definitions given in GB/T 43253.1-2023 apply.
Functional safety audit and assessment at the software level mainly involves the following contents:
——Software development environment;
——Software security requirements;
——Software architecture design specification;
——Safety analysis report;
——Related failure analysis report;
——Software unit design and implementation;
——Software unit verification;
——Software integration and verification;
——Embedded software testing;
——Software calibration and configuration management;
——Software component identification.
Through audit and assessment, it is judged that the functional safety development at the software level based on evidence meets the following requirements:
——Software-related technical security requirements specifications are appropriate and complete;
Contents Foreword i Introduction ii 1 Scope 2 Normative references 3 Terms and definitions 4 General requirements 5 Software development environment 5.1 Objective 5.2 Input of audit and assessment 5.3 Requirements for audit and assessment 6 Requirements for software security 6.1 Objective 6.2 Input of audit and assessment 6.3 Requirements for audit and assessment 7 Software architecture design specification 7.1 Objective 7.2 Input of audit and assessment 7.3 Requirements for audit and assessment 8 Software unit design and implementation 8.1 Objective 8.2 Input of audit and assessment 8.3 Requirements for audit and assessment 9 Software unit verification 9.1 Objective 9.2 Input of audit and assessment 9.3 Requirements for audit and assessment 10 Software integration and verification 10.1 Objective 10.2 Input of audit and assessment 10.3 Requirements for audit and assessment 11 Embedded software testing 11.1 Objective 11.2 Input of audit and assessment 11.3 Requirements for audit and assessment 12 Software calibration and configuration management 12.1 Objectives 12.2 Input of audit and assessment 12.3 Requirements for audit and assessment 13 Software component identification 13.1 Objective 13.2 Input of audit and assessment 13.3 Requirements for audit and assessment Annex A (Informative) Software development environment Annex B (Informative) Software security requirement Annex C (Informative) Software architecture design specification Annex D (Information) Software unit design and implementation Annex E (Informative) Software unit verification Annex F (Informative) Software integration and verification Annex G (Informative) Embedded software testing Annex H (Informative) Software calibration and configuration management Annex I (Informative) Software component identification
