{'fraction_non_alphanumeric': 0.019487179487179488, 'fraction_numerical': 0.0, 'mean_word_length': 4.951219512195122, '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}}
Current trends of the software reliability in Japan and needs of future related activities

Recently, software development is following hardware development in terms of features such as downsizing and short time-to-market. In the past, software development took place slowly in a centralized computer environment. On the other hand, recent software has the potential to be released in a rather short development time, because of the availability of distributed development environments and workstations. In this kind of short lifecycle, software reliability should be a central quality concern but not be overwhelmed. The trade-off among different factors of qualities becomes even more important than in the traditional big size development style. We have to evaluate the acquired quality in quantitative way, and in order to do this we need a suitable measure. To have such a measure, we need to have appropriate data we can analyze. As a result, we must have precise data.