Software Defect Attributes

Defect Attributes
(deals with important aspects of identification, categorization, classification, resolution and closure of bugs/ defects/ deviations).

A defect is any flaw or imperfection in a software work product or software process

Software work product is any artifact created as part of the software process,

Software process is a set of activities, methods, practices, and transformations that people use to develop and maintain software work products.

What is Defect Analysis?– A method to find the cause of the defect that has occurred.

Why is it necessary?– To aid the individual/ team to focus on predicting those defects that affect Project and Product performance.

Most defect prediction techniques used in planning rely on historical data,
– Defect prediction techniques vary in the type of data involved,
– Some require little data, some more,
– Some use work product characteristics, others require defect data only.

Some of the prominent attributes related to a defect are given below.

# Defect attributes are mainly dependent on the following
a. Problem status,
b. Problem type,
c. Uniqueness,
d. Criticality level,

# Problem Status
1. Open (An Open defect/ bug will be acted upon in the following manner).
a. Recognized
b. Evaluated
c. Resolved
2. Closed

# Problem Type (A defect will fall under the following).
a. Software Defect
b. Requirements defect,
c. Design defect
d. Code defect,
e. Operation defection (functional)
f. Test case defect
g. Others (H/w, OS, User mistake, Operation mistake, New requirement, enhancement).

# Uniqueness (determining if the bug is original or duplicate)
a. Original
b. Duplicate

# Criticality Level (how the defect is to be resolved and tackled)
a. Identify suitable levels of urgency

# Recognition (The primary details related to the defect/ bug?)
a. What is the problem?
b. When was the problem reported?
c. Who reported the problem?

# Evaluation (How can we tackle and resolve the bug?)
a. What work product caused the problem?
b. What activity discovered the problem?
c. What activity introduced the problem?

# Resolution (Will the solution plug the bug or have other manifested behavior?)
a. What work needs to be done?
b. What work products will be affected by the change?
c. What are the prerequisite changes?

# Closure (The closure mechanism identified for the bug)
a. When are the changes expected?
b. What configuration contains the changes?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s