 UNIT04.

DEFECT MANAGEMENT

 Defect
1. Definition and Explanation
 A defect is an error, flaw, or imperfection in a software product that causes it to perform
unexpectedly or incorrectly.
 It occurs when the actual result deviates from the expected result during testing.
2. Real-World Examples
 Example 1: A payment gateway fails to process credit card payments correctly.
 Example 2: The app crashes when trying to upload a profile picture.
3. Advantages
1. Helps identify areas where the software can be improved.
2. Provides insights into the development process's quality.
3. Ensures better software performance after fixing.
4. Disadvantages
1. Detecting defects late increases project costs.
2. Not all defects are easy to identify.
3. Tracking and managing defects in large systems can be challenging.

 Root Causes of Defects

1. Requirements Issues
 Ambiguous, incomplete, or misunderstood requirements lead to incorrect
implementation.
 Example: Misinterpreting user needs for a feature.
2. Design Flaws
 Errors in the software design process can result in functional or structural issues.
 Example: Poor database schema design causing slow performance.
3. Coding Errors
 Mistakes in the code during development lead to defects.
 Example: Using incorrect logic or syntax errors.
4. Environment Problems
 Discrepancies in the testing or production environment compared to the development
environment.
 Example: Software working on Windows but failing on Linux due to compatibility issues.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

5. Insufficient Testing
 Failure to adequately test all scenarios, including edge cases.
 Example: Skipping validation tests for rare user inputs.

 Defect Attributes
1. Defect ID

 A unique identifier assigned to each defect for easy tracking and reference.

 Example: Defect-101.

2. Defect Description

 A brief but clear explanation of the defect, including what went wrong.

 Example: "The login button on the homepage is unresponsive."

3. Severity

 Indicates the impact of the defect on the system's functionality.

 Levels: Critical, High, Medium, Low.

 Example: A defect causing a system crash is "Critical."

4. Priority

 Specifies how urgently the defect needs to be fixed.

 Levels: High, Medium, Low.

 Example: A typo on a webpage might have low severity but high priority during a
release.

5. Steps to Reproduce

 A list of actions taken to reproduce the defect.

 Example:

1. Open the app.

2. Navigate to the login page.

3. Enter credentials and click "Login."

6. Status

 The current state of the defect in its life cycle.

 Example States: New, Assigned, Open, Fixed, Retested, Closed.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

 Defect Reporting Guidelines

To ensure effective defect reporting, follow these guidelines:
1. Be Clear and Specific
 Clearly describe the defect with sufficient details.
 Example: Instead of "Login failed," write "Login button is unresponsive when valid
credentials are entered on Chrome browser version X.X."
2. Provide Steps to Reproduce
 Include step-by-step instructions to replicate the defect.
 Example: 1. Open the application.
2. Navigate to the login page.
3. Enter valid credentials and click "Login."
3. Include Expected and Actual Results
 Mention what you expected to happen versus what actually occurred.
 Example: 1. Expected: "User is redirected to the dashboard after login."
2. Actual: "An error message appears saying 'Invalid Request.'"
4. Attach Evidence
 Provide screenshots, logs, or videos to support the report.
 Example: Attach a screenshot of the error message or a video of the issue.
5. Specify Severity and Priority
 Indicate the impact of the defect (severity) and the urgency to fix it (priority).
 Example: Severity: High, Priority: Critical.
6. Include Environment Details
 Mention the environment where the defect was observed.
 Example: OS: Windows 11, Browser: Chrome 90.0, App Version: 1.2.3.
7. Use a Standard Template
 Follow a consistent format for defect reports. Example template:
o Defect ID: Unique identifier
o Description: Brief summary
o Steps to Reproduce: Actions leading to the defect
o Severity: High/Medium/Low
o Priority: High/Medium/Low
o Environment: Details of system
o Attachments: Supporting evidence

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

 Defect Classification
1. Definition

 Defect classification categorizes defects based on the stage of the software development
life cycle (SDLC) where they occur.

 It helps in identifying root causes, improving processes, and reducing defects in future
projects.

2. Diagram of Defect Classification

 Classification Categories:

Fig.(a) Defect classification

1. Requirement Defect
Explanation

 These defects occur due to incorrect, incomplete, or ambiguous requirements provided

during the analysis phase.

 They impact the understanding of what needs to be developed, leading to mismatched

deliverables.

Types of Requirement Defects

1. Functional Defect

o Missing or incorrect functionalities in the requirements.

o Example: Forgetting to specify a search feature in an e-commerce platform.

2. Interface Defect

o Problems in specifying how different modules or systems should interact.

o Example: Missing API details for integration between a frontend app and
backend server.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

Real-World Examples

1. Missing a key feature, such as a payment option in an e-commerce application.

2. Misinterpreting a requirement, like developing a mobile app for Android only when both
iOS and Android were required.

Disadvantages

 Difficult to detect in later stages, leading to higher correction costs.

 Causes delays in development as rework is needed to clarify and correct the

requirements.

Additional Points

 Prevention: Use requirement review processes and clear documentation.

 Impact: Results in poor user satisfaction if undetected.

2. Design Defect
Explanation

 Arises from flaws in the software's architecture or design phase, such as improper
system structure or integration logic.

 Leads to inefficiencies or failure to meet functional goals.

Types of Design Defects

1. Algorithm Defect

o Inefficient or incorrect algorithms affecting performance.

o Example: Using a slow sorting algorithm for large datasets.

2. Interface Defect

o Poor design of interfaces between modules or components.

o Example: Designing a frontend that does not handle backend API responses
properly.

Real-World Examples

1. Designing a database schema without normalization, causing redundant data storage.

2. Poor choice of algorithms leading to slow system performance.

Disadvantages

 Redesigning can be time-consuming and costly.

 Impacts system scalability and maintainability.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

Additional Points

 Prevention: Perform design reviews and use modelling tools.

 Impact: Results in long-term technical debt.

3. Coding Defect
Explanation

 Errors made by developers during the implementation phase.

 Includes syntax errors, logic errors, or incorrect handling of edge cases.

Real-World Examples

1. Using = instead of == in conditional statements.

2. Hardcoding values instead of using configurable parameters.

Disadvantages

 Most common and frequent type of defect.

 Increases debugging and testing efforts.

Additional Points

 Prevention: Use code reviews, automated tools, and proper training.

 Impact: Directly affects the functionality and reliability of the application.

4. Testing Defect
Explanation

 Defects introduced during the testing phase, often due to inadequate test coverage or
incorrect test case design.

 Leads to undetected issues being deployed.

Types of Testing Defects

1. Test Design Defect

o Errors in the design of test cases or scenarios.

o Example: Missing edge cases in boundary value testing.

2. Test Tool Defect

o Problems with the tools used for testing, such as incorrect configurations or
limitations.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

o Example: An automated test script failing due to an outdated tool version.

Real-World Examples

1. Missing critical test scenarios, such as stress testing for high-load situations.

2. Using outdated test data, causing inaccurate results.

Disadvantages

 May result in incomplete defect detection.

 Affects overall software quality and customer trust.

Additional Points

 Prevention: Improve test planning, use updated test data, and focus on comprehensive
test cases.

 Impact: Hidden defects might emerge in production environments.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

 Defect Management Process

What is Defect Management?

1. Defect management is the systematic process of identifying, documenting, resolving, and

preventing defects throughout the software development lifecycle.

2. It ensures software quality by reducing the number and impact of defects.

3. The process involves monitoring and improving defect handling strategies for continuous
improvement.

Diagram of Defect Management Process

Fig.(b) Defect management process

1. Defect Prevention
Explanation

 Focuses on identifying potential defect sources and taking proactive measures to prevent
defects from occurring.

 Includes techniques like training, code reviews, and robust design practices.

Examples/Implementation

 Conduct regular code reviews to catch issues early.

 Use static analysis tools to identify vulnerabilities in the code.

Additional Points

 Saves time and cost by reducing the occurrence of defects.

 Requires collaboration between teams during the early stages of development.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

2. Deliverable Baseline
Explanation

 Establishes a stable and agreed-upon version of deliverables (e.g., requirements, design

documents, code) to prevent changes that introduce defects.

 Acts as a reference point for defect tracking.

Examples/Implementation

 Use version control systems like Git to manage baselines.

 Perform baseline reviews before moving to the next phase.

Additional Points

 Ensures all team members work on a consistent version.

 Helps trace defects back to specific deliverables.

3. Defect Discovery
Explanation

 Involves identifying defects through various techniques, such as testing, peer reviews,
and user feedback.

 Ensures defects are documented and categorized for effective resolution.

Examples/Implementation

 Use manual testing to identify usability issues.

 Employ automated test scripts for functional validation.

Additional Points

 Requires maintaining a defect log for tracking and prioritization.

 Helps improve testing efficiency by identifying high-risk areas.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

4. Defect Resolution
Explanation

 Focuses on analyzing, fixing, and verifying defects to ensure they are fully resolved.

 Involves collaboration between developers, testers, and other stakeholders.

Examples/Implementation

 Developers use the debugging process to identify and fix code defects.

 Testers perform regression testing to confirm defect fixes.

Additional Points

 Ensures fixes do not introduce new defects.

 Involves proper documentation of resolved defects for future reference.

5. Process Improvement
Explanation

 Uses insights gained from defect management to enhance processes and reduce future
defects.

 Focuses on learning from past mistakes to optimize practices.

Examples/Implementation

 Conduct root cause analysis to understand recurring defects.

 Implement automated tools to streamline testing and defect tracking.

Additional Points

 Promotes a culture of continuous improvement.

 Helps in aligning processes with organizational quality goals.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

 Defect Life Cycle

Definition and Explanation
 The defect life cycle, also known as the bug life cycle, is the series of stages that a defect
or bug goes through from its identification to its closure.
 This cycle helps in tracking and managing defects efficiently, ensuring all discovered
defects are resolved systematically.
 The stages may vary slightly between projects, but the primary goal remains the same:
to identify, fix, and verify defects.

Diagram of Defect Life Cycle

Fig.(c) Defect life cycle

Explanation of Each State in the Diagram

1. New
o When a defect is identified, it is marked as "New" and awaits review.
o Example: A tester finds a bug in the login functionality and logs it as a new
defect in the tracking system.
2. Assigned
o The defect is reviewed and assigned to a developer or a relevant team member
for resolution.
o Example: The project manager assigns the login bug to a developer who is
responsible for fixing authentication issues.
3. Open
o The developer starts working on the defect, analyzing its cause and working on a
fix.
o Example: The developer begins investigating the login bug to understand why
users cannot access their accounts.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

4. Fixed
o After resolving the defect, the developer marks it as "Fixed" and sends it back to
the testing team for verification.
o Example: The developer fixes the login issue and marks the defect as "Fixed" in
the tracking system.
5. Retest
o The testing team tests the fixed defect to confirm it is resolved and has not
caused any new issues.
o Example: The tester re-tests the login functionality to ensure the bug is fixed and
users can log in successfully.
6. Closed
o If the tester verifies that the defect is resolved and no further issues are found,
the defect status is marked as "Closed."
o Example: After confirming that the login issue is fixed, the tester closes the
defect in the tracking system.
7. Reopen
o If the defect is still present or new issues arise, the tester reopens the defect and
assigns it back to the developer.
o Example: During retesting, if the login issue persists, the tester reopens the
defect for further analysis and fixing.
8. Deferred
o If a defect is low priority or does not impact the current release, it can be
deferred for future releases.
o Example: A minor UI defect in the settings page might be deferred until the next
version, as it doesn’t affect major functionality.
9. Rejected
o If the reported defect is not valid or does not need fixing, it is marked as
"Rejected."
o Example: A tester reports an issue that turns out to be expected behavior. The
developer rejects the defect.
10. Duplicate
o If the defect has already been reported or logged, it is marked as "Duplicate."
o Example: A tester logs a new defect that describes the same issue as an existing
defect, so it is marked as duplicate.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

Diagram Explanation
 New to Assigned: Defect is identified and assigned to a developer.

 Assigned to Open: Developer starts investigating the defect.

 Open to Fixed: The defect is fixed by the developer.

 Fixed to Retest: The defect fix is verified by the QA team.

 Retest to Closed: The defect is confirmed as resolved and marked "Closed."

 Reopened: If the defect recurs, it returns to the lifecycle for resolution.

 Deferred: If the defect is not critical for the current release, it may be deferred for future
consideration.

 Rejected: If the defect is invalid or not a true defect, it is rejected and removed from the
lifecycle.

 Duplicate: If the defect is a duplicate of an existing issue, it is marked accordingly to avoid

redundancy.

Real-Life Examples of the Entire Defect Life Cycle

1. Example 1:

o A tester finds a defect in a banking application where users cannot view

transaction history.

o The defect is logged as "New" and assigned to a developer.

o The developer marks it as "Open" and works on fixing the database query.

o Once fixed, it is sent for "Retest" and eventually "Closed" when confirmed
resolved.

2. Example 2:

o During testing, a minor cosmetic issue is found in the homepage UI.

o It’s marked as "New" and assigned to the developer.

o The developer decides to "Defer" it as it doesn’t impact the functionality for the
current release.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

Advantages of Defect Life Cycle

1. Efficient Defect Tracking

o Provides a systematic approach to track each defect, ensuring no issue is

overlooked.

2. Improves Communication

o Each stage clearly indicates the status of defects, facilitating better

communication between teams.

3. Prioritization of Defects

o Helps teams prioritize defects based on severity, allowing critical issues to be

fixed first.

4. Enhances Product Quality

o Ensures thorough resolution of defects, leading to a higher-quality final product.

Disadvantages of Defect Life Cycle

1. Time-Consuming

o Following each stage can be lengthy, especially if defects are numerous.

2. Complexity in Large Projects

o Managing the defect life cycle can become complicated in large projects with
many stakeholders.

3. Resource Intensive

o Requires dedicated resources for tracking, updating, and managing defects at

each stage.

4. Risk of Rejected or Deferred Defects

o Defects marked as rejected or deferred might lead to unresolved issues affecting

future releases.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

 Defect Template
Definition and Explanation

 A Defect Template is a standardized form used to document details of each defect

identified during software testing.

 It captures key information like defect ID, description, severity, steps to reproduce, and
more, ensuring consistent and complete documentation.

 A well-designed defect template facilitates efficient tracking, analysis, and

communication between testers and developers.

Defect Template Attributes

1. Defect ID

o Definition: A unique identifier assigned to each defect for tracking purposes.

o Example: DEF12345

2. Defect Name

o Definition: A brief title describing the defect.

o Example: "Login Button Not Working"

3. Project Name

o Definition: The name of the project where the defect was found.

o Example: "Online Banking App"

4. Module Name

o Definition: The specific module or feature within the project where the defect
exists.

o Example: "User Authentication"

5. Phase Introduced

o Definition: The phase during development where the defect was initially
introduced.

o Example: "Design Phase"

6. Phase Found

o Definition: The phase during development or testing where the defect was
identified.

o Example: "System Testing"

7. Defect Type

o Definition: The category of defect, such as functional, UI, performance, etc.

o Example: "Functional Defect"

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

8. Defect Severity

o Definition: Indicates the impact level of the defect on the system’s functionality.

o Example: "High" (if the defect blocks user login)

9. Priority

o Definition: Determines the urgency for fixing the defect.

o Example: "P1" (Priority 1, indicating immediate attention)

10. Summary

o Definition: A brief description outlining the defect details.

o Example: "The login button is unresponsive, preventing users from logging into
the system."

11. Status

o Definition: The current state of the defect in the defect life cycle.

o Example: "Assigned" (indicating it is assigned to a developer for fixing)

12. Reported By

o Definition: The name of the person or team who reported the defect.

o Example: "QA Team - John Doe"

13. Assigned To

o Definition: The developer or team responsible for resolving the defect.

o Example: "Dev Team - Alice Smith"

Advantages of a Defect Template

 Ensures Consistency: Provides a standardized way to log defects, reducing errors in

documentation.

 Improves Communication: Clear and detailed information helps developers understand

issues faster.

 Simplifies Tracking: Easy to track defect status, ownership, and history for better process
management.

Disadvantages of a Defect Template

 Time-Consuming to Fill Out: Requires detailed entry, which can be time-intensive for
testers.

 Dependence on Accuracy: Inaccurate or incomplete fields may lead to

misunderstandings or delays.

 Can Be Overwhelming for Small Defects: The extensive format may feel excessive for
minor issues.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

 Techniques of Finding Defects

 Definition:

 Techniques of finding defects are methods used to identify errors, bugs, or

inconsistencies in software throughout its development lifecycle.

 These techniques ensure quality by detecting defects at different stages, reducing

the risk of issues in the final product.

 The primary defect-finding techniques are Static, Dynamic, and Operational, each
offering unique approaches to identify different types of defects.

1) Static Technique
 Explanation:

o Static techniques involve examining code, requirements, or design documents

without executing the software.

o This approach focuses on finding defects early through document reviews, code
inspections, and walkthroughs.

o It helps identify issues related to coding standards, design flaws, and missing
requirements.

 Examples:

1. Code Review: Developers review code to catch syntax errors, logic flaws, or style
violations before execution.

2. Requirements Document Review: Team members review requirements

documents to ensure clarity, completeness, and alignment with user needs.

 Additional Points:

1. Formal Inspection: Structured and formal review meetings where every line of
code or documentation is checked thoroughly.

2. Pair Programming: Developers work in pairs to write and review code in real-
time, minimizing errors immediately.

 Advantages:

1. Catches defects early, reducing the cost and time required for fixing later issues.

2. Improves overall code quality and compliance with standards.

3. Can be used on both code and non-code artifacts (e.g., design or requirements
documents).

4. Facilitates knowledge sharing among team members during reviews.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

 Disadvantages:

1. Cannot detect runtime errors or performance issues.

2. Time-consuming, especially with large documents or complex codebases.

3. Requires skilled reviewers for effective issue identification.

2) Dynamic Technique
 Explanation:

o Dynamic techniques involve running the software to observe its behavior in

various conditions.

o This includes functional, regression, and performance testing to catch issues

during execution.

o Helps in identifying runtime defects, integration issues, and performance

bottlenecks.

 Examples:

1. Unit Testing: Verifying individual components or modules for correct

functionality.

2. Load Testing: Testing how the software performs under high user load,
identifying any scalability issues.

 Additional Points:

1. Automated Testing Tools: Using tools to automate repetitive test cases,

increasing coverage and efficiency.

2. Exploratory Testing: Testers actively explore the application without predefined

scripts to uncover unexpected issues.

 Advantages:

1. Identifies defects that occur during actual software execution, which static
techniques may miss.

2. Ensures the software performs well under various real-world conditions.

3. Helps verify that all components and modules integrate and function as
expected.

4. Supports continuous testing through automation, enabling faster feedback

loops.

 Disadvantages:

1. Requires a fully or partially functional software environment, limiting its use

early in development.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

2. Resource-intensive, needing test data, tools, and environment setups.

3. May miss defects that are not covered by predefined test scenarios.

3) Operational Technique
 Explanation:

o Operational techniques involve testing in a live or simulated production

environment.

o These tests focus on real-world usage scenarios and assess how the software
behaves under actual operating conditions.

o Examples include beta testing, field testing, and usability testing to gather end-
user feedback.

 Examples:

1. Beta Testing: Releasing a beta version to a small group of users for feedback on
functionality and performance.

2. Usability Testing: Observing how end-users interact with the software to identify
any issues in user experience.

 Additional Points:

1. Field Testing: Conducting tests directly in the user’s environment to capture any
issues that may arise in specific conditions.

2. Pilot Testing: Implementing a smaller version of the application in a controlled

environment to identify potential issues.

 Advantages:

1. Provides valuable feedback on software performance in real-world usage

scenarios.

2. Helps identify usability issues and ensures the software meets user expectations.

3. Detects defects that only arise under specific operational conditions.

4. Validates the software's compatibility with different devices, networks, or

platforms in the field.

 Disadvantages:

1. Defects discovered at this stage may be costly to fix, especially if close to release.

2. Testing in live environments can expose users to potential bugs and defects.

3. Requires careful planning to avoid negative impacts on the end-user experience.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

 Reporting a Defect
Definition and Explanation
 Reporting a defect is the process of documenting and communicating a defect (also
known as a bug or issue) found during testing.
 A defect report provides details about the problem, its impact, how to reproduce it, and
the environment where it was found. It is a vital part of the software testing process and
helps development teams fix issues promptly.
 A clear and well-organized defect report ensures that developers understand the issue
quickly and can prioritize its resolution.

Components of a Defect Report

1. Defect ID
o A unique identifier assigned to each defect for tracking purposes.
o Example: DEF-001, BUG-1234.
2. Summary/Title
o A brief, descriptive title that summarizes the defect.
o Example: “Login button unresponsive on Android app.”
3. Description
o A detailed explanation of the defect, including what is wrong and why it is a
defect.
o Example: “The login button on the mobile app does not respond when clicked
after entering valid credentials.”
4. Steps to Reproduce
o A clear, step-by-step guide that helps someone else reproduce the issue. This is
essential for developers to confirm the defect.
o Example:
1. Open the app.
2. Enter valid credentials (username and password).
3. Click the “Login” button.
4. Observe that the button does not respond.
5. Expected Result
o What should happen if the software is working correctly.
o Example: “The user should be logged in successfully and redirected to the
homepage.”

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

6. Actual Result
o What actually happened when the defect was encountered.
o Example: “The login button remains unresponsive, and the user stays on the
login screen.”
7. Severity
o The impact of the defect on the software’s functionality. It can be categorized as:
 Critical: Stops the system from working; high-priority bug.
 Major: A significant issue, but the system still works.
 Minor: A cosmetic or less severe issue.
 Trivial: A very minor issue, not affecting functionality.
8. Priority
o How soon the defect should be fixed, based on business needs or project
timelines.
 High: Needs immediate attention.
 Medium: Should be fixed soon.
 Low: Can be addressed later.
9. Environment
o The software version, hardware, and operating system where the defect was
found.
o Example: “Android version 10, App version 2.3.5.”
10. Attachments
o Screenshots, videos, or logs that help demonstrate the defect.
o Example: A screenshot showing the unresponsive button or a log file that
provides more details.
11. Status
o The current state of the defect, such as:
 Open: The defect has been reported but not fixed yet.
 In Progress: The defect is being worked on by the development team.
 Resolved: The defect has been fixed, but it is not yet verified.
 Closed: The defect has been fixed and verified.
12. Assigned To
o The developer or team responsible for fixing the defect.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

Real-Life Example of Reporting a Defect

 Defect Report Example:
o Defect ID: DEF-101
o Summary: “Payment gateway not responding during checkout”
o Description: The payment gateway hangs and does not complete the
transaction, preventing users from completing their purchases.
o Steps to Reproduce:
1. Add items to the cart.
2. Proceed to checkout.
3. Select a payment method.
4. Click on the “Pay Now” button.
5. Observe that the payment page freezes and no transaction is processed.
o Expected Result: Payment should be processed successfully, and user should
receive a confirmation.
o Actual Result: The payment process freezes, and no confirmation is received.
o Severity: Critical
o Priority: High
o Environment: Chrome version 89, Windows 10, E-commerce website version 1.0
o Attachments: Screenshot of the frozen payment page
o Status: Open
o Assigned To: Developer Team A

Advantages of Reporting Defects

 Clear Communication: A well-documented defect report ensures that developers
understand the problem quickly.
 Efficient Bug Fixing: A clear defect report helps developers fix issues faster and more
accurately.
 Helps in Decision-Making: Defects are categorized by severity and priority, helping
project managers make informed decisions on resource allocation.
Disadvantages of Reporting Defects
 Time-Consuming: Detailed defect reports can take time to prepare, especially when
reproducing defects.
 Quality of Reports: Inadequate or unclear defect reports can lead to confusion and
delays in fixing defects.
 Overwhelming for Developers: Too many defect reports, especially low-priority ones,
can overwhelm developers and hinder their ability to focus on high-impact issues.

Diploma Helper. Feel free to DM us at . 8698079745

  UNIT04. DEFECT MANAGEMENT

 Winter 2019
1. Define Defect (2marks)
2. Enlist different techniques for finding defects and describe any one technique with an example.
(4marks)
3. Draw a diagram for defect life cycle and write example for defect template. (6marks)

 Summer 2022
1. State any four defect reporting guidelines. (2marks)
2. Draw defect prevention process cycle. State working of each phase.(4marks)

 Winter 2022
1. Give the defect classification and its meaning. (2marks)

 Summer 2023
1. State any four attributes of defect. (2marks)
2. Describe detect management process with neat diagram (4marks)

 Winter 2023
1. Write any two root causes of defect. (2marks)
2. Enlist any four attributes of defect. Describe them with suitable example. (4marks)
3. Explain defect management process with suitable diagram. (4marks)
4. Describe defect life cycle with neat diagram. (6marks)

 Summer 2024
1. State the classification of defects. (2marks)
2. Describe detect management process with neat diagram. (4marks)
3. Draw a diagram for defect life cycle and write example for defect template. (6marks)

Diploma Helper. Feel free to DM us at . 8698079745