programmable electronics, A software lifecycle change procedure any modification or change exists includes the criteria to be to the integrated system is applied by an impact analysis subject to an impact analysis that shall An impact analysis has been performed determine all the software on the software when a need for modules impacted and the modification has arisen necessary re-verification activities. The impact analysis information is held under configuration management. The impact analysis information is uniquely identifiable and traceable to a bug report / change request. An approval process exists for authorising modifications on completion of the impact analysis. Modification requests are recorded, dated, uniquely identified and reference impact analysis (the use of a bug tracking system is evidence of this e.g. Bugzilla). The impact analysis clearly identifies the area of the software to be changed. The impact analysis clearly identifies associated documentation to be changed. 32 To ensure the 7.5.2.7, For all safety integrity levels ensure that of results documenting of the test 7.5.2.8 is evidence that: cases and their expected
programmable electronics, any modification or change to the integrated system is subject to an impact analysis that shall determine all the software modules impacted and the necessary re-verification activities. A software lifecycle change procedure exists includes the criteria to be applied by an impact analysis An impact analysis has been performed on the software when a need for modification has arisen The impact analysis information is held under configuration management. The impact analysis information is uniquely identifiable and traceable to a bug report / change request. An approval process exists for authorising modifications on completion of the impact analysis. Modification requests are recorded, dated, uniquely identified and reference impact analysis (the use of a bug tracking system is evidence of this e.g. Bugzilla). The impact analysis clearly identifies the area of the software to be changed. The impact analysis clearly identifies associated documentation to be changed. 32 of results To ensure the documenting of the test cases and their expected 7.5.2.7, 7.5.2.8 For all safety integrity levels ensure that is evidence that:
CASS_TOES_for_software_assessment_IEC_61508-3_2010_-_ABRIDGED_v1.docx