Safe solution for the Configurable Software challenge
ISO 26262 (Part 6, Annex C) specifies the test requirements for a Configurable Software.
A Configurable Software’s feature set and behaviour is dependent on its Configuration data (parameters that influence the compilation results) and Calibration data (parameters that influence the compiled software behaviour). Most developed software ends up fitting this definition, so most organizations that develop software for the automotive domain need to comply with the directives of Annex C.
The standard proposes two ways to validate such software, but the text is hard to understand and needs explaining. Once it is understood, it becomes clear that meeting the standard’s requirements may call for testing an unrealistic number of SW/HW combinations.
Avoiding this huge test effort is possible, if one can present a justifiable strategy for SW/HW combinations selection.
The lecture first explains the standard: what the various terms mean and what options the standard’s suggests for validation of the configurable software. This will make the challenges posed by the standard apparent: compliance require testing a very large number of SW/HW combinations.
The lecture then propose a well thought out, yet quite generic strategy for the selection of justifiable sub-set of HW/SW combinations to be used in testing.
During 2017, Michael was involved in defining work methodologies for compliance with ISO 26262.
In this role, he defines testing strategies and work methodologies for test teams, and sometimes even gets to test something himself – which he enjoys most.
Michael presented papers in local and international conferences and is teaching SW Testing in the Hebrew University in Jerusalem. You can view his papers and presentations at www.testprincipia.com.