1. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 12 February 1999 Its not the model - its what you do Its not the model - its what you do SPIN-UK, 2 February 1999

2. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 22 February 1999 Contents Characteristics of s/w process models Using models Change - approaches and strategies for SPI Tools for change Summary

3. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 32 February 1999 Characteristics of s/w process models... Examples of models: –SPICE –CMM –Bootstrap –Trillium –ISO 9000-3

4. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 42 February 1999 …Characteristics of s/w process models... Models describe/prescribe what development practices are advisable They do not describe how

5. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 52 February 1999 …Characteristics of s/w process models Models tend to be: –generic –abstract (specifications rather than particulars) –static, or steady state* –conservative –well considered (easy to criticize, difficult to improve) * Abdel Hamid, Madnick ‘Software Project Dynamics’ model is a notable exception

6. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 62 February 1999

7. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 72 February 1999 Using the models... Models are used for: –comparison –emulation –sources of information and ideas

8. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 82 February 1999 …Using the models... Development Process Business Objective A Model comparison meets ?

9. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 92 February 1999 …Using the models... Used in business context –what are business requirements for s/w development? –how do these relate to model requirements? Need to know how to compare (assess, evaluate, audit) Need to know how to emulate (make changes) ‘Judgement’ is critical –indicates deficiencies

10. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 102 February 1999 …Using the models Judgement is required: –there is no equivalent to production engineering or production management for s/w –need to identify ‘appropriate technology’ distinguish state of practice from state of art keep it simple –need disinterested view of industry practices and cultures

11. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 112 February 1999

12. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 122 February 1999 Change - approaches to SPI... Top down –directed by model –directed by business need Bottom up –fix current development problems (these are not exclusive)

13. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 132 February 1999...Change - approaches to SPI... Top Down - directed by model Tools and tactics Framework for action (e.g. TCM) Planning (e.g. DevPIP) Assess (e.g CBA IPI) For visibility -metrics -assessment -QA Frameworks -PDCA -TCM -resource models -PI templates PI - Process Definition - work ‘upstream’ - piloting/rollout - models - ‘flat pack’ infrastructure

14. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 142 February 1999...Change - approaches to SPI... Top Down - directed by business objectives Tools and tactics Framework for action (e.g. TCM) Performance target (e.g. HP’s 10X) Business need (e.g reduce costs) For visibility -metrics -assessment -QA Frameworks -PDCA -TCM -resource models -PI templates PI - Process Definition - work ‘upstream’ - piloting/rollout - models - ‘flat pack’ infrastructure

15. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 152 February 1999...Change - approaches to SPI... 10X “We need similar gains in the quality of our software products to achieve the same excellent reputation for quality that our hardware products have earned. For this reason I an extending the commitment made for hardware to software…. “HP is to achieve a tenfold improvement in two key software quality measures in the next five years. The first measure is aimed at out design process; the second at our ability to solve problems once customers have our products in place. We will measure these improvements by... Post Release Defect Density - The total number of defects (KPRs) reported from any source, during the first twelve months after first shipment, divided by the size (KNCSS) of the product. This measure helps us to understand the effectiveness of our design and testing process and is in a format widely used in industry. “Open and Serious KPRs - The number of service requests classified as KPRs (Known Problem Reports) which have a severity of critical or serious which are not yet closed or signed off at the end of the month. This measure helps us to focus on the support process involved in providing permanent solutions to severe customer problems.” John Young HP’s CEO, 24 April 1986

16. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 162 February 1999...Change - approaches to SPI... Bottom Up - e.g. PIRL Tools and tactics Focus for PI (e.g. SEPG) PIR’sDevelopment For visibility -metrics -assessment -QA Frameworks -PDCA -TCM -resource models -PI templates PI Process Definition work ‘upstream’ piloting/rollout models ‘flat pack’ infrastructure ‘quick fixes’ trends and issues

17. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 172 February 1999...Change - approaches to SPI... Top Down - directed by model Strengths –available ‘off the shelf’ –others have done it Weaknesses –may not address real issues –expensive –takes time –high risk

18. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 182 February 1999...Change - approaches to SPI... Top Down - directed by business objectives Strengths –meets business needs –generates commitment Weaknesses –novel

19. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 192 February 1999...Change - approaches to SPI... Bottom Up Strengths –addresses real developer needs –quick –cheap –effective –low risk Weaknesses –does not explicitly address business needs.

20. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 202 February 1999

21. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 212 February 1999 Tools... There are numerous tools and tactics for SPI They can be classified (loosely) into three types –Visibility –Frameworks for change –Analysis and production

22. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 222 February 1999 …Tools... Visibility Provide visibility and understanding of development processes Examples: –Quality Assurance –Measurement –Assessment

23. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 232 February 1999 …Tools... Frameworks for change Provide a secure, repeatable infrastructure for SPI activities Improve the probability of rapid completion of tasks Examples: –PDCA –TCM –PI templates –Grady - ‘spiral’

24. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 242 February 1999 …Tools Analysis and production tools Develop artefacts Build understanding and consensus Examples: –process definition –PIRs –‘7 tools’ –‘upstream’ analysis –piloting and roll-out –‘flat pack’ infrastructure, etc...

25. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 252 February 1999

26. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 262 February 1999 Summary Models are useful as static generic specifications Models can be used for comparison and emulation They do not address business needs or show how to make changes Strategies tactics and tools for change are being developed Select elements to build effective SPI strategy equipped with useful tools

27. OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 272 February 1999 O X F O R D S O F T W A R E E N G I N E E R I N G L I M I T E D 9 Spinners Court, 53 West End, Witney, Oxfordshire OX8 6 NS tel. +44 (0) 1993 700878 email shelley@osel.netkonect.co.ukshelley@osel.netkonect.co.uk www.osel.co.uk