40 likes | 150 Views
Potential for influencing standards and broadening collaboration. N. Thuy EDF R&D. Rule-based approaches vs. Claim-based approaches. Rule-based approaches rules that give (reasonable) assurance for given properties often: too rigid Claim-based approaches
E N D
Potential for influencing standardsand broadening collaboration N. ThuyEDF R&D
Rule-based approaches vs.Claim-based approaches • Rule-based approaches • rules that give (reasonable) assurance for given properties • often: too rigid • Claim-based approaches • may be necessary for specific, unanticipated, or new issues • example: the RID3 project (EPRI) WP3_edf036_v01_FISA_November 2003
RID3 • Risk Informed Defense in Depth and Diversity • for digital I&C upgrades • Evaluation of potential for digital Common Cause Failure • Example: use of the same digital I&C platform in several lines of defence • claim: the operating system software is an unlikely source of digital CCF • claim: the application function library is also an unlikely source WP3_edf036_v01_FISA_November 2003
Revision of IEC 61508 • Current standard • lists of (highly) recommended methods / techniques • no clear indication of what is to be achieved • Revised standard • identification of essential properties to be achieved at each stage of the system / software safety lifecycles • gradation of the rigour of evidence according to Safety Integrity Level (SIL) • development process, assessment, independent assessment • technical evidence, + objective acceptance criteria, + rigorous reasoning • recommendation of methods / techniques • that may be used to achieve these properties • that meet the expected level of rigour (SIL) WP3_edf036_v01_FISA_November 2003