Scribd
Upload
657 views1 page

A) KLOC: B) Function Points: C) Pages or Words of Documentation

This document discusses different types of metrics used to measure aspects of software testing and development. It describes size metrics like lines of code and function points that measure the size of software. Defect metrics count defects and their severity. Product measures evaluate attributes like performance and reliability. Satisfaction metrics assess customer feedback. Productivity metrics measure the effectiveness and costs of testing.

Uploaded by

amulya s
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
657 views1 page

A) KLOC: B) Function Points: C) Pages or Words of Documentation

This document discusses different types of metrics used to measure aspects of software testing and development. It describes size metrics like lines of code and function points that measure the size of software. Defect metrics count defects and their severity. Product measures evaluate attributes like performance and reliability. Satisfaction metrics assess customer feedback. Productivity metrics measure the effectiveness and costs of testing.

Uploaded by

amulya s
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Size Measurements: This category includes methods primarily developed for measuring the software

size of software systems, such as lines of code, and function points. These can also be used to
measure software-testing productivity. Sizing is important in normalizing data for comparison to other
projects.

The following are examples of size metrics:

a) KLOC: thousand lines of code, used primarily with statement level languages.

b) Function points: a defined unit of size for software.

c) Pages or words of documentation

Defect Metrics: This category includes values associated with numbers or types of defects, usually
related to system size, such as “defects/1000 lines of code” or “defects/100 function points,” severity
of defects, uncorrected defects, etc.

The following are examples of defect metrics:

a) Defects related to size of software.


b) Severity of defects such as very important, important, and unimportant.
c) Priority of defects: the importance of correcting defects.
d) Age of defects: the number of days the defect has been uncovered but not corrected.
e) Defects uncovered in testing
f) Cost to locate a defect

Product Measures: This category includes measures of a product’s attributes such as performance,
reliability, usability.

The following are examples of product measures:

a) Defect density : the expected number of defects that will occur in a product during development.

Satisfaction Metrics: This category includes the assessment of customers of testing on the
effectiveness and efficiency of testing.

The following are examples of satisfaction metrics:

a) Ease of use: the amount of effort required to use software and/or software documentation.

b) Customer complaints: some relationship between customer complaints and size of system or
number of transactions processed.

c) Customer subjective assessment: a rating system that asks customers to rate their satisfaction
on different project characteristics on a scale, for example a scale of 1-5.

d) Acceptance criteria met: the number of user defined acceptance criteria met at the time software
goes operational.

e) User participation in software development: an indication of the user desire to produce high
quality software on time and within budget.

Productivity Metrics: This category includes the effectiveness of test execution.

Examples of productivity metrics are:

a) Cost of testing in relation to overall project costs: assumes a commonly accepted ratio of the costs
of development versus tests.
b) Under budget/Ahead of schedule.
c) Software defects uncovered after the software is placed into an operational status.
d) Amount of testing using automated tools.

www.softwaretestinggenius.com Page 10 of 10

You might also like