Software qualification aims to ensure that safety- or security‑relevant software artefacts provide their intended features. These features must be verified and made traceable, down to elementary hardware functions, along a structured hierarchy. Importantly, qualification under standards such as ISO 26262 or ISO 21434 concerns not only the critical software running on the target hardware. For compliance, it must also be demonstrated that the tools used to develop, verify, trace, and deliver critical software do not introduce, or fail to detect, errors that could compromise guaranteed safety or security properties. Typical tools considered in a certification include compilers, static code analyzers, model‑based design environments, and test automation frameworks. However, the scope extends further to include reporting tools such as JIRA and version‑control systems like SVN or Git, as they, too, may influence the development process or the intended functioning of the critical software under assessment.

This talk clarifies the practitioner’s view on relevant safety standards, especially ISO 26262, and examines the implications for the toolchain used when developing critical software undergoing safety assessments. A particular focus is placed on tool qualification and the associated tool evaluation report, which ensures that all tools potentially affecting the development, verification, or validation of critical software artefacts are assessed according to their relevance and impact. 

Panelists