Minimizing risk in applying metrics on multiple projects
Open Access
- 2 January 2003
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
Abstract
Using the author's own metrics validation methodology, he shows how this methodology can be used across dissimilar multiple projects. He shows how to reduce the risk of using metrics on multiple projects. He also shows that the choice of metrics and their values can have a significant effect on the quality of software that is achieved and on the cost and amount of inspection that is incurred on multiple projects. A multi-project example, emphasizing the discriminative power validity criterion in support of the quality control function, is presented. A metrics validation process is defined that integrates quality factors, metrics and quality functions.Keywords
This publication has 10 references indexed in Scilit:
- Validating software metrics: producing quality discriminatorsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Methodology for validating software metricsIEEE Transactions on Software Engineering, 1992
- A philosophy for software measurementJournal of Systems and Software, 1990
- Software measurement: A conceptual frameworkJournal of Systems and Software, 1990
- Deriving structurally based software measuresJournal of Systems and Software, 1990
- Empirically guided software development using metric-based classification treesIEEE Software, 1990
- Evaluating software complexity measuresIEEE Transactions on Software Engineering, 1988
- The TAME project: towards improvement-oriented software environmentsIEEE Transactions on Software Engineering, 1988
- Metric Analysis and Data Validation Across Fortran ProjectsIEEE Transactions on Software Engineering, 1983
- An Empirical Study of a Syntactic Complexity FamilyIEEE Transactions on Software Engineering, 1983