Validation on an Approach for Improving Existing Measurement Frameworks

Software organizations are in need of methods to understand, structure, and improve the data their are collecting. We have developed an approach for use when a large number of diverse metrics are already being collected by a software organization (M.G. Mendonca et al., 1998; M.G. Mendonca, 1997). The approach combines two methods. One looks at an organization's measurement framework in a top-down goal-oriented fashion and the other looks at it in a bottom-up data-driven fashion. The top-down method is based on a measurement paradigm called Goal-Question-Metric (GQM). The bottom-up method is based on a data mining technique called Attribute Focusing (AF). A case study was executed to validate this approach and to assess its usefulness in an industrial environment. The top-down and bottom-up methods were applied in the customer satisfaction measurement framework at the IBM Toronto Laboratory. The top-down method was applied to improve the customer satisfaction (CUSTSAT) measurement from the point of view of three data user groups. It identified several new metrics for the interviewed groups, and also contributed to better understanding of the data user needs. The bottom-up method was used to gain new insights into the existing CUSTSAT data. Unexpected associations between key variables prompted new business insights, and revealed problems with the process used to collect and analyze the CUSTSAT data. The paper uses the case study and its results to qualitatively compare our approach against current ad hoc practices used to improve existing measurement frameworks.

[1]  Sandro Morasca,et al.  Property-Based Software Engineering Measurement , 1996, IEEE Trans. Software Eng..

[2]  Elaine J. Weyuker,et al.  Evaluating Software Complexity Measures , 2010, IEEE Trans. Software Eng..

[3]  Victor R. Basili,et al.  Technology transfer at Motorola , 1994, IEEE Software.

[4]  Austin Melton,et al.  Deriving structurally based software measures , 1990, Journal of Systems and Software.

[5]  Marvin V. Zelkowitz,et al.  A formal program complexity model and its application , 1992, J. Syst. Softw..

[6]  Norman E. Fenton,et al.  Measurement : A Necessary Scientific Basis , 2004 .

[7]  Inderpal Bhandari,et al.  Attribute focusing: machine-assisted knowledge discovery applied to software production process control , 1993 .

[8]  Tom DeMarco Why Does Software Cost So Much , 1995 .

[9]  Victor R. Basili,et al.  Software process evolution at the SEL , 1994, IEEE Software.

[10]  Adam A. Porter,et al.  Learning from Examples: Generation and Evaluation of Decision Trees for Software Resource Analysis , 1988, IEEE Trans. Software Eng..

[11]  Edward F. Weller Using metrics to manage software projects , 1994, Computer.

[12]  Victor R. Basili,et al.  An approach to improving existing measurement frameworks in software development organizations , 1997 .

[13]  E. GaffneyJ.,et al.  Software Function, Source Lines of Code, and Development Effort Prediction , 1983 .

[14]  Victor R. Basili,et al.  Developing Interpretable Models with Optimized Set Reduction for Identifying High-Risk Software Components , 1993, IEEE Trans. Software Eng..

[15]  Norman F. Schneidewind,et al.  Methodology For Validating Software Metrics , 1992, IEEE Trans. Software Eng..

[16]  Horst Zuse,et al.  Software complexity: Measures and methods , 1990 .

[17]  Richard J. Lipton,et al.  Software Project Forecasting , 1980 .

[18]  Willi Klösgen,et al.  Knowledge discovery in databases terminology , 1996, KDD 1996.

[19]  Stan Rifkin,et al.  Measurement in Practice , 1991 .

[20]  Victor R. Basili,et al.  The TAME Project: Towards Improvement-Oriented Software Environments , 1988, IEEE Trans. Software Eng..

[21]  Inderpal S. Bhandari,et al.  In-Process Improvement through Defect Data Interpretation , 1994, IBM Syst. J..

[22]  Barry W. Boehm,et al.  Quantitative evaluation of software quality , 1976, ICSE '76.

[23]  Inderpal S. Bhandari,et al.  A Case Study of Software Process Improvement During Development , 1993, IEEE Trans. Software Eng..

[24]  Victor R. Basili,et al.  A Pattern Recognition Approach for Software Engineering Data Analysis , 1992, IEEE Trans. Software Eng..

[25]  Victor R. Basili,et al.  Metric Analysis and Data Validation Across Fortran Projects , 1983, IEEE Transactions on Software Engineering.

[26]  Shari Lawrence Pfleeger,et al.  Towards a Framework for Software Measurement Validation , 1995, IEEE Trans. Software Eng..

[27]  Martin J. Shepperd,et al.  Algebraic Models and Metric Validation , 1991, Formal Aspects of Measurement.

[28]  Ray Offen,et al.  Establishing Software Measurement Programs , 1997, IEEE Softw..

[29]  Khaled El Emam,et al.  An empirical evaluation of the G/Q/M method , 1993, CASCON.

[30]  Victor R. Basili,et al.  An Empirical Study of a Syntactic Complexity Family , 1983, IEEE Transactions on Software Engineering.

[31]  B. Kitchenham,et al.  Case Studies for Method and Tool Evaluation , 1995, IEEE Softw..

[32]  Taghi M. Khoshgoftaar,et al.  An Information Theory-Based Approach to Quantifying the Contribution of a Software Metric , 1997, J. Syst. Softw..

[33]  Shari Lawrence Pfleeger,et al.  Lessons learned in building a corporate metrics program , 1993, IEEE Software.

[34]  Robert B. Grady,et al.  Successfully applying software metrics , 1994, Computer.

[35]  Jeff Tian,et al.  Analyzing and Improving Reliability: A Tree-Based Approach , 1998, IEEE Softw..

[36]  Arthur L. Price,et al.  Managing code inspection information , 1994, IEEE Software.

[37]  Marvin V. Zelkowitz,et al.  Experimental Models for Validating Technology , 1998, Computer.

[38]  Barbara Ann Kitchenham,et al.  Evaluating software engineering methods and tools part 6: identifying and scoring features , 1997, SOEN.

[39]  E. Guba,et al.  Naturalistic inquiry: Beverly Hills, CA: Sage Publications, 1985, 416 pp., $25.00 (Cloth) , 1985 .

[40]  John E. Gaffney,et al.  Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation , 1983, IEEE Transactions on Software Engineering.

[41]  Inderpal S. Bhandari,et al.  On the use of machine-assisted knowledge discovery to analyze and reengineer measurement frameworks , 1995, CASCON.

[42]  Victor R. Basili,et al.  An Approach to Improving Existing Measurement Frameworks , 1998, IBM Syst. J..

[43]  D. Potier,et al.  Experiments with computer software complexity and reliability , 1982, ICSE '82.

[44]  Claude E. Walston,et al.  A Method of Programming Measurement and Estimation , 1977, IBM Syst. J..

[45]  Chris F. Kemerer,et al.  An empirical validation of software cost estimation models , 1987, CACM.

[46]  Norman E. Fenton,et al.  Implementing Effective Software Metrics Programs , 1997, IEEE Softw..

[47]  Michael Daskalantonakis,et al.  A Practical View of Software Measurement and Implementation Experiences Within Motorola , 1992, IEEE Trans. Software Eng..

[48]  Albert L. Baker,et al.  A mathematical perspective for software measures research , 1990, Softw. Eng. J..

[49]  Robert B. Grady,et al.  Practical Software Metrics for Project Management and Process Improvement , 1992 .

[50]  Douglas Fisher,et al.  Machine Learning Approaches to Estimating Software Development Effort , 1995, IEEE Trans. Software Eng..

[51]  Victor R. Basili,et al.  A Methodology for Collecting Valid Software Engineering Data , 1984, IEEE Transactions on Software Engineering.