Measurements and Metrics A measurement is an indication of the size, quantity, . Quality Control Plan; Managing Defects in Integration & Test. generally talk about metrics and how to do measurements in a right way. Some of them use very dangerous metrics to assess team members'. A Metric is a quantitative measure of the degree to which a system, system component, or process possesses a given attribute. Metrics can be defined as “STANDARDS OF MEASUREMENT”. Software Metrics are used to measure the quality of the project. Simply, Metric is a unit used for describing an attribute.


Author: Dante O'Conner
Country: Gambia
Language: English
Genre: Education
Published: 15 December 2014
Pages: 225
PDF File Size: 43.38 Mb
ePub File Size: 18.47 Mb
ISBN: 831-6-94544-101-8
Downloads: 993
Price: Free
Uploader: Dante O'Conner


It can be used to measure the efficiency of a project team or any testing tools being used by the team members Identification of correct testing metrics is very important. Few things need to be considered before identifying the test metrics Fix the target audience for the metric preparation Define the goal for metrics Introduce all the relevant metrics based on project test metrics and measurements Analyze the cost benefits aspect of each metrics and the project lifestyle phase in which it results into the maximum output Manual Test Metrics Manual test metrics is classified into two classes Base Metrics Calculated Metrics Base metrics is the raw data collected by Test Analyst during the test case development and execution of test cases executed, of test cases.

While, calculated test metrics and measurements is derived from the data collected in base metrics. When using number of lines of code as a metric, other metrics would need to be used such as product quality. Source lines of code can be measured from another point of view.

This is the measuring the actual number of lines of code written in a specific amount of time. When looking at a project level, the number of lines of code that is measured would typically come from the overall lines of code written throughout the project within a specific amount of time.

If the SLOC metric was being applied to an individual developer or a team then the number of lines of code would obviously be measured on the lines written by the developer or team respectively.


When developers use test metrics and measurements code from GUI designers, frameworks, etc it can lead to incorrect productivity measures. When using SLOC to assess different projects written in different programming languages it cannot be taken directly.

The use of function points would give a better test metrics and measurements because the number of function points would remain the same i. Since the number of lines of code would be different, even for the same functionality, the effort required would be completely different.

When comparing projects by using SLOC, then it is far more useful if there test metrics and measurements orders of magnitudes between them. There are two ways to measure lines of code: Names of SLOC measures: Albrecht in at IBM and official release was in available for the community.

This is a relatively old technique for measurement of certain software module or property. Function Point is a measurement unit or software metric for FPA that is the end-user analysis of the functions needed for the software.

Software Testing Metrics: Complete Tutorial

Function Points test metrics and measurements grouped into five types of functionality: Internal Logical Files — logical data that is nurtured inside test metrics and measurements application.

External Interface Files — logical data that resides outside the application but is restrained with the application that is measured.

External Input — preservation, management and processing of logical data through external input through peripherals and other sources.

External Output — logical output of data by application. External Inquiries — requests and responses for external data procedures.

Software Testing: Principles and Practices by Gopalaswamy Ramesh, Srinivasan Desikan

Each of those types of test metrics and measurements is given metric called weighting factor. Implementation of Function Point metrics is a very effective way to measure the size of the software at the beginning of the development phase after establishing needs and requirements of the software.

Objects[ edit ] In software development was a need for application extensibility and software reuse. By the reuse of existing resources we have to manage dependencies that are between modules of the application and cause of the changes that may arise through the dependencies.

Test Metrics and Measurements - Software Testing: Principles and Practices [Book]

These factors are described as test metrics and measurements package metrics that are derived from: Class Cohesion — a measurement for the unity of purpose in the object or class; elements within the class or object should make as much purpose as possible.

Coupling — dependency that are between two or more classes that are heavily related together. Changing one class may force drastic changes in other classes that are highly test metrics and measurements together.