University of Southern California Center for Systems and Software Engineering Metrics Organizational Guidelines [1] ©USC-CSSE1 [1] Robert Grady, Practical Software Metrics for Project Management and Process Improvement, Prentice-Hall, 1992

University of Southern California Center for Systems and Software Engineering Goal-Question-Metric Paradigm GQM is a framework for developing a metrics program [1] Steps: –Generate a set of organizational goals What do you want to improve? –Derive a set of questions relating to the goals Answers provide visibility into meeting the goals –Develop a set of metrics needed to answer the questions ©USC-CSSE2 [1] Victor Basili, Software Modeling and Measurement: The Goal/Question/Metric Paradigm, CS-TR-2956, University of Maryland, 1992

University of Southern California Center for Systems and Software Engineering GQM Goal Definition Template Purpose: To (characterize, evaluate, predict, motivate, etc.) the (process, product, model, metric, etc.) in order to (understand, assess, manage, engineer, learn, improve, etc.) it. Perspective: Examine the (cost, effectiveness, correctness, defects, changes, product metrics, reliability, etc.) from the point of view of the (developer, manager, customer, corporate perspective, etc.) Environment: The environment consists of the following: process factors, people factors, problem factors, methods, tools, constraints, etc. ©USC-CSSE3

University of Southern California Center for Systems and Software Engineering Sample Goal Trees (1/2) ©USC-CSSE4 Improve software process predictability Improve effort predictability Improve schedule predictability Improve defect predictability Deliver a quality product within cost and schedule constraints Achieve business value Execute successful project Project planning goal area: Predict the process in order to manage it Project tracking goal area: Evaluate the project in order to manage it

University of Southern California Center for Systems and Software Engineering Sample Goal Trees (2/2) ©USC-CSSE5 Improve the software process Improve productivity Maximize reuse Improve quality Minimize schedule Characterize the process to understand it Prevent defects (minimize defect fixing costs, improve product quality) Defect prevention goal area: Characterize defects in order to prevent them Process change management goal area: Evaluate the process in order to improve it

University of Southern California Center for Systems and Software Engineering ©USC-CSSE6 Sample GQM Map for Inspections defect removal effectiveness Increase quality inspection efficiency Is defect density being reduced over time? Increase productivity Goal Question Metric effectiveness vs. # of inspectors inspection rate control chart Is the inspection process under control? defect finding rate control chart How effective have process changes been? defect density trends How well are inspections performing? Efficiently use inspections to improve process What is the return of inspections? productivity trends Organizational Process ImprovementInspection Process What are optimal inspection parameters? effectiveness vs. preparation/inspection time Is productivity increasing over time? effectiveness vs. inspection rate defect categorization What are high-leverage opportunities for defect prevention? inspection ROI