Empirical Study of Defect Injection During Requirement and Design Phases

Abstract

Defect injection during requirement and design phases is a major concern in software projects because early lifecycle defects can spread into coding, testing, integration, and deployment activities if they are not detected on time. Requirement-phase defects may arise from ambiguity, incompleteness, inconsistency, missing constraints, and incorrect stakeholder interpretation, while design-phase defects may occur through weak architecture, poor interface definition, incorrect data flow, and unsuitable module decomposition. Traditional defect analysis often focuses on coding and testing defects, but this approach may underestimate the cost and risk created by faults introduced before implementation begins. This article presents an empirical study of defect injection during requirement and design phases by examining defect origin, defect type, detection stage, severity level, correction effort, and phase-wise leakage. The study discusses how early reviews, requirement validation, design inspection, traceability, and stakeholder clarification can reduce defect injection and prevent downstream rework. The article concludes that systematic analysis of requirement and design defects can improve early quality control, reduce correction cost, strengthen project predictability, and support more reliable software development.