Software Crisis

1
Software Crisis

• For Every 6 Installations ? 2 Cancelled
• Average Schedule ? 50 Longer
• Large Projects More Likely to Fail
• ¾ All Large Systems ? Operational Failure
• Major Quality Productivity Problems

2
Software Crisis

• Requirement Analysis (5 of Cost)
• 55 Errors, 18 Found
• Design (25 of Cost)
• 30 Errors, 10 Found
• Others
• 15 Errors, 72 Found

3
Best Practices

• Formal Risk Management
• User Manual as a Specification
• Inspection and Walkthroughs
• Metric-based Scheduling and Tracking
• Visibility of Plans and Progress
• Defect Tracking
• Quality Gates

4
Worst Practices

• Justifying New Technologies to speed up
• Specifying Impl. Technology too early
• Using Unproven Silver Bullets
• Trying to recover large schedule slips without
  major reduction in functionality
• Putting Out-of-control Items in Critical Path
• Expecting Formal Reviews to Provide Accurate
  Assessments

5
CMM

• Software Engineering Institute
• Capability Maturity Model
• 5 Levels
• Key Process Areas at each Level
• Most of companies at 1st Level

6
CMM

• Level Two, Repeatable
• Req. Mgt.
• S/W Project Planning
• S/W Tracking
• S/W Subcontract Mgt.
• S/W Quality Assurance
• S/W Configuration Mgt.

7
CMM

• Level Three, Defined
• Organization Process Focus
• Organization Process Definition
• Training Program
• Integrated S/W Mgt.
• S/W Product Engineering
• Inter-group Coordination
• Peer Reviews

8
CMM

• Level Four, Managed
• Quantitative Process Mgt.
• S/W Product Quality Mgt.
• Level Five, Optimization
• Defect Prevention
• Technology Change Mgt.
• Process Change Mgt.