33 Execution of To ensure the validation 7.7.2.2 For all safety integrity levels ensure that software activities are carried out as there is evidence that: aspects of specified during software There is a (set of) precisely defined system safety safety validation planning validation and that testing is the validation configuration(s) main validation method for software; animation and There are recorded software validation test results. modelling may be used to supplement the validation activities. There are operational profile coverage targets defined, justified and met (R2 for 3+) 34 Recording of To ensure the software 7.7.2.4, For all safety integrity levels ensure that results of the validation activities are 7.7.2.5, there is evidence that: software documented in order to 7.7.2.6, safety record that the specified 7.7.2.7, The software validation test results have validation functions for software 7.7.2.8, a revision number. safety are correctly 7.7.2.9 performed, that the The software validation test results are software system does not dated. perform unintended The software validation test results functions, the test cases and their results and if identify the individuals who performed failed the reason for failure the testing. The software validation test results identify any test environment/equipment used. Only validated/approved test that satisfy ToE 18 (para 7.4.4) shall be used
33 Execution of software aspects of system safety validation To ensure the validation activities are carried out as specified during software safety validation planning and that testing is the main validation method for software; animation and modelling may be used to supplement the validation activities. 7.7.2.2 For all safety integrity levels ensure that there is evidence that: There is a (set of) precisely defined validation configuration(s) There are recorded software validation test results. There are operational profile coverage targets defined, justified and met (R2 for 3+) 34 Recording of results of the software safety validation To ensure the software validation activities are documented in order to record that the specified functions for software safety are correctly performed, that the software system does not perform unintended functions, the test cases and their results and if failed the reason for failure 7.7.2.4, 7.7.2.5, 7.7.2.6, 7.7.2.7, 7.7.2.8, 7.7.2.9 For all safety integrity levels ensure that there is evidence that: The software validation test results have a revision number. The software validation test results are dated. The software validation test results identify the individuals who performed the testing. The software validation test results identify any test environment/equipment used. Only validated/approved test that satisfy ToE 18 (para 7.4.4) shall be used
CASS_TOES_for_software_assessment_IEC_61508-3_2010_-_ABRIDGED_v1.docx