Can Clean Pipes Produce Dirty Water?
IEEE Software
Does OO Sync with How We Think?
IEEE Software
From Complex Specifications to a Working Prototype. A Protocol Engineering Case Study
FME '01 Proceedings of the International Symposium of Formal Methods Europe on Formal Methods for Increasing Software Productivity
Journal of Systems and Software
A model for software rework reduction through a combination of anomaly metrics
Journal of Systems and Software
Software inspections in practice: six case studies
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Finding and ranking research directions for software testing
EuroSPI'05 Proceedings of the 12th European conference on Software Process Improvement
| Hi-index | 0.00 |
The software quality community has become too satisfied with the “state of the practice”. We face the same problems today that we did a decade ago, but now the urgency for solutions is greater. Our present dilemma can be best explained by walking through the past decade's major software quality trends and their associated myths. By myths, I refer to the claims used to support the numerous software quality “silver bullets” that flourished and faded in the past decade. Although I could add lesser items to my list, I consider the following eight as the main culprits (because these fads are hard to compare fairly and quantitatively, they appear in no particular order): (1) software process improvement and maturity; (2) formal methods; (3) programming languages and object-oriented design; (4) software metrics and measurement; (5) software standards; (6) software testing; (7) computer-aided software engineering; and (8) total quality management