This presentation has been given in 2003 at the Spider Conference to show how CMM could contribute to the business results of a large organization within Philips

1. Translating the business needs into an improvement programme using CMM: a practical experience within PHILIPS TV Guy Van Hooveld Thanks to Hans Aerts, Baudewyn Meersseman and Geert Acke for some of the presentation material

6. High End Market High End products, High End expectations and targets

9. Field call rate : what is acceptable? 4 Cylinders + 25.000 € 6 Cylinders + 40.000 € 8 Cylinders + 70.000 € 3 5 7 The higher the price, the higher the complexity, the higher the potential failure modes… ?

11. Field call rate: what about this...? Standard HIGH END Flat 16Kb SW 200 € 64Kb SW/ 50 Hz. 600 € 2Mb+ SW/100 Hz. 1200 € to 8000 € Portable The higher the price, the higher the complexity, the higher the potential failure modes… ?

13. Software Performance Improvement SW Introduction Feature Expansion Mastering Complexity Open Systems Process Organization Product People Technology Architecture

14. Improvement Requirements per Stage Evolution in Embedded SW Development

15. How much software does a shaver contain ? Telephone exchange: 1975: 256 Kbytes 1990: 80 Mbytes High-end TV: 1985: 8 Kbytes 2000: 2 Mbytes Shaver: 2000: 4 Kbytes 2015: ?????

16. Software Growth 1 10 100 1000 10000 1985 1987 1989 1991 1993 1995 1997 1999 2001 Year Software Size (KBytes) TV VCR Double every 2 years

18. Evolution time slip Decision making made possible: predictibility is also predicting delay. Peak in 2000 ? Product was not on the critical path and had the appropriate quality. The potential delay was predictable and has been taken into account.

19. Evolution post release defects density

21. Correlation pre-post release defects We could expect a linear correlation, but reality shows that the number of post release defects is in fact more or less constant while complexity is growing .

32. Software Performance Improvement SW Introduction Feature Expansion Mastering Complexity Open Systems Process Organization Product People Technology Architecture

34. Different aspects are related High Architecture and Technology level Organization, Staff, and Process level problematic inefficient high risk target High Low

35. Balanced Software Performance Improvements High Architecture and Technology level Organization, Staff, and Process level problematic inefficient high risk target High Low SPI