Using Software Metrics to Allocate Testing Resources
- 1 March 1988
- journal article
- research article
- Published by Taylor & Francis in Journal of Management Information Systems
- Vol. 4 (4), 93-105
- https://doi.org/10.1080/07421222.1988.11517810
Abstract
Several methods of allocating testing resources among modules within a large software development project are examined and evaluated. The objective of each of the allocation schemes is to distribute resources across modules so that a uniform percentage of resources is allocated based on the predicted number of errors each module contains (i.e., resources per error are the same for each module). By far, the most uniform allocation of resources per error is obtained through the use of software complexity metrics. However, the allocation was not perfect in any of the strategies considered, suggesting that additional work must be performed to arrive at better approaches to allocation.Keywords
This publication has 10 references indexed in Scilit:
- Complexity: Some general observationsSystems Research, 1985
- An analysis of static metrics and faults in C softwareJournal of Systems and Software, 1985
- Applying Mccabe's complexity measure to multiple‐exit programsSoftware: Practice and Experience, 1984
- Determinants of program repair maintenance requirementsCommunications of the ACM, 1984
- Software errors and complexity: an empirical investigation0Communications of the ACM, 1984
- Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science ValidationIEEE Transactions on Software Engineering, 1983
- Applying software complexity metrics to program maintenanceComputer, 1982
- Quantitative Estimates of Debugging RequirementsIEEE Transactions on Software Engineering, 1979
- A Review and Evaluation of Software ScienceACM Computing Surveys, 1978
- A Complexity MeasureIEEE Transactions on Software Engineering, 1976