1 / 22

GQM, GQM+

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

kelli
Download Presentation

GQM, GQM+

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GQM, GQM+ Supannika Koolmanojwong CSCI577 Spring 2013 (C) USC-CSSE

  2. Project Tracking • Goal-Question-Metric • Goal-Question-Metric + (C) USC-CSSE

  3. GQM paradigm (C) USC-CSSE http://thecriticalpath.info/tag/gqm/

  4. Goal-Question-Metric: What? • Promoted By Victor Basili, University of Maryland Software metric approach • Capturesmeasurement 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-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 (C) USC-CSSE

  6. Goal-Question-Metric: How? • Six-step process • Develop a set of corporate, division, and project business goals • Generate questions defining those goals • Specify measures needed to be collected to answer questions • Develop mechanisms for data collection • Collect, validate,and analyze data. Provide feedback in real-time • Analyze data in post mortem fashion. Provide recommendations for future improvements. (C) USC-CSSE

  7. To create Goal • Build a sentence addressing each topic • “…object, purpose, quality attribute, perspective/viewpoint, environment …” • “ Analyzethe unit test process to understand the impact of adding additional tests to project A from the viewpoint of the project manager.” • Object – unit test process • Purpose – understand • Focus – impact of adding additional tests • View point - project manager • Environment – Project A (C) USC-CSSE http://sqgne.org/presentations/2007-08/Dow-Nov-2007.pdf

  8. (C) USC-CSSE http://sqgne.org/presentations/2007-08/Dow-Nov-2007.pdf

  9. (C) USC-CSSE http://sqgne.org/presentations/2007-08/Dow-Nov-2007.pdf

  10. GQM example (C) USC-CSSE http://thecriticalpath.info/tag/gqm/

  11. GQM Example (C) USC-CSSE http://www.goldpractices.com/practices/gqm/

  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) (C) USC-CSSE

  13. (C) USC-CSSE

  14. GQM Example • TASK: Software-development process managementPROBLEM: 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-CSSE

  15. When it would be possible to ship the software? (C) USC-CSSE

  16. (C) USC-CSSE

  17. GQM – example : Office Space (C) USC-CSSE http://www.cura.org.uk/fig88gqmetric.pdf

  18. GQM+Strategies: What? • An extension of GQM • Built on top • Link software measurement goals to higher-level goals • Software organization • Entire business (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 (C) USC-CSSE

  20. GQM+Strategies: Example (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. (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 (C) USC-CSSE

More Related