UNIT 4 DEFECT MANAGEMENT

Learning Objectives…….
To learn basic concepts of defect managements

To study defect life cycle and defect Template

To understand techniques for finding defects

To learn defect reporting.

PROF. M.K.TATTE
GOVERNMENT POLYTECHNIC,ARVI
4.0 Introduction
Generally, defect management can be defined as
a process of detecting bugs and fixing them. It is
necessary to say that bugs occur constantly in the
process of software development. They are a part
of the software industry.

That is because of the fact that software

development is quite a complex process. The
team members are usually placed in strict time
frames.

They must write large pieces of code every day,

and they usually don’t have time to think about
how to avoid bugs. Hence, every software
development project requires a process that
helps detect defects and fix them.
Root Causes of defects :
1. Requirements are not defined clearly
customer

2. Design are wrong and not

implemented properly

3. People are not trained for work in

collecting requirements.

4. Processes used for product

development, testing are not capable.
4.1 Basics for defect management
In a simple words, a defect is an
undesirable state .Defect is considered
as cause of user/customer
dissatisfaction.
The Variation in the expected and
actual results is known as Defects.
A defect is an Error or a bug.

What is defect management process?

Generally, defect management can be defined as a process of detecting
bugs and fixing them. It is necessary to say that bugs occur constantly
in the process of software development. They are a part of the
software industry. That is because of the fact that software
development is quite a complex process. The team members are
usually placed in strict time frames. They must write large pieces of
code every day, and they usually don’t have time to think about how
to avoid bugs. Hence, every software development project requires a
process that helps detect defects and fix them.
4.1.3 Defect Classification

•Defect Classification
•Requirement Defects

•Design Defects

•Testing Defects

•Coding Defects

•Test environment •Initialization

•Functional Defects Defects Defects
•Interface Defects • System Interface Defects •Test tool Defects •Database related
• User interface Defects •Test Design Defects Defects
•Module Defects
•Algorithmic Defects
1. Requirement Defects These Defect arise in a product when one fails
to understand what is required by the
customer.
It may be due to customer gap, where the
customer is unable to define his
Functional Defects requirments,where developing team is not able
to make a product as per requirements.

Functional : The functionalities in the

Interface Defects application which are expected / not expected
by the customer.

Interface : Talk about various interface

essential as per requirement statement
2. Design Defect These defect generally refer to the way of design creation
or its usage while creating a software products.

The customer may or may not be in a position to

understand these defects, if structures are not correct.

System Interface : it may be generated when application

System Interface communication with Environmental factors is hampered.
Defects

User Interface: It may be a part of navigation ,look and

User interface
Defects feel type of defects which affect usability of an application.

Module Interface : If one module gives some parameters

Module Defects which are not recognised by another, it creates module
interface defects.
Algorithmic
Defects Algorithmic : If design of various decisions aree not
handled correctly then create algorithmic defects.
3. Coding Defect
These defects may arise when design
are implemented wrongly.

Some Coding defects are as…….

Test environment
Defects Variable Declaration
Documentation Defects
Database related defects
Test tool Defects

Test Design
Defects
4.Testing Defect
These Defects are introduced in an
application due to wrong testing or defect in
the test artifacts leading to wrong testing.

Test Design Defects

Test tools Defects

Initialization
Defects
Test Environment Defects

Database
related
Defects
4.1.4 Defect management Process Approach

Software defects are expansive ,The cost of finding and correcting defects represents one of the
most expensive software development activities.
4.1.4.1 Principles of Defect management Process

The Primary Goal is to prevent defects

The defect management process should be risk Driven

Defect Measurement Should be integrated into the software

development process

The capture and analysis of the information should be automated

Defect information should be used to improve the process

Defect are caused by imperfect or faulty process

4.1.4.2 Steps in Defect Management process
4.1.4.2 Steps in Defect Management process

Defect Prevention
Implementation of techniques, methodology and standard processes
to reduce the risk of defects.

Deliverable baseline
Establishment of milestones where deliverables will be considered
complete and ready for further development work. When a
deliverable is baselined, any further changes are controlled. Errors in a
deliverable are not considered defects until after the deliverable is
baselined.

Defect Discovery
Identification and reporting of defects for development team
acknowledgment. A defect is only termed discovered when it has been
documented and acknowledged as a valid defect by the development
team member(s) responsible for the component(s) in error.
4.1.4.2 Steps in Defect Management process

Defect Resolution
Work by the development team to prioritize, schedule and fix
a defect, and document the resolution. This also includes
notification back to the tester to ensure that the resolution is
verified.

Process Improvement
Identification and analysis of the process in which a defect
originated to identify ways to improve the process to prevent
future occurrences of similar defects. Also the validation
process that should have identified the defect earlier is
analyzed to determine ways to strengthen that process.

Management Reporting
Analysis and reporting of defect information to assist
management with risk management, process improvement
and project management.
4.1.4.3 Defect prevention process /Defect Fixing

Defect prevention is a framework and ongoing process of collecting the defect data, doing root cause analysis,
determining and implementing the corrective actions and sharing the lessons learned to avoid future defects.
4.1.4.3 Defect prevention process /Defect Fixing

1. Identify critical risks :

2. Estimate Expected Impact:
3. Minimize Expected Impact:
4.1.4.4 deliverable baseline

A deliverable (e.g. work product) is baselined when it reaches a predefined

milestone in its development. This milestone involves transferring the product
from one stage of development to the next. As a work product moves from one
milestone to the next, defects in the deliverable have a much larger impact on
the rest of the system, and making changes becomes much more expensive. A
deliverable is subject to configuration management (e.g., change control) once it
is "baselined."

4.1.4.5 defect discovery

 4.1.4.6 defect resolution process

Defect Resolution in software testing is a step by

step process of fixing the defects. Defect
resolution process starts with assigning defects to
developers, then developers schedule
the defect to be fixed as per priority,
then defects are fixed and finally developers send
a report of resolution to the test manager

4.1.4.7 process improvement

Process improvement involves the

business practice of identifying,
analyzing and improving existing
business processes to optimize
performance, meet best practice
standards or simply improve quality
and the user experience for customers
and end-users.
 4.1.4.8 management reporting

Management reports are a form of business intelligence.

Management reports contain performance data and
analysis. This is so management can make decisions and
advise other senior executives. Often these reports
include proprietary information and are for internal use
only.
 … … … .
… … …
T ha nks …