Performing Defect Prevention

Objectives
In this lesson, you will learn to:
• Analyze test reports for coverage and effectiveness.
• Calculate defect metrics to analyze the effectiveness and efficiency of
testing.

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 1 of 12

Performing Defect Prevention

Analyzing Test Reports

• Problem Statement

• Globalsolutions Inc. is a software development company. The

company is presently preparing a Student Registration Entry
module using C++.

The module accepts the detail of each student, performs certain

validation checks on the entered data, and prompts the user for
the same. The details accepted from the user include name,
address, phone number, and age.

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 2 of 12

Performing Defect Prevention

Analyzing Test Reports

• Problem Statement (Contd.)

• The validations expected are:

• Name: Should not be left blank and should not contain

anything except alphabets

• Phone number: Should be digits and length should be 8 or 10

• Address: Should not be left blank

• Age: Should be a positive number

The code snippet for this program is given in the Student

Guide.

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 3 of 12

Performing Defect Prevention

Solution
Refer to Student Guide for Solution

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 4 of 12

Performing Defect Prevention

Defect Leakage Matrix

• Defect leakage matrix is the ratio of the number of defects encountered due to
earlier phases to the total number of defects encountered in the current phase.
• This helps to identify the number of defects encountered in the later stages
because of the defects in earlier stages.
• This matrix is also called defect introduction and defect removal matrix, and is
used for defect prevention and defect analysis.
• Defects can be categorized on the basis of the following points:
• Category
• Severity
• Type
• Origin

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 5 of 12

Performing Defect Prevention

Calculating Defect Metrics

• Problem Statement

• StarMoon Technologies is working on a project to automate the

inventory management system used by Green Alley Stores Inc., a
renowned retail chain. The customer wants the automated solution
to be operational within three months, so that they can implement
the system to ease work during the year’s financial closure. The
team at StarMoon Technologies has worked on a similar project
recently and is confident about meeting the customer’s timelines.

John Allen, a Project Manager at StarMoon Technologies, heads the

software project. John’s team successfully delivers the inventory
control software to Green Alley Stores Ltd. on time.
However, on delivery, the customers find an alarming number of
defects in the application. This disappoints the customer, as the
software needs to be implemented at the earliest.

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 6 of 12

Performing Defect Prevention

Calculating Defect Metrics

• Problem Statement (Contd.)

• The senior management of StarMoon Technologies decides to

analyze the following:

• The efficiency of the defect removal processes adopted by

John’s team.

• The average number of defects found in the application.

• The quality of the testing processes.

• The testing cost to the project.

The information provided is given in the Student Guide.

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 7 of 12

Performing Defect Prevention

Solution
Refer to Student Guide for Solution

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 8 of 12

Performing Defect Prevention

Types of Metrics
• Other types of metrics that enable you to measure various factors of software,
such as size and complexity, include:
• Complexity measurements: Complexity metrics is a component-level
design metric. Component-level design metrics are used to focus on the
internal characteristics of the software at the component level.
• Size measurements: Size is another fundamental metric. Most of the
metrics that are gathered are normalized by size metrics. This provides a
size independent analysis of a software project. For example, productivity
can be defined as size produced per unit effort. Software size is a critical
input to project planning. The size estimate and other factors are used to
derive effort and schedules before and during a project.
• Product measurements: Product metrics is the metrics used for software
products.

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 9 of 12

Performing Defect Prevention

Types of Metrics (Contd.)

• Software products are independent of the processes that are implemented to
develop them. Examples of Product metrics include:
• Effort Productivity = Test Planning Productivity = Number of Test cases
designed / Actual Effort for Design and Documentation
• Quality of Testing = (Number of defects found during Testing/(Number of
defects found during testing + Number of defects found after delivery)) *
100
• Test cost (in %) = (Cost of testing / total cost of software project)*100
• Evaluating the effectiveness of a software solution is difficult without the use of
metrics. Metrics relate to the four functions of management, as follows:
• Planning: Metrics can serve as a basis for planning costs, trainings,
resources, scheduling, and budget.
• Organizing: Size and schedule metrics influence a project’s organization.
• Controlling: Metrics are used to track software development activities for
compliance to plans.
• Improving: Metrics are used as a tool for process improvement.
©NIIT Planning and Designing Software Tests Lesson 5 / Slide 10 of 12
Performing Defect Prevention

Summary
In this lesson, you learned that:

• The test report is the result of formally running the test procedure and
recording the results.
• The test report summarizes the results of the test and draws conclusions
about the fitness of the product.
• Preparing a defect leakage matrix is a good way to check if the effectiveness
and coverage parameters have been covered in the test reports.
• The metrics unique to software testing are:
• Defect Removal Efficiency
• Defect Density

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 11 of 12

Performing Defect Prevention

Summary (Contd.)
• Other types of metrics include:
• Complexity measurements
• Size measurements
• Defect measurements
• Product measurements
• While calculating defect metrics, the root cause of the defect should be first
identified. Each root cause entry, in general, contains three fields:
• Life cycle stage in which the defect originated
• Type of defect
• Specific cause of the defect

©NIIT Planning and Designing Software Tests Lesson 5 / Slide 12 of 12