- Bringing common sense back to software development -
The traditional model
The software black holes model
Key ingredient
Defects are uniformly distributed
Defects are concentrated in fewer areas
Resource utilization
Spread thinly and evenly
Increased on potential weak areas and decreased otherwise
Development efficiency
Overstaffing of solid development areas and understaffing of weak areas
Staffing is proportionate to expected weakness
Data analysis and QA
Overemphasis on counting bugs and under-emphasis on engineering judgment
Using engineering judgment to assess elimination of black holes
Cost efficiency (quality per $)
Low
High