ITMPI FLAT 002
Main Menu
Home / IT Best Practices / Defining the GQM Method for Software

Defining the GQM Method for Software

According to its originator, Victor Basili, the goal-question-metric (GQM) method presents a systematic approach for integrating goals to models of the software processes, products, and quality perspectives of interest based upon the specific needs of the project and the organization. If that sounds like a mouthful, allow us to break it down a little further for you.

Putting the Question in Goal-Question-Metric

In order to improve software development, goals for improvement must first be introduced. Compounding this issue is that improvement goals should be in some way related to organizational goals. So to distinguish our goals, we start measuring various attributes of our processes, looking for areas that are left wanting. GQM can be used to determine why an attribute is being measured. It also provides a three-part framework:

  1. The major goals of the development project
  2. Questions derived from goals that must be answered in order to determine if the goals are achieved
  3. Measurements that provide the most appropriate information for answering the questions

GQM enables metrics to be defined from two points of view, from the view of the project team, and from the view based on models for software processes and products. As for its actual implementation, GQM is divided into four phases:

  1. The Planning phase, during which the project for measurement application is selected, defined, characterised, and planned, resulting in a project plan.
  2. The Definition phase, during which the measurement programme is defined (goal, questions, metrics and hypotheses are defined) and documented.
  3. The Data collection phase, during which the actual data collection takes place, resulting in collected data.
  4. The Interpretation phase, during which the collected data is processed with respect to the defined metrics into measurement results, that provide answers to the defined questions, after which goal attainment can be evaluated.

If you are still raising an eyebrow about what this all means, consult this further explanation at SM Lab: http://www-ivs.cs.uni-magdeburg.de/sw-eng/us/java/GQM/link1.shtml

About John Friscia

John Friscia is the Editor of Computer Aid's Accelerating IT Success. He began working for Computer Aid, Inc. in 2013 and continues to provide graphic design support for AITS. He graduated summa cum laude from Shippensburg University with a B.A. in English.

Check Also

10 Mistakes to Avoid When Troubleshooting IT Problems

Troubleshooting a problem can be a pretty tense time in the heat of the moment. …

Leave a Reply

Your email address will not be published. Required fields are marked *