Sei sulla pagina 1di 48

Safety and Reliability Engineering

Part 2: Terminology
Prof. Dr.-Ing. Stefan Kowalewski
Chair Informatik XI, Embedded Software Laboratory
RWTH Aachen University
Summer term 2006
Terminology 1: Reliability
Reliability is the property which describes how much we
can expect the system to fulfill its specified function under
certain conditions (time period, environment conditions)
Safety and Reliability Engineering
Part 2: Terminology, Slide 2
Stefan Kowalewski, 28 April 2005
Terminology 1: Reliability
Reliability is the property which describes how much we
can expect the system to fulfill its specified function under
certain conditions (time period, environment conditions)
A failure is an event at which the system stops to fulfill its
specified function.
Safety and Reliability Engineering
Part 2: Terminology, Slide 3
Stefan Kowalewski, 28 April 2005
Terminology 1: Reliability
Reliability is the property which describes how much we
can expect the system to fulfill its specified function under
certain conditions (time period, environment conditions)
A failure is an event at which the system stops to fulfill its
specified function.
- Does this always happen immediately?
- Difference to defect, fault, error?
Safety and Reliability Engineering
Part 2: Terminology, Slide 4
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
Graphics: Marko Auerswald, Bosch
Safety and Reliability Engineering
Part 2: Terminology, Slide 5
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 6
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
unremoved
defect
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 7
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
unremoved
defect
fault 1
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 8
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
unremoved
defect
fault 1
component
failure 1
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 9
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 10
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 11
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
component
failure 2
system
failure 2
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 12
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
component
failure 2
system
failure 2
Defect
(deutsch: Defekt)
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 13
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
component
failure 2
system
failure 2
Fault/Error
(deutsch: Fehler)
Defect
(deutsch: Defekt)
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 14
Stefan Kowalewski, 28 April 2005
Reliability: Cause-Effect-Model
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
component
failure 2
system
failure 2
Fault/Error
(deutsch: Fehler)
Defect
(deutsch: Defekt)
Failure
(deutsch: Ausfall, Versagen)
Graphics: Marko Auerswald, Bosch
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 15
Stefan Kowalewski, 28 April 2005
Cause-Effect model: example
fault 2
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
component
failure 2
system
failure 2
Fault/Error
(deutsch: Fehler)
Defect
(deutsch: Defekt)
Failure
(deutsch: Ausfall, Versagen)
introduction
of defect
wrong expr.
for calcul.
array bound
wrong expr.
for calcul.
array bound
writing
beyong
array bound
incorrect
return
value
wrong
measurem.
result
memory
corruption
component
crash
system
crash
Safety and Reliability Engineering
Part 2: Terminology, Slide 16
Stefan Kowalewski, 28 April 2005
Graphics: Marko Auerswald, Bosch
Access points to improve reliability
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
component
failure 2
system
failure 2
introduction
of defect
Safety and Reliability Engineering
Part 2: Terminology, Slide 17
Stefan Kowalewski, 28 April 2005
Graphics: Marko Auerswald, Bosch
Access points to improve reliability
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
component
failure 2
system
failure 2
introduction
of defect
defect
avoidance
Safety and Reliability Engineering
Part 2: Terminology, Slide 18
Stefan Kowalewski, 28 April 2005
Graphics: Marko Auerswald, Bosch
Access points to improve reliability
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
component
failure 2
system
failure 2
introduction
of defect
defect
avoidance
defect
removal
Safety and Reliability Engineering
Part 2: Terminology, Slide 19
Stefan Kowalewski, 28 April 2005
Graphics: Marko Auerswald, Bosch
Access points to improve reliability
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
component
failure 2
system
failure 2
introduction
of defect
defect
avoidance
defect
removal
side effect
avoidance
Safety and Reliability Engineering
Part 2: Terminology, Slide 20
Stefan Kowalewski, 28 April 2005
Graphics: Marko Auerswald, Bosch
Access points to improve reliability
Development/Maintenance Operation/Runtime
unremoved
defect
system
failure 1
fault 1
component
failure 1
fault 2
component
failure 2
system
failure 2
introduction
of defect
defect
avoidance
defect
removal
side effect
avoidance
fault tolerance
Safety and Reliability Engineering
Part 2: Terminology, Slide 21
Stefan Kowalewski, 28 April 2005
Graphics: Marko Auerswald, Bosch
Defect, fault, error
Defect: Cause of an error/fault
Error/fault: State of the system in which defect is existing and failure
is possible to occur.
Beware: Many different definitions are used.
Sometimes: defect = fault error
Safety and Reliability Engineering
Part 2: Terminology, Slide 22
Stefan Kowalewski, 28 April 2005
Failure vs. fault/error
Failure: system view (black box)
Error/fault: subsystem structure view (white box)
Safety and Reliability Engineering
Part 2: Terminology, Slide 23
Stefan Kowalewski, 28 April 2005
Fault tolerance?
Safety and Reliability Engineering
Part 2: Terminology, Slide 24
Stefan Kowalewski, 28 April 2005
Systematic vs. random failures
Systematic failure
Deterministic relation between stimulus and failure
If a certain stimulus/usage of the system leads to a failure, it will
always do so.
Systematic failures are repeatable.
Safety and Reliability Engineering
Part 2: Terminology, Slide 25
Stefan Kowalewski, 28 April 2005
Systematic vs. random failures
Systematic failure
Deterministic relation between stimulus and failure
If a certain stimulus/usage of the system leads to a failure, it will
always do so.
Systematic failures are repeatable.
Examples?
Safety and Reliability Engineering
Part 2: Terminology, Slide 26
Stefan Kowalewski, 28 April 2005
Systematic vs. random failures
Random failure
also accidental failure
Nondeterministic relation between stimulus and failure
The same stimulus/usage of the system may either lead to correct
response or to a failure.
Random failures are not repeatable.
Safety and Reliability Engineering
Part 2: Terminology, Slide 27
Stefan Kowalewski, 28 April 2005
Systematic vs. random failures
Random failure
also accidental failure
Nondeterministic relation between stimulus and failure
The same stimulus/usage of the system may either lead to correct
response or to a failure.
Random failures are not repeatable.
Examples?
Safety and Reliability Engineering
Part 2: Terminology, Slide 28
Stefan Kowalewski, 28 April 2005
Systematic vs. random failures
Typical causes for systematic failures?
Safety and Reliability Engineering
Part 2: Terminology, Slide 29
Stefan Kowalewski, 28 April 2005
Systematic vs. random failures
Typical causes for systematic failures?
specification errors
constructive faults
Safety and Reliability Engineering
Part 2: Terminology, Slide 30
Stefan Kowalewski, 28 April 2005
Systematic vs. random failures
Typical causes for systematic failures?
specification errors
constructive faults
Typical causes for random failures?
Safety and Reliability Engineering
Part 2: Terminology, Slide 31
Stefan Kowalewski, 28 April 2005
Systematic vs. random failures
Typical causes for systematic failures?
specification errors
constructive faults
Typical causes for random failures?
aging, wear-out
destruction
Safety and Reliability Engineering
Part 2: Terminology, Slide 32
Stefan Kowalewski, 28 April 2005
Systematic vs. random failures
Typical causes for systematic failures?
specification errors
constructive faults
Typical causes for random failures?
aging, wear-out
destruction
Which class:
Hardware failures?
Software failures?
Safety and Reliability Engineering
Part 2: Terminology, Slide 33
Stefan Kowalewski, 28 April 2005
Failure rate
Reliability of a system is often specified by the failure rate .
= failures per time unit (in a collection of systems)
Safety and Reliability Engineering
Part 2: Terminology, Slide 34
Stefan Kowalewski, 28 April 2005
Failure rate
Reliability of a system is often specified by the failure rate .
= failures per time unit (in a collection of systems)
For most technical products (incl. embedded systems),
(t) is a bath-tub curve:
Safety and Reliability Engineering
Part 2: Terminology, Slide 35
Stefan Kowalewski, 28 April 2005
Bath-tub curve (ctd.)
Does the bath-tub also apply to software-failures?
Safety and Reliability Engineering
Part 2: Terminology, Slide 36
Stefan Kowalewski, 28 April 2005
Bath-tub curve (ctd.)
Consequences of bath-tub curve for manufacturers who want to
increase the reliability of their product?
Safety and Reliability Engineering
Part 2: Terminology, Slide 37
Stefan Kowalewski, 28 April 2005
Reliability vs. costs
Manufacturers dont want to increase reliability but minimize costs.
They have to find the optimal trade-off between pre- and post-
shipment costs:
Safety and Reliability Engineering
Part 2: Terminology, Slide 38
Stefan Kowalewski, 28 April 2005
Safety vs. costs
Trade-off considerations are ethically doubtful when safety is involved!
Safety and Reliability Engineering
Part 2: Terminology, Slide 39
Stefan Kowalewski, 28 April 2005
Safety vs. costs
Trade-off considerations are ethically doubtful when safety is involved!
Example: Ford Pinto Desaster (http://www.fordpinto.com/blowup.htm)
- Pinto was Fords answer to VW and Japanese small size cars in
the 60s.
- Soon defect became apparent: weak gas tank, burning casualties
in rear end collisions.
Safety and Reliability Engineering
Part 2: Terminology, Slide 40
Stefan Kowalewski, 28 April 2005
Safety vs. costs
Trade-off considerations are ethically doubtful when safety is involved!
Example: Ford Pinto Desaster (http://www.fordpinto.com/blowup.htm)
- Pinto was Fords answer to VW and Japanese small size cars in
the 60s.
- Soon defect became apparent: weak gas tank, burning casualties
in rear end collisions.
- Cost/benefit analysis by Ford for correcting the flaw:
Costs: $11 per car $137 million
Benefit: 180 avoided deaths ($200.000 each), 180 avoided burn
injuries ($67.000 each), 2100 burned cars ($700 each) $49.5 million
Safety and Reliability Engineering
Part 2: Terminology, Slide 41
Stefan Kowalewski, 28 April 2005
Safety vs. costs
Trade-off considerations are ethically doubtful when safety is involved!
Example: Ford Pinto Desaster (http://www.fordpinto.com/blowup.htm)
- Pinto was Fords answer to VW and Japanese small size cars in
the 60s.
- Soon defect became apparent: weak gas tank, burning casualties
in rear end collisions.
- Cost/benefit analysis by Ford for correcting the flaw:
Costs: $11 per car $137 million
Benefit: 180 avoided deaths ($200.000 each), 180 avoided burn
injuries ($67.000 each), 2100 burned cars ($700 each) $49.5 million
- They left it as it was. (Lee Iacocca: Safety doesnt sell)
- In 1978 Ford was forced by the Dept of Transportation to recall 1.5
million Pintos.
Safety and Reliability Engineering
Part 2: Terminology, Slide 42
Stefan Kowalewski, 28 April 2005
Safety
Safety?
Safety and Reliability Engineering
Part 2: Terminology, Slide 43
Stefan Kowalewski, 28 April 2005
Safety
Safety:
The property of a situation, in which the risk of
operating/using a system does not exceed the limit risk.
Safety and Reliability Engineering
Part 2: Terminology, Slide 44
Stefan Kowalewski, 28 April 2005
Safety
Safety:
The property of a situation, in which the risk of
operating/using a system does not exceed the limit risk.
Risk?
Safety and Reliability Engineering
Part 2: Terminology, Slide 45
Stefan Kowalewski, 28 April 2005
Safety
Safety:
The property of a situation, in which the risk of
operating/using a system does not exceed the limit risk.
Risk:
A measure comprising
- the probability of an event leading to damage
- the expected amount of damage, if the event occurs
Safety and Reliability Engineering
Part 2: Terminology, Slide 46
Stefan Kowalewski, 28 April 2005
Safety
Safety:
The property of a situation, in which the risk of
operating/using a system does not exceed the limit risk.
Risk:
A measure comprising
- the probability of an event leading to damage
- the expected amount of damage, if the event occurs
If quantification is possible:
R = P
damage
A
damage
Safety and Reliability Engineering
Part 2: Terminology, Slide 47
Stefan Kowalewski, 28 April 2005
Safety
R = P
damage
A
damage
Safety and Reliability Engineering
Part 2: Terminology, Slide 48
Stefan Kowalewski, 28 April 2005

Potrebbero piacerti anche