0% found this document useful (0 votes)
54 views2 pages

Cs607 Ass.2

Uploaded by

mahnoornaseem805
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
0% found this document useful (0 votes)
54 views2 pages

Cs607 Ass.2

Uploaded by

mahnoornaseem805
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

MAHNOOR NASEEM

BC200409543

Assignment 2:
Defects

Defects can be classified into three categories. These are as follows along with brief explanation
of them.

● Defect Prevention - Error Source Removal: Defect Prevention is the process of addressing
root causes of defects to prevent their future occurrence.

● Defect Detection: it’s a process to detect and remove defects as early/many as possible
through various approaches like QA, code reviews, code inspection and design review.

● Defect Containment: It measures the amount of defects that any QA team was able to find as
a portion of total defects i.e. found by QA, appeared as run-time error. The focus of this activity
is to reduce/eliminating escaping defects.

Scenario

Imagine you are part of a software development team working on a new mobile application. The
app is designed to help users track their daily habits and provide reminders for their activities.
Your team has encountered a few defects during the development process. Below are
descriptions of three defects found at different stages:

Defect A: During a code review, it was noticed that a section of the code responsible for sending
notifications had a logical error. This was corrected before any further development.

Defect B: During a QA testing phase, a bug was found that caused the app to crash when users
tried to add a new habit. The bug was fixed before the app was released.

Defect C: After the app was released, users reported that reminders were not being triggered on
specific days. This issue was identified and fixed in a subsequent update.

Question

Based on the scenario provided, classify each defect (A, B, and C) into one of the three
categories of defects (Defect Prevention, Defect Detection, and Defect Containment). Explain
your reasoning for each classification.

Solution:
Defect A classified as “Defect Prevention”:

Description: It was noticed that a section of the code responsible for sending notifications had a
logical error during a code review,. This was corrected before any further development.

Reasoning: This defect was caught during a code review process, which is a proactive process
where developers scrutinize code for identifying and fixing issues early in the development
lifecycle. By addressing the logical error before it could lead to any further development or
testing phases, the team prevented the defect from manifesting into a more serious issue
downstream. It focuses on eliminating root causes of defects before they occur, which aligns
perfectly with the scenario described.

Defect B is classified as “Defect Detection”:

Description: A bug was found that caused the app to crash when users tried to add a new habit
during a QA testing phase The bug was fixed before the app was released.

Reasoning: This defect was discovered during the QA testing phase, where the primary
objective is to detect and identify issues within the software. Finding the bug during this stage
allowed the team to fix it before the users prevent it. QA testing involves various approaches like
functional testing, integration testing, and user acceptance testing. In this case, the bug causing
the app to crash was detected during these tests, indicating that the defect was found through the
process of defect detection.

Defect C is classified as “Defect Containment”:

Description: After the app was released, users reported that reminders were not being triggered
on specific days. This issue was identified and fixed in a subsequent update.

Reasoning: Defect containment refers to minimizes the defects and measures taken to limit the
impact of defects that have already occurred and escaped detection during earlier phases. In this
scenario, defect wasn’t identified until after the app was released and the issue with reminders
not being triggered was not caught during development or QA testing phases but rather surfaced
after the app was released and used by customers. The team identified and contained the defect
by addressing it in a subsequent update, thus preventing it from causing further dissatisfaction or
issues for more users.

You might also like