{'fraction_non_alphanumeric': 0.019363762102351315, 'fraction_numerical': 0.0, 'mean_word_length': 5.135593220338983, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Utilizing the Micro-processes of Software Development for Defect Prevention

In recent years progress in quality assurance for software products has mainly been made in the area of testing, i.e. executing the software with the aim to cause failures which in turn are signs for software defects. Inspection techniques seek defects in software artifacts or any other intermediate document directly. As it is, quality assurance departments in software organizations recognize their job mainly as "hunting for bugs". Of course, after finding such problems they still need to be resolved. It's a strange phenomenon that software engineering seems to accept software defects as to be removed after being created by professionals.