eXpress

  Help

×
Menu
Index
 

Detect Malfunctions with Fewest Tests

Feature Description

 

What is the purpose of this algorithm?

 
The Detect Malfunctions with Fewest Tests fault detection algorithm attempts to provide the most direct path to a detected failure. Assuming that the desire to detect failures using the fewest tests implies a certain sense of expediency, the Test Candidate Groupings for this algorithm dictate that all intrusive tests be postponed until all useful non-intrusive tests have been performed. Within these groupings, the Test Weightings are set up so that the test that is most likely to fail is selected first. In other words, the first test in the detection order will be the one that is most likely to fail (that is, most likely to detect a failure). The second test will be that which is most likely to fail, given that the first test did not. And so on.
 

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: Non-Intrusive Tests
          a) Candidate Test Types (4)
               1) All Operational Tests
               2) All User-Initiated Tests
               3) All Signature Tests
               4) Non-intrusive Inspection Tests
          b) Weightings: uses algorithm defaults
          c) Cutoffs: uses algorithm defaults
     2. Test Candidate Grouping 2 of 4: Intrusive Tests
          a) Candidate Test Types (2)
               1) All Probe Tests
               2) Intrusive Inspection Tests
          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)
               1) All Net Functions
          b) Weightings: uses algorithm defaults
          c) Cutoffs: uses algorithm defaults
     4. Test Candidate Grouping 4 of 4: Output Flags
          a) Candidate Test Types (1)
               1) All Output Flags
          b) Weightings: uses algorithm defaults
          c) Cutoffs: uses algorithm defaults
 
B. Default Test Weightings (8)
     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: Highest
     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: Highest
     3. Test Weighting 3 of 8: Sum Failure Probability
          a) Priority:         40
          b) Entity:           Failure Probability
          c) Type:            Sum
          d) Domain:        Suspect Functions Proven
          e) Best Equals: Highest
     4. Test Weighting 4 of 8: Sum Failure Probability
          a) Priority:         30
          b) Entity:           Failure Probability
          c) Type:            Sum
          d) Domain:        Suspect Failure Modes Proven
          e) Best Equals: Highest
     5. Test Weighting 5 of 8: Count Number of Functions
          a) Priority:         20
          b) Entity:           Number of Functions
          c) Type:            Count
          d) Domain:        Suspect Functions Detected
          e) Best Equals: Highest
     6. Test Weighting 6 of 8: Count Number of Failure Modes
          a) Priority:         15
          b) Entity:           Number of Failure Modes
          c) Type:            Count
          d) Domain:        Suspect Failure Modes Detected
          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)