1. CMPUT 402 - Software QualityMajor Software Strategies - 1 © Paul Sorenson MAJOR SW STRATEGIES BASED HEAVILY ON ROBERT GRADY'S BOOK “Practical Software Metrics for Project Management and Process Improvement”, Prentice-Hall 1996 What are the goals in developing successful software systems? We wish to develop systems that.... meet customer needs are reliable (perform well) are cost effective to build and evolve meet a product delivery schedule

2. CMPUT 402 - Software QualityMajor Software Strategies - 2 © Paul Sorenson GOAL DEVELOPMENT GOAL: Develop Successful Software Systems SG1: Maximize Customer Satisfaction SG3: Minimize Defects SG2: Minimize Engineering Effort and Schedule SG4: Minimize Time to Market

3. CMPUT 402 - Software QualityMajor Software Strategies - 3 © Paul Sorenson QUESTION GENERATION SG1: Maximize Customer Satisfaction Q1: What are the attributes of customer satisfaction? Q2: What are the key indicators of customer satisfaction? Q3: What aspects result in customer satisfaction? Q4: How satisfied are the customers? Q5: How do we compare with the competition? Q6: How many problems are affecting customers? Q7: How long does it take to fix a problem? (compared to customer expectn) Q8: How does installing a fix affect the customer? Q9: How many customers are affected by the problem? (by how much?) Q10: Where are the bottlenecks?

4. CMPUT 402 - Software QualityMajor Software Strategies - 4 © Paul Sorenson Q1: What are the attributes of customer satisfaction? F F unctionality U U sability R R eliability P P erformance S S upportability Feature Set CapabilitiesGeneralitySecurity Human Factors AestheticsConsistencyDocumentation Failure Freq. Failure Severity RecoverabilityPredictabilityAccuracy Mean Time to Fail SpeedEfficiencyThruput Resource Consumpt. Response Time TestabilityExtensibilityAdaptabilityMaintainabilityCompatiabilityConfigurabilityServiceabilityInstallabilityLocalizability

5. CMPUT 402 - Software QualityMajor Software Strategies - 5 © Paul Sorenson MEASUREMENT PROGRAM PLANNING FURPS+ planned versus actual tracking (from Fig. 4-3 Grady, Practical Software Metrics) FURPS WEEK

6. CMPUT 402 - Software QualityMajor Software Strategies - 6 © Paul Sorenson QUESTION GENERATION SG2: Minimize Effort & Schedule Q11: Where are the resources going? Where are the worse rework loops? Q12: What are the total maintenance and support costs for the product? Q13: What development methods affect maintenance costs? Q14: How maintainable is the product as change occurs? When do we rewrite? Q15: What will process monitoring cost and where are costs distributed? Q16: What will the maintenance requirements be? Q17: How long does it take to respond to (fix) a defect? Q18: How can we predict cycle time, reliability and effort? Q19: What practices yield best results? Q20: How much do maintenance phase activities cost? Q21: What are the major cost components? Q22: How do costs change over time?

7. CMPUT 402 - Software QualityMajor Software Strategies - 7 © Paul Sorenson Minimize Effort & Schedule Emphasis is clearly on management aspects Much more process-oriented than customer-oriented Important to get people involved in looking at where time is spent. Also important to empower groups and individuals to make changes in their areas to achieve stated goals

8. CMPUT 402 - Software QualityMajor Software Strategies - 8 © Paul Sorenson Q11: Where are the resources going? Project Type Firmware (31 Projects) Systems (48 Projects) Applications (53 Projects) Phase Requirements Design Implementation Test 15% 14% 22% 21% 19% 16% 39% 30% 34% 25% 37% 28% (adapted from Fig. 5-1 Percent engineering hours by phase)

9. CMPUT 402 - Software QualityMajor Software Strategies - 9 © Paul Sorenson QUESTION GENERATION SG3: Minimize Defects Q23: What are the key indicators of process health and how are we doing? Q24: What are the high-level opportunities for preventive maintenance? Q25: Are fixes effective and are unexpected side-effects created? Q26: What is the post-release quality of each module ? Q27: What are we doing right (w.r.t. defects)? Q28: How do we know when to release? Q29: How effective is the development process in preventing defects? Q30: What can we predict post-release based on pre-release data? Q31: What defects are getting through and what caused those defects?

10. CMPUT 402 - Software QualityMajor Software Strategies - 10 © Paul Sorenson MINIMIZING DEFECTS most applicable when product features are competitive and holding or improving market share is the goal Grady points to products such as standard operating systems and compilers as examples Typical metrics are defect-tracking oriented: count of prerelease and postrelease defects, count of remaining critical & serious defects or defects sorted by module or size, NCSS and branch coverage in testing

11. CMPUT 402 - Software QualityMajor Software Strategies - 11 © Paul Sorenson MAJOR STRATEGIES CHARACTERISTICS MAJORCHARACTERISTICS MAJOR BUSINESS FACTOR WHEN MOST EFFECTIVE CHARACTERISTIC FEATURE MOST VISIBLE METRICS GROUP LIKELY TO DRIVE STRATEGY GROUP MOST IN CONTACT WITH CUSTOMER POTENTIAL DRAWBACKS IF FOCUS TOO RESTRICTED MAXIMIZECUSTOMERSATISFACTION MINIMIZE EFFORT AND SCHEDULE MINIMIZEDEFECTS Attempt to capture market share When initially entering the market Customer commun. & quick response Survey & interview data product metrics, defects Development team initally, customer support later Development team Process of developing products may not improve Competitive pressures => prod dev & cost cntrl Competitive products or prod cost reduction req. Focus on delivery dates and effort Calendar time, effort and defects Division or company management Marketing/factory customer support Defect backlog can get unmanageable, customers & developers frustrated Hold/increase market share When features are competitive Analysis & removal of defect causes Failure analysis by module, cause & sev. Devel. team &/or quality organization Field support organization Defects may be fixed that are not cost effective

12. CMPUT 402 - Software QualityMajor Software Strategies - 12 © Paul Sorenson QUESTION GENERATION SG4: Minimize Time to Market 1.

13. CMPUT 402 - Software QualityMajor Software Strategies - 13 © Paul Sorenson Mixture of Goals MaximizeCustomerSatisfaction MinimizeCosts MinimizeDefects MinimizeTime-to-Market Air Traffic Control System Next Version of Baldergome Java Compiler