A Software test manager must have the competency to measure test processes effectively. The key to effective mesurement lies in the ability to clearly identify the goals to be accomplished and the issues to be tackled. Many test managers and their organizations waste time and money in measuring more things than are necessary.
Test metrics are an important indicator of the effectiveness of a software testong process. The first step in establishing test metrics is to identify the key software testing processes that can be objectively measured. This information can be used as the baseline to define the metric(s) and to determine what information will be trackled, who will track the information and at which frequency. Then the processes necessary to effectively track, calculate, manage and interpret the defined metrics must be implemented. Areas for processs improvement can be identified based on the interpretation of the defined metrics.
Paul Goodman defines software metrics as "The continuos application of measurement-based techniques to the software development process and its products to supply meaningful and timely management information, together with the use of those techniques to improve that process and its products".
G. Gordon Schulmeyer defines a metrics as "A quantitative measure of the degree to which a system, component or process possesses a given attribute".
Although challenging, software measurement is an essential component for a healthy and high-performance software engineering culture. This paper revisits some basic software measurement priciples and suggest some metrics that can help you better understand and improve operations in your organization. Measurement activities must be planned carefully because they require significant efforts to implement and returns are realized only over a period of time