Prove Maximum Operation Before Detecting Malfunction
Feature Description
What is the purpose of this algorithm?
The Prove Maximum Operation Before Detecting Malfunction fault detection algorithm attempts to prove good as much of the design as possible before detecting a failure (so that, if multiple-fault isolation is used, better isolation can be achieved once a fault is detected). Unlike many of the other detection algorithms, this algorithm does not distinguish between intrusive and non-intrusive tests (although it does use Test Candidate Groupings to postpone Probe Tests until all other types of tests have been performed). The assumption here is that the Analyst is willing to perform additional or less convenient testing in exchange for better fault isolation.
How was this algorithm implemented?
The following outline describes the full set of test selection criteria defined by this algorithm.
1. Test Candidate Grouping 1 of 4: BIT Tests
a) Candidate Test Types (4)
b) Weightings: uses algorithm defaults
c) Cutoffs: uses algorithm defaults
2. Test Candidate Grouping 2 of 4: Intrusive Tests
a) Candidate Test Types (1)
b) Weightings: uses algorithm defaults
c) Cutoffs: uses algorithm defaults
3. Test Candidate Grouping 3 of 4: Individual Net Functions
a) Candidate Test Types (1)
b) Weightings: uses algorithm defaults
c) Cutoffs: uses algorithm defaults
4. Test Candidate Grouping 4 of 4: Output Flags
a) Candidate Test Types (1)
b) Weightings: uses algorithm defaults
c) Cutoffs: uses algorithm defaults
1. Test Weighting 1 of 8: Sum Failure Probability
a) Priority: 80
b) Entity: Failure Probability
c) Type: Sum
d) Domain: Suspect Functions Detected
e) Best Equals: Lowest
2. Test Weighting 2 of 8: Sum Failure Probability
a) Priority: 60
b) Entity: Failure Probability
c) Type: Sum
d) Domain: Suspect Failure Modes Detected
e) Best Equals: Lowest
3. Test Weighting 3 of 8: Count Number of Functions
a) Priority: 40
b) Entity: Number of Functions
c) Type: Count
d) Domain: Suspect Functions Detected
e) Best Equals: Lowest
4. Test Weighting 4 of 8: Count Number of Failure Modes
a) Priority: 30
b) Entity: Number of Failure Modes
c) Type: Count
d) Domain: Suspect Failure Modes Detected
e) Best Equals: Lowest
5. Test Weighting 5 of 8: Sum Failure Probability
a) Priority: 20
b) Entity: Failure Probability
c) Type: Sum
d) Domain: Suspect Functions Proven
e) Best Equals: Highest
6. Test Weighting 6 of 8: Sum Failure Probability
a) Priority: 15
b) Entity: Failure Probability
c) Type: Sum
d) Domain: Suspect Failure Modes Proven
e) Best Equals: Highest
7. Test Weighting 7 of 8: Count Number of Functions
a) Priority: 10
b) Entity: Number of Functions
c) Type: Count
d) Domain: Suspect Functions Proven
e) Best Equals: Highest
8. Test Weighting 8 of 8: Count Number of Failure Modes
a) Priority: 5
b) Entity: Number of Failure Modes
c) Type: Count
d) Domain: Suspect Failure Modes Proven
e) Best Equals: Highest
C. Default Test Cutoffs (0)
