{'fraction_non_alphanumeric': 0.019077901430842606, 'fraction_numerical': 0.0, 'mean_word_length': 5.023923444976076, '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}}
A Method to Diagnose Self-weaknesses for Software Development Organizations

A root cause is a source of a defect such that if it is removed, the defect is subsequently decreased or removed. By analyzing the root causes of defects of our software projects, we will be able to determine the weaknesses of our software development teams. We could thus decide on how much effort to be invested on specific actions to improve the weaknesses of the teams. In this paper, we first described how defects were objectively collected during project development. Second, the root causes were defined and categorized into six groups. Then we focused on analyzing defects to find out their root causes. Based on statistical results, the weaknesses of the project teams were determined. The results showed that the disturbing defects in our projects were mainly injected in the design phase, especially in the detail design phase. Moreover, we should invest considerable effort on enhancing our detail design skills, such as designing components, algorithms and interfaces, and so on. Some corrective actions and prevention proposals would correspondingly be acted upon and planned, respectively. Overall, we believe that our experiences and methods are worthy of sharing.