A testing time for software

Abstract

Suggests, with statistics, that a substantial part of any software development budget is spent on revisions and maintenance. Argues that systems are long overdue to measure the quality of software applications rather than focusing on the quality of the procedures and management approach. Feels the quest for software quality must not be held up by standards debates or management philosophies and that investment in CASE tools or 4GLs, though valuable, simply puts the majority of software budgets into areas where the smallest productivity improvements are to be made. Arguest that as only a tiny percentage of the money spent on software tools is devoted to products for application testing, yet test and maintenance consume over half the development effort, it is time this imbalance was rectified.

Citation

Hankinson, T. (1991), "A testing time for software", The TQM Magazine, Vol. 3 No. 4. https://doi.org/10.1108/09544789110032241