What describes the process involving record-keeping, classifying, and identifying impact of defects?

The correct answer is defect management, which refers to the systematic approach taken to ensure that defects in a software product are effectively tracked, documented, categorized, and addressed. This process involves several key activities such as:

• Record-keeping: Maintaining accurate and detailed records of defects, including their nature, severity, status, and any relevant historical data. This is crucial for tracking the lifecycle of defects from detection to resolution.

• Classifying: Organizing defects into categories based on various criteria such as the type of defect (e.g., functional, performance), severity, or the area of the application affected. Classification helps in prioritizing defect resolution efforts and understanding trends in defect occurrences.

• Identifying impact: Assessing the implications of defects on the overall system functionality, user experience, and business objectives. This assessment is vital to determine not only the urgency of addressing a defect but also its potential impact on other components and overall project success.

In contrast, quality assurance focuses on ensuring that the processes involved in software development lead to high-quality outcomes, but it does not specifically deal with tracking and managing defects. Test planning outlines the strategy and approach for testing within a project but does not encompass defect handling. Risk assessment involves identifying and analyzing