When a tool is utilized in the development of ADF, it’s crucial to have confidence in the selected tool’s use. For software, this confidence is established if the tool effectively reduces the risk of systematic errors in the product being developed, and both the development process and the tool adhere to the processes of (ISO 26262-1-12, 2018) and SOTIF (ISO 21448, 2022).
To evaluate the confidence of a software tool in the development the following criteria shall be considered:
- The possibility that a malfunctioning software tool could produce erroneous outputs, which could take it in turns;
- Introduce errors in the function being developed;
- Prevent errors in the function being developed to be detected, and
- The confidence in preventing or detecting such errors in the output
The evaluation considers two primary aspects: tool usage and tool qualification. The former is based on the tool’s necessary functions and properties, taking into account its appropriate usage in the user environment. The latter is conducted based on provided or assumed information about the tool’s usage (e.g., use cases, user requirements, Automotive Safety Integrity Level (ASIL)).
A Tool Confidence Level (TCL) can be determined based on these aspects. If certification is required, qualification methods are applied as per ISO 26262-1-12 (2018).
Main Question
Do the selected development tools satisfy quality and safety standards and requirements?
Sub-Questions
- Do the selected development tools effectively reduce the risk of systematic errors in the product being developed?
- Are the tool’s necessary functions and properties considered in its usage in the user environment?
References
- ISO (2018) 26262-1-12: Road vehicles — Functional safety part 1-12, Part 1 availabe at: https://www.iso.org/standard/68383.html (Accessed: 18 October 2023)
- ISO (2022) 21448: Road vehicles — Safety of the intended functionality. Available at: https://www.iso.org/standard/77490.html (Accessed: 18 October 2023)