SOFTWARE QUALITY ENGINEERING) Part 3

(SOFTWARE QUALITY ENGINEERING)-KIT-042
Unit-II
Software Quality Metrics
Customer Satisfaction Metrics
• Customer satisfaction is often measured by customer survey

data via the five-point scale:
– Very satisfied
– Satisfied
– Neutral
– Dissatisfied
– Very dissatisfied
Customer Satisfaction(Cont’d)
• Satisfaction with the overall quality of the product and its

specific dimensions is usually obtained through various
methods of customer surveys. For example, the specific
parameters of customer satisfaction in software monitored by
IBM include the CUPRIMDSO categories (capability,
functionality, usability, performance, reliability, install ability,
maintainability, documentation/information, service, and
overall); for Hewlett-Packard they are FURPS (functionality,
usability, reliability, performance, and service).
Examples Metrics for Customer Satisfaction
• Percent of completely satisfied customers

• Percent of satisfied customers (satisfied and completely
satisfied)
• Percent of dissatisfied customers (dissatisfied and completely
dissatisfied)
• Percent of non satisfied customers (neutral, dissatisfied, and
completely dissatisfied)
Customer Satisfaction(Cont’d)
• Usually the second metric, percent satisfaction, is used. In
practices that focus on reducing the percentage of nonsatisfaction,
much like reducing product defects, metric is used.
• In addition to forming percentages for various satisfaction or
dissatisfaction categories, the weighted index approach can
be used. For instance, some companies use the net
satisfaction index (NSI) to facilitate comparisons across
product. The NSI has the following weighting factors:
• Completely satisfied = 100%
• Satisfied = 75%
• Neutral = 50%
• Dissatisfied = 25%
• Completely dissatisfied = 0%
In-Process Quality Metrics
• In-process quality metrics simply means tracking defect

arrival during formal machine testing for some organizations.
On the other hand, some software organizations with well-
established software metrics programs cover various
parameters in each phase of the development cycle.
• Defect density during machine testing
• Defect arrival pattern during machine testing
• Phase-based defect removal pattern
• Defect removal effectiveness
Defect Density During Machine Testing
• Defect rate during formal machine testing (testing after code is

integrated into the system library) is usually positively
correlated with the defect rate in the field.
• The simple metric of defects per KLOC or function point is a
good indicator of quality while the product is being tested.
• It is especially useful to monitor subsequent releases of a
product in the same development organization. release-to-
release comparisons are not contaminated by extraneous
factors.
Defect Density During Machine Testing(Cont’d)
• The development team or the project manager can use the

following scenarios to judge the release quality:
• If the defect rate during testing is the same or lower than that
of the previous release (or a similar product), then ask: Does
the testing for the current release deteriorate?
 If the answer is no, the quality perspective is positive.
 If the answer is yes, you need to do extra testing (e.g., add test
cases to increase coverage, blitz test, customer testing, stress
testing, etc.).
Defect Density During Machine Testing(Cont’d)
• If the defect rate during testing is substantially higher than that

of the previous release (or a similar product), then ask: Did we
plan for and actually improve testing effectiveness?
 If the answer is no, the quality perspective is negative.
Ironically, the only remedial approach that can be taken at this
stage of the life cycle is to do more testing, which will yield
even higher defect rates.
 If the answer is yes, then the quality perspective is the same
or positive.
Defect Arrival Pattern During Machine Testing
• The pattern of defect arrivals gives more information than

defect density during testing.
• The objective is to look for defect arrivals that stabilize at a
very low level, or times between failures that are far apart
before ending the testing effort and releasing the software.
Phase-Based Defect Removal Pattern
• This is an extension of the test defect density metric.

• It requires tracking defects in all phases of the development
cycle.
• The pattern of phase-based defect removal reflects the overall
defect removal ability of the development process.
Defect Removal Effectiveness
•Defect removal effectiveness (or efficiency, as used by some

writers) can be defined as follows:
Because the total number of latent defects in the product at any

given phase is not known, the denominator of the metric can only
be approximated. It is usually estimated by:

SOFTWARE QUALITY ENGINEERING) Part 3

Uploaded by

Copyright:

Available Formats

SOFTWARE QUALITY ENGINEERING) Part 3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SOFTWARE QUALITY ENGINEERING) Part 3

Uploaded by

Copyright:

Available Formats

(SOFTWARE QUALITY ENGINEERING)-KIT-042

• Customer satisfaction is often measured by customer survey

• Satisfaction with the overall quality of the product and its

• Percent of completely satisfied customers

• In-process quality metrics simply means tracking defect

• Defect rate during formal machine testing (testing after code is

• The development team or the project manager can use the

• If the defect rate during testing is substantially higher than that

• The pattern of defect arrivals gives more information than

• This is an extension of the test defect density metric.

•Defect removal effectiveness (or efficiency, as used by some

Because the total number of latent defects in the product at any

You might also like