and that details of all Identify and their level of modifications shall be competency documented, including references to: the Specification of the modification modification request; the result of the impact Planning of the verification of the analysis; software modification configuration management history; deviation from of revalidation and testing of the normal operations and modification to the extent required by conditions; all documented the SIL information affected by the modification activity; Modifications to the software have been re-verification and identified i.e. the revision control system revalidation of data contains information of the change, what results. was changed and when it was changed. All modifications are recorded 39 Verification To ensure that the 7.9.2.1, For all safety integrity levels ensure that planning verification of software is 7.9.2.2 there is evidence that: planned concurrently with the development for each For each phase of development (design phase of the software and coding) that verification activities safety lifecycle and this have been planned. Evidence of planned reviews for these phases is sufficient. information shall be documented, and that the planning refers to the criteria, techniques and tools to be used in the verification activities 40 Verification of To ensure that verification 7.9.2.3, For all safety integrity levels ensure that the software of the software is 7.9.2.4, there is evidence that: (general) performed at each stage 7.9.2.5,
and that details of all modifications shall be documented, including references to: the modification request; the result of the impact analysis; software configuration management history; deviation from normal operations and conditions; all documented information affected by the modification activity; re-verification and revalidation of data results. Identify and their level of competency Specification of the modification Planning of the verification of the modification of revalidation and testing of the modification to the extent required by the SIL Modifications to the software have been identified i.e. the revision control system contains information of the change, what was changed and when it was changed. All modifications are recorded 39 Verification planning To ensure that the verification of software is planned concurrently with the development for each phase of the software safety lifecycle and this information shall be documented, and that the planning refers to the criteria, techniques and tools to be used in the verification activities 7.9.2.1, 7.9.2.2 For all safety integrity levels ensure that there is evidence that: For each phase of development (design and coding) that verification activities have been planned. Evidence of planned reviews for these phases is sufficient. 40 Verification of the software (general) To ensure that verification of the software is performed at each stage 7.9.2.3, 7.9.2.4, 7.9.2.5, For all safety integrity levels ensure that there is evidence that:
CASS_TOES_for_software_assessment_IEC_61508-3_2010_-_ABRIDGED_v1.docx