{'fraction_non_alphanumeric': 0.008831521739130434, 'fraction_numerical': 0.0, 'mean_word_length': 4.939516129032258, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
A unified approach for successive release of a software under two types of imperfect debugging

The competitive essence of market and the rapid turnover in the technology is shrinking the life of software. A software with bounded functionality cannot survive the high tides of contention. This raise the need for multiple up gradations of the software and consequently the customary approach towards software development process as observed in practice by most of the software firms today is iterative in nature. They are putting in lots of efforts to mark their presence in the market through periodic functional enrichment. But, functional enhancement adds to the existing complexity of the software and at the same time higher prospects of error. On the grounds of increasing complexity and partial insight into the software, the testing team may not prove to be competent enough to perfectly fix the faults by removing or correcting them after failure is detected. Hence, a fault might go unperceived by surviving the selected test cases performed by the testing unit resulting in a phenomenon termed as imperfect debugging. Another possible scenario is when an error get replaced by another one leading to error generation. In this paper we have developed a two stage fault detection and correction model in the presence of two types of imperfect debugging for multiple releases of a software. The proposed model has been validated on real data set for four releases.