{'fraction_non_alphanumeric': 0.014115092290988056, 'fraction_numerical': 0.0, 'mean_word_length': 5.1466666666666665, '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 light-weight proactive software change impact analysis using use case maps

Changing customer needs and technology are driving factors influencing software evolution. Consequently, there is a need to assess the impact of these changes on existing software systems. For many users, technology is no longer the main problem, and it is likely to become a progressively smaller problem as standard solutions are provided by technology vendors. Instead, research will focus on the interface of the software with business practices. There exists a need to raise the level of abstraction further by analyzing and predicting the impact of changes at the specification level. In this research, we present a lightweight approach to identify the impact of requirement changes at the specification level. We use specification information included in use case maps to analyze the potential impact of requirement changes on a system.