Embed Size (px)
DESCRIPTION
GQM, GQM+. Supannika Koolmanojwong CSCI577 Spring 2013. Project Tracking. Goal-Question-Metric Goal-Question-Metric + . GQM paradigm. http://thecriticalpath.info/tag/gqm/. Goal-Question-Metric: What?. Promoted By Victor Basili , University of Maryland Software metric approach - PowerPoint PPT Presentation
Citation preview
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 1
GQM, GQM+
Supannika KoolmanojwongCSCI577 Spring 2013
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 2
Project Tracking• Goal-Question-Metric• Goal-Question-Metric +
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 3
GQM paradigm
http://thecriticalpath.info/tag/gqm/
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 4
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
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 5
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
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 6
Goal-Question-Metric: How?• Six-step process
1. Develop a set of corporate, division, and project business goals
2. Generate questions defining those goals3. Specify measures needed to be collected to answer
questions4. Develop mechanisms for data collection5. Collect, validate, and analyze data. Provide feedback in real-
time6. Analyze data in post mortem fashion. Provide
recommendations for future improvements.
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 7
To create Goal• Build a sentence addressing each topic
– “…object, purpose, quality attribute, perspective/viewpoint, environment …”
Object – unit test processPurpose – understandFocus – impact of adding additional testsView 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.”
http://sqgne.org/presentations/2007-08/Dow-Nov-2007.pdf
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 8http://sqgne.org/presentations/2007-08/Dow-Nov-2007.pdf
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 9http://sqgne.org/presentations/2007-08/Dow-Nov-2007.pdf
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 10
GQM example
Goal 1
[1] Purpose[2] Issue[3] Object (process)[4] Viewpoint
Maintaina maximum level ofcustomer satisfactionfrom the Help Desk user’s viewpoint
Question 1 What is the current help desk ticket trend?
Metrics 1Metrics 2Metrics 3Metrics 4Metrics 5
Number of help desk tickets closedNumber of new help desk tickets% tickets outside of the upper limitSubjective rating of customer satisfactionNumber of new help desk tickets open
Question 2 Is the help desk satisfaction improving or diminishing?
Metrics 6Metrics 7Metrics 8Metrics 9
Number of help desk calls abandonedNumber of help desk calls answeredNumber of help desk calls sent to voicemailSubjective rating of customer satisfaction
http://thecriticalpath.info/tag/gqm/
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 11
GQM Example
http://www.goldpractices.com/practices/gqm/
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 12
GQM ExampleAT&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)
Goal Question Metrics
Plan
How much does the inspection process cost?
Average effort per KLOCPercentage of the reinspections
How much calendar time does Average effort per KLOCthe inspection process take Total KLOC inspected
Monitor and control
What is the quality of the inspected software
Average faulted detected per KLOCAverage inspection rateAverage preparation rate
To what degree did the staffconform to the procedures
Average inspection rateAverage preparation rateAverage lines of code inspected
What is the status of theinspection process? Total KLOC inspected
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 13
Improve
How effective is the inspectionprocess?
Defect removal efficiencyAverage faults detected per KLOCAverage inspection rateAverage preparation rateAverage lines of code inspected
What is the productivity ofthe inspection process?
Average effort per fault detectedAverage inspection rateAverage preparation rateAverage lines of code inspected
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 14
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.
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 15
When it would be possible to ship the software?
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 16
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 17
GQM – example : Office Space
http://www.cura.org.uk/fig88gqmetric.pdf
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 18
GQM+Strategies: What?• An extension of GQM
– Built on top• Link software measurement goals to higher-level
goals– Software organization– Entire business
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 19
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
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 20
GQM+Strategies: Example
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 21
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.
University of Southern California
Center for Systems and Software Engineering
(C) USC-CSSE 22
References• Goal-Question-Metric
– http://en.wikipedia.org/wiki/GQM– http://www.cs.umd.edu/~mvz/handouts/gqm.pdf– http://goldpractice.thedacs.com/practices/gqm/
• GQM+Strategies– http://www.cs.umd.edu/~basili/publications/proceedings/P122.pdf– http://www-ivs.cs.uni-magdeburg.de/sw-eng/us/java/GQM/link3.shtml
•
