Summary: Software failures are very common and fault localization is always an important, but laborious activity. In practice, developers are aware of the number of failed test cases for their programs, but they are unaware of whether a single fault or many faults caused those failures. Generally, developers start with one fault at a time and they consider a single test case to find the cause of failures. After a fault is found and fixed, the program is tested again to determine whether the previously failing test case now passes. If any further failure is found, the debugging process is conducted again. This process is called sequential debugging in literature. It is a time-consuming process and requires a set of test cases indicating presence of each of the faults. Sometimes, the presence of multiple faults in a program inhibits the ability of the fault localization techniques as certain faults mask other faults. In absence of appropriate test cases, some faults may remain unidentified for years.
This project aims to eliminate the need of test cases and the need for repeated invocation of the fault localization method. In model-based fault localization methods, the correct model of each program being diagnosed is assumed to be available. In general, these techniques require test cases and user-specified assertions to localize the fault. The aim of the proposal is to project a model-based fault localization method which takes the correct and the faulty programs as inputs. It would indicate the code segment responsible for fault in the faulty program with respect to the correct program for every fault and the method would not require user-specified assertions or test cases.
If you are interested in applying, please send an email to me or submit your interest below
If you are interested in applying, please send an email to me or submit your interest below.
Please follow the eligibility criteria given in the page 6 of the link : LINK