Introduction
Many aspects of the software products, projects and processes can be measured. The trick is to select a small and balanced set of metrics that will help your organization track progress toward its goal Goal-Question-Metric (GQM) is an excellent technique for selecting appropriate metrices to meet your needs.
Goal-Question-metric Methodology
The GQM methodology is used to define measurement on the software project, process and product in such a way that:-
- Resulting metrics are tailored to the organization and its goal.
- Resulting measurement data play a constructive and instructive role in the organization.
- Metrices and their interpretation reflected the values and viewpoints of the different group affected.
- Conceptual Level (Goal)
- Operational Level (Goal)
- Quantitative Level (Goal)
A Goal is defined for and a object for a variety of reasons with respect to various model of quality from various points of view, and relative to a particular environment.
Operational Level (Question) :-
A set of Questions is used to define model of the object of study and then focuses on that object to characterize the assessment or achievement of a specific goal.
Quantitative Level ( Metric) :-
A set of metrics, based on the model is associated with every question in order to ensure it in a measurable way.
For example, we may choose to examine a code module and capture its size using a measure such as lines of code (LOC). The measure is the mapping that tells us how to count the lines of code from any module, counting comments or not, counting reused code or not, and so on. Thus, for each module we can generate a mathematical representation the no. of lines of code. We evaluate the no. of lines of code for each of a set of modules so that we can compare and contrast the modules. The measure helps us see if one module is larger or smallest than another.
Comments
Post a Comment