Software Fault Localization Using Program Slicing Techniques

Abstract

Software fault localization is important for reducing debugging effort by identifying the program statements, variables, methods, or control paths most likely responsible for observed failures. Large software systems often contain complex control flow, data dependencies, conditional logic, and interactions between modules, making manual fault identification time-consuming and error-prone. Traditional debugging approaches may depend heavily on developer experience, test logs, or repeated code inspection, but these methods may not clearly isolate the exact region where a fault originates. This article focuses on software fault localization using program slicing techniques by examining how static slicing, dynamic slicing, backward slicing, and forward slicing can trace the relationship between failure outputs and relevant program statements. The study discusses how slicing can reduce the search space for debugging, improve defect diagnosis, support test failure analysis, and guide corrective maintenance. The article concludes that program slicing provides a structured and practical method for improving fault localization accuracy, reducing repair time, and strengthening software reliability.