Scribd
Upload
17 views3 pages

Document (1)

Uploaded by

Sameer Patil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views3 pages

Document (1)

Uploaded by

Sameer Patil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

• Topic:- HOW TO DESIGN AND TEST SAFETY CRITICAL

SOFTWARE

Techniques for testing and verifying Safety Critical System


1 Probabilistic Risk Assessments (PRA).
Probabilistic Risk Assessment is a systematic methodology To evaluate risk
associated with a complex engineering Technologies entity (such as an airliner
or a nuclear power Plants). The steps involved in PRA for testing Safety Critical
System are:
1. Perform a primary hazard analysis to find out the Predefined hazard on
Safety Critical System.
2. The severity of each impact is calculated. The severity Levels can be
classified as
a. Catastrophic
b. Hazardous
c. Major
d. Minor
e. Not safety related.
3. The probability of occurrence is then calculated and it can Also be
classified as:
a. Probable
b. Remote
c. Extremely remote
d. Extremely improbable
4. The assessment of risk is calculated by combining both Impact and
probability of occurrence in matrix.
For this evaluation we use different risk criteria like riskcost trade-offs, risk
benefit of technological options, etc.
Risks that fall into the unacceptable category (e.g.: high Severity and high
probability), that is to say, are Unacceptable, must be mitigated by some means
such as Safeguards, redundancy, prevention and recovery Mechanisms, etc., to
reduce the level of safety risk. Probabilistic risk assessment also uses tools such
as cause And effect diagrams. For instance, HP applies these Techniques to
their patient monitors naming it as risk and Hazard analysis and they consider it
to be a grey box method.
2. Failure Modes and Effect Analysis (FMEA).
Failure modes and effect analysis (FMEA) is a procedure for Analysis of
potential failures within a system for Classification by severity or determination
of the effect of These failures on the system. Failure modes can be defined as
any errors or defects in a Process, design or item, especially those that affect the
Customer and can be potential or actual. Effects analysis Refers to studying the
consequences of these failures. Failure Modes, effects and criticality analysis
(FMECA) is an Extension to this procedure, which includes criticality Analysis
used to chart the probability of failures against the Severity of their
consequences.
3. Fault Tree Analysis (FTA).
Fault trees analysis is a graphical technique that provides a Systematic
description of the combinations of possible Occurrences in a system which can
result in an undesirable Outcome (failure). An undesired effect is taken as the
root of A tree of logic. Each situation that could cause that effect is Added to the
tree as a series of logic expressions. Events are Labelled with actual numbers
about failure probabilities. The Probability of the top level event can be
determined using Mathematical techniques.
FTA can be used to:
a) Understand the logic leading to the top event / Undesired state.
b) Show compliance with the (input) system safety / reliability requirements.
c) Prioritize the contributors leading to the top Event – Creating the Critical
Equipment/Parts/Events lists for different Importance measures.
d) Monitor and control the safety performance of The complex system.
e) Minimize and optimize resources.
f) Assist in designing a system. The FTA can be Used as a design tool that
helps to create (output / Lower level) requirements.
g) Function as a diagnostic tool to identify and Correct causes of the top
event.
CONCLUSIONS
A basic overview of safety-critical software systems has been given and some
standards to cope with the development of Safety Critical System are also
named. Programming features and languages related to these kinds of systems
have also been mentioned. Then, the two main approaches like Formal method-
based approach and Prevention and recovery-based approach; used when
designing safety-critical software were explained. Finally, some techniques used
to test safety critical software have been described, general techniques also used
to test typical software systems and special techniques from safety engineering
aimed at safety critical software. The main idea behind the testing techniques
mentioned is to reduce risks of implementation errors

REFERENCES:-
https://www.irjet.net/archives/V3/i9/IRJET

You might also like