2023

Name -: Ruchin Shinde

Student Number -: 8846140
Course number -: QUAL8350
Section-: 1
Professor Name-: Gunjan Sharma
Date assignment Due-: 11/02/2023
Word Count-:

Assignment 3
DECLARATION
I, Ruchin Shinde, affirm that the attached work is entirely my own, except where the words or ideas of
other writers are specifically acknowledged in accordance with accepted APA citation conventions. This
assignment has not been submitted for any other course at Conestoga College or any other global
institution. I acknowledge that I have revised, edited, and proofread this paper, and I certify that I am the
author of this paper. Any assistance I received in its preparation is fully and properly acknowledged and
disclosed. I have also cited any sources from which I used data, ideas, theories, or words, whether
quoted directly or paraphrased. I further acknowledge that this paper has been prepared by myself
specifically for this course.

Ruchin Shinde
Table of Contents
DECLARATION..............................................................................................................................................2
Introduction-:..............................................................................................................................................4
Test Case Plan:.............................................................................................................................................5
Defect Management is the coordinated approach to detect, classify, resolve, validate, conclude, and
document software bugs. Here's a brief explanation of each step:

Discovery: This is the initial identification of a bug. The purpose is to capture any discrepancies from the
expected results in the software.

Categorization: Here, defects are sorted based on type, severity, and impact. This aids in prioritizing
which bugs to address first and allocates resources efficiently.

Resolution: In this phase, developers address and rectify the identified defect. The purpose is to ensure
that the software meets its intended functionality and quality.

Verification: Testers reassess the software to confirm that the defect has been correctly fixed and that no
new issues have been introduced.

Closure: Once verified, the defect is officially closed. This signifies that the issue has been resolved to
satisfaction.

Reporting: At the end of a project, a comprehensive defect summary is created. This provides insights
into software quality, areas of improvement, and ensures lessons are learned for future projects.
Defect Log: