Scribd
Upload
9 views2 pages

Defect Management Chapter 5

Uploaded by

sangharaj5252
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views2 pages

Defect Management Chapter 5

Uploaded by

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

Defect Management (Chapter 5)

1. What is a Defect?
A defect, or bug, is an error in the software caused by mistakes during its design or
development. These errors indicate flaws in the system, which can affect functionality,
performance, or user experience. Defects can occur at various stages of the Software
Development Life Cycle (SDLC), such as requirements gathering, design, coding, testing, or
deployment. The cost and impact of defects depend on the stage in which they arise and
when they are detected. The earlier a defect is found, the easier and cheaper it is to fix.

2. Causes of Software Defects


1. Miscommunication of Requirements: Incomplete or incorrect understanding of
requirements leads to errors in implementation.
2. Unrealistic Development Timelines: Tight deadlines force developers to rush, increasing
the likelihood of mistakes.
3. Lack of Design and Coding Experience: Inadequate knowledge or skills can introduce
flaws in the design or code.
4. Human Factors: Simple errors caused by developers, such as typos or logic mistakes.
5. Lack of Version Control: Poor version management can result in mismatched or outdated
code.
6. Defective Third-Party Tools: Bugs in external libraries or tools can introduce issues in the
software.
7. Last-Minute Requirement Changes: Sudden changes can disrupt existing workflows and
introduce errors.
8. Inadequate Testing: Poor testing skills or insufficient coverage can leave defects
unnoticed.

3. Defect Classification
Defects are categorized based on Severity and Priority:

a) Severity-Wise Classification:
1. Critical: Causes complete system failure or blocks key functionality. Needs immediate
fixing.
2. Major: Causes noticeable product failure or deviation from expected behavior, but the
system is still usable.
3. Minor: Causes small, non-critical issues that do not affect core functionality.
4. Cosmetic: Issues related to UI or appearance that have no impact on functionality.

b) Priority-Wise Classification:
1. High Priority: Must be fixed immediately as it affects critical functionality or the delivery
schedule.
2. Medium Priority: Important but can be scheduled for a later fix.
3. Low Priority: Non-urgent issues that can be resolved in future releases.

4. Importance of Defect Management


1. Quality Assurance: Ensures the final product meets user expectations and specifications.
2. Cost Control: Identifying defects early reduces the cost of fixing them.
3. Improved Processes: Helps identify weaknesses in the development process and
implement corrective actions.
4. Customer Satisfaction: Delivering defect-free software enhances user trust and
experience.

You might also like