{'fraction_non_alphanumeric': 0.006896551724137931, 'fraction_numerical': 0.0, 'mean_word_length': 5.507462686567164, '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}}
Using Semantic Annotations for Supporting Requirements Evolution

Requirements change for a variety of reasons and at different stages of the project development. Changes to items in a requirements document must be propagated to other items that depend on the changed items in order to maintain their consistency. This paper explores the use of semantic annotations in requirements document templates to support requirements evolution.