|
|
系统确认计划 模板发表时间:2023-10-12 15:15 备注:本文档仅用于学习知识传播,如有侵权请联系我们删除!
<insert project name>
Document Control Information
Location: The version of this document is maintained in folder <fill in folder location>
Revision History
Table 1 : Version History
Table of Contents
Contents 1.3Definitions, Acronyms, and Abbreviations 2.2Further supporting Information 3Safety Strategy and Processes 3.3Safety Validation (Item development life cycle) 3.5Safety Organization and R&R 5Project Development and Validation schedule 5.1.1HARA Controllability Validation 5.3Validation method for safety goal 6Test Case and Acceptance Criteria
List of Figures
Figure 1 :
List of Tables
1 Introduction
1.1 Purpose
Validation Plan is planning document which plans validation performance for integrated item at Vehicle level. After HW, SW development, the hardware and software elements are integrated and tested to form an item that is then integrated into a vehicle. Once integrated at the vehicle level, safety validation is performed to provide evidence of functional safety with respect to the safety goals.
Therefore the Validation Plan describes all validation activities which shall be carried out for this IWV project. It is fully compliant to the requirements of ISO 26262 Part4 paragraph 5.4.2, 6.4.6 and 9.4.2.
The objective of Safety Validation is described in ISO 26262.
The first objective is to provide evidence of compliance with the safety goals and that the functional safety concepts are appropriate for the functional safety of the item.
The second objective is to provide evidence that the safety goals are correct, complete and fully achieved at the vehicle level.
1.2 Scope
This plan is useful for validation activities which should be performed at vehicle level by IWV Development Project. This document describes the following information for IWV validation: Ythe configuration of the item subjected to validation Ythe calibration of the item subjected to validation YValidation procedures Ytest cases Ydriving maneuvers Yacceptance criteria Ythe equipment and required environmental conditions.
1.3 Definitions, Acronyms, and Abbreviations
All terms, acronyms and abbreviations which are required to correctly interpret this document are listed as follows.
Table 2 : Terms
Table 3 : Acronyms & Abbreviations
2 Inputs and Output
2.1 Prerequisition
The following information shall be available.
- Safety Plan - Item Definition - Hazard Analysis & Risk Assessment - Safety Goal - Functional Safety Concept - Validation plan (refined)
2.2 Further supporting Information
The following information may be considered
- Project plan - Technical Safety Concept - Functional Concept (from external source) - Item Integration and Testing Plan - Safety Analysis Reports
2.3 Outputs
The following is the deliverable from this phase
- Validation Report
3 Safety Strategy and Processes
3.1 Overview
The Validation Plan is a requirement of the Automotive Functional Safety Standard ISO 26262. Internal and external safety inspectors may use this System Validation Plan as the basis for assessing how and to what extent safety-related issues have been addressed and treated during development of a safety critical system in the automotive domain.
3.2 Validation Test objectives
Validation plan must satisfy the following requirements: - The safety activities for the product development at the system level shall be planed including determination of appropriate methods and measures during design and integration (5.4.1) - The validation activities shall be planned (5.4.2)
3.3 Safety Validation (Item development life cycle)
Following figure shows that when it must be performed according to safety activity cycle for Safety Validation. Timing for performing according to safety activity cycle for Safety Validation is shown in figure 4-3.
3.4 Validation Processes
The safety goals of the item shall be validated at the vehicle level by evaluating the controllability, effectiveness of safety measures, external measures and other technologies. And the results of the validation shall be evaluated. Validation process is like below.
Validation Start
- Operating scenario - Intended use - Foreseeable misuse - Safety Measure - External Measure - Other Technology - Positive test of Function - Fault Injection Test - Simulation - Fleet Test - User test under real-life condition
Result Evaluation
Validation Report
3.5 Regression strategyRegression test shall be required the quality and performance improvement in case of vehicle structure, mounting position and vehicle communication load changes.
Table 5 : Regression strategy
4 Item Description
4.1 Item overview
4.1.1 System Component
Figure 3 : Sketch of <fill in system name>
4.1.2 Safety Goal of <fill in system name>
The safety goals for validation test are listed in the following table. SPF shall be documented by reference of FMEA, FTA analysis report.
Table 6 Safety goal of <fill in system name>
4.2 Configuration
Validation tester shall check configuration of IWV through scanning tool before testing
Table 6 Configuration Data
4.3 Calibration
For domestic market, IWV shall use calibration data for domestic market; IWV shall use calibration data for EU and general market because the structure of vehicle is different according to market. Therefore validation tester shall check calibration ID through scanning tool before testing.
Table 7 Calibration Data
5 Project Development and Validation schedule
5.1 Validation Test Plan
5.1.1 HARA Controllability Validation
In case of HARA performance, Severity, Exposure, Controllability shall be driven by stated critera and other brain-storming on criteria. At this time, high ASIL C,D to allocate for Controllability rating shall be needed to verify the rating validity through vehicle test. The validation test such as this Controllability shall be performed in the initial development, detail content and test case shall be specified in 7. Test case clause.
Description of the performance period of Controllability validation test
5.1.2 Safety Goal Validation
The final goal of validation is to verify that safety goal shall be accurately implemented at the vehicle level. The evaluation period is (TBD). Test case shall be completed and sample shall be prepared until (TBD).
5.1.3 Long-term test
The durability test of Safety Goal shall be verified through long-term test. The implementation period is (TBD).
5.2 Test Methods information
Table 8 : Information related with Validation test
Pass/fail criteria and test procedure are regulated in test case.
5.3 Validation method for safety goal
Table 9 : Safety Goal Validation
6 Test Case and Acceptance Criteria
Pass/fail criteria and test procedure are regulated in test case.
7 References
Table 10 : References
(NOTE) Basically, each referenced document should be listed by specifying the document name, version number, and date. A reference document which is continuously and frequently updated within the project, however, does not need to specify the version and date. If the version and date for a reference document are missing, it means the latest baseline version for that document has been referred to. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||