1. 1 Introducing Bayesian Nets in AgenaRisk An example based on Software Defect Prediction

2. Typical Applications Predicting reliability of critical systems Software defect prediction Aircraft accident traffic risk Warranty return rates of electronic parts Operational risk in financial institutions Hazards in petrochemical industry

3. Typical Applications Predicting reliability of critical systems Software defect prediction Aircraft accident traffic risk Warranty return rates of electronic parts Operational risk in financial institutions Hazards in petrochemical industry

4. Typical Applications Predicting reliability of critical systems Software defect prediction Aircraft accident traffic risk Warranty return rates of electronic parts Operational risk in financial institutions Hazards in petrochemical industry

5. Typical Applications Predicting reliability of critical systems Software defect prediction Aircraft accident traffic risk Warranty return rates of electronic parts Operational risk in financial institutions Hazards in petrochemical industry

6. Typical Applications Predicting reliability of critical systems Software defect prediction Aircraft accident traffic risk Warranty return rates of electronic parts Operational risk in financial institutions Hazards in petrochemical industry

7. Typical Applications Predicting reliability of critical systems Software defect prediction Aircraft accident traffic risk Warranty return rates of electronic parts Operational risk in financial institutions Hazards in petrochemical industry

8. A Bayesian Net for predicting air traffic incidents

9. A Detailed Example What follows is a demo of a simplified version of a Bayesian net model to provide more accurate predictions of software defects Many organisations worldwide have now used models based around this one

10. Predicting software defects Operational defects The number of operational defects (i.e. those found by customers) is what we are really interested in predicting

11. Residual Defects Operational defects We know this is clearly dependent on the number of residual defects. Predicting software defects

12. Residual Defects Operational defectsOperational usage But it is also critically dependent on the amount of operational usage. If you do not use the system you will find no defects irrespective of the number there. Predicting software defects

13. Residual Defects Defects IntroducedOperational defectsOperational usage Predicting software defects The number of residual defects is determined by the number you introduce during development….

14. Residual Defects Defects found and fixed Defects IntroducedOperational defectsOperational usage Predicting software defects …minus the number you successfully find and fix

15. Residual Defects Defects found and fixed Defects IntroducedOperational defectsOperational usage Obviously defects found and fixed is dependent on the number introduced Predicting software defects

16. Residual Defects Problem complexity Defects found and fixed Defects IntroducedOperational defectsOperational usage The number introduced is influenced by problem complexity… Predicting software defects

17. Residual Defects Problem complexity Defects found and fixed Defects Introduced Design process quality Operational defectsOperational usage ….and design process quality Predicting software defects

18. Residual DefectsTesting Effort Problem complexity Defects found and fixed Defects Introduced Design process quality Operational defectsOperational usage Finally, how many defects you find is influenced not just by the number there to find but also by the amount of testing effort Predicting software defects

19. A Model in action Here is that very simple model with the probability distributions shown

20. A Model in action We are looking at an individual software component in a system

21. A Model in action The prior probability distributions represent our uncertainty before we enter any specific information about this component.

22. A Model in action So the component is just as likely to have very high complexity as very low

23. A Model in action and the number of defects found and fixed in testing is in a wide range where the median value is about 20.

24. A Model in action As we enter observations about the component the probability distributions update

25. Here we have entered the observation that this component had 0 defects found and fixed in testing

26. Note how the other distributions changed.

27. The model is doing forward inference to predict defects in operation…..

28. ..and backwards inference to make deductions about design process quality.

29. but actually the most likely explanation is very low testing quality.

30. …and lower than average complexity.

31. But if we find out that the complexity is actually high…..

32. https://intranet.dcs.qmul.ac.uk/courses/coursenotes/DCS235/ then the expected number of operational defects increases

33. https://intranet.dcs.qmul.ac.uk/courses/coursenotes/DCS235/ and we become even more convinced of the inadequate testing

34. https://intranet.dcs.qmul.ac.uk/courses/coursenotes/DCS235/ So far we have made no observation about operational usage.

35. https://intranet.dcs.qmul.ac.uk/courses/coursenotes/DCS235/ If, in fact, the operational usage is high…

36. Then we have an example of a component with no defects in test..

37. …but probably many defects in operation.

38. But suppose we find out that the test quality was very high.

39. Then we completely revise out beliefs

40. We are now pretty convinced that the module will be fault free in operation

41. …And the ‘explanation’ is that the design process is likely to be very high quality

42. A Model in action we reset the model and this time use the model to argue backwards

43. A Model in action Suppose we know that this is a critical component that has a requirement for 0 defects in operation…

44. The model looks for explanations for such a state of affairs.

45. The most obvious way to achieve such a result is to not use the component much.

46. But if we know it will be subject to high usage…

47. Then the model adjusts the beliefs about the other uncertain variables.

48. A combination of lower than average complexity…..

49. …Higher than average design quality…..

50. and much higher than average testing quality …..

51. But suppose we cannot assume our testing is anything other than average…

52. Then better design quality …..

53. ..and lower complexity are needed …..

54. But if complexity is very high …..

55. …Then we are left with a very skewed distribution for design process quality.

56. What the model is saying is that, if these are the true requirements for the component then you are very unlikely to achieve them unless you have a very good design process

57. Making better decisions That was a simplified version of model produced for Philips Helped Philips make critical decisions about when to release software for electronic components 95% accuracy in defect prediction – much better than can be achieved by traditional statistical methods

58. Model Implementation In AgenaRisk www.agenarisk.com