University of Southern California Center for Systems and Software Engineering GQM, GQM+ Supannika Koolmanojwong CSCI577 Spring 2013 (C) USC-CSSE1

University of Southern California Center for Systems and Software Engineering Project Tracking Goal-Question-Metric Goal-Question-Metric + (C) USC-CSSE2

University of Southern California Center for Systems and Software Engineering GQM paradigm (C) USC-CSSE3

University of Southern California Center for Systems and Software Engineering Goal-Question-Metric: What? Promoted By Victor Basili, University of Maryland Software metric approach Captures measurement on three levels –Conceptual level (goal) Defined for an object –Operational level (question) Define models of the object of study –Quantitative level (metric) Metrics associated with each question in a measurable way (C) USC-CSSE4

University of Southern California Center for Systems and Software Engineering Goal-Question-Metric: Why? Used within context of software quality improvement Effective for the following purposes: –Understanding organization’s software practices –Guiding and monitoring software processes –Assessing new software engineering technologies –Evaluating improvement activities (C) USC-CSSE5

University of Southern California Center for Systems and Software Engineering Goal-Question-Metric: How? Six-step process 1.Develop a set of corporate, division, and project business goals 2.Generate questions defining those goals 3.Specify measures needed to be collected to answer questions 4.Develop mechanisms for data collection 5.Collect, validate, and analyze data. Provide feedback in real- time 6.Analyze data in post mortem fashion. Provide recommendations for future improvements. (C) USC-CSSE6

University of Southern California Center for Systems and Software Engineering To create Goal Build a sentence addressing each topic –“…object, purpose, quality attribute, perspective/viewpoint, environment …” (C) USC-CSSE7 Object – unit test process Purpose – understand Focus – impact of adding additional tests View point - project manager Environment – Project A “ Analyze the unit test process to understand the impact of adding additional tests to project A from the viewpoint of the project manager.”

University of Southern California Center for Systems and Software Engineering (C) USC-CSSE8

University of Southern California Center for Systems and Software Engineering (C) USC-CSSE9

University of Southern California Center for Systems and Software Engineering GQM example Goal 1 [1] Purpose [2] Issue [3] Object (process) [4] Viewpoint Maintain a maximum level of customer satisfaction from the Help Desk user’s viewpoint (C) USC-CSSE10 Question 1What is the current help desk ticket trend? Metrics 1 Metrics 2 Metrics 3 Metrics 4 Metrics 5 Number of help desk tickets closed Number of new help desk tickets % tickets outside of the upper limit Subjective rating of customer satisfaction Number of new help desk tickets open Question 2 Is the help desk satisfaction improving or diminishing? Metrics 6 Metrics 7 Metrics 8 Metrics 9 Number of help desk calls abandoned Number of help desk calls answered Number of help desk calls sent to voic Subjective rating of customer satisfaction

University of Southern California Center for Systems and Software Engineering GQM Example (C) USC-CSSE11

University of Southern California Center for Systems and Software Engineering GQM Example AT&T developers was evaluating effectiveness of software inspections. The main task was cost-benefits analysis of the inspections. (amount of effort expended per thousands of lines of code reviewed) (C) USC-CSSE12

University of Southern California Center for Systems and Software Engineering (C) USC-CSSE13

University of Southern California Center for Systems and Software Engineering GQM Example TASK: Software-development process management PROBLEM: During the software testing phase many anomalies were discovered and it is suspected that the software quality would not reach a satisfactory level by the shipping deadline. QUESTION: Construct a GQM tree that helps you to decide when it would be possible to ship the software. (C) USC-CSSE14

University of Southern California Center for Systems and Software Engineering When it would be possible to ship the software? (C) USC-CSSE15

University of Southern California Center for Systems and Software Engineering (C) USC-CSSE16

University of Southern California Center for Systems and Software Engineering GQM – example : Office Space (C) USC-CSSE17

University of Southern California Center for Systems and Software Engineering GQM+Strategies: What? An extension of GQM –Built on top Link software measurement goals to higher-level goals –Software organization –Entire business (C) USC-CSSE18

University of Southern California Center for Systems and Software Engineering GQM+Strategies: Example Wants: Increase customer satisfaction Strategy: Improve product reliability –Both hardware and software Software development contribution –Reduce defect slippage –Improve testing process –Team leaders decide on set of actions to take –Implement improvements –Measure results of improvements A tie between test defect data and customer satisfaction (C) USC-CSSE19

University of Southern California Center for Systems and Software Engineering GQM+Strategies: Example (C) USC-CSSE20

University of Southern California Center for Systems and Software Engineering Workshop Find a pair, do not pair with your own team members 25 minutes to develop questions and metrics from the given goals. Prepare to present your result. (C) USC-CSSE21

University of Southern California Center for Systems and Software Engineering References Goal-Question-Metric – – – GQM+Strategies – – (C) USC-CSSE22