{'fraction_non_alphanumeric': 0.01020408163265306, 'fraction_numerical': 0.0, 'mean_word_length': 5.719178082191781, '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}}
Considering the Exceptional : Incorporating Exceptions into Property Specifications

Property specifications concisely describe aspects of what a system is supposed to do. It is important that these specifications be correct, describing all the desired behavior and ruling out undesired behavior. Our experience shows that properties are sometimes specified incorrectly because specifiers fail to take into account some exceptional behaviors of the system. In previous work we presented PROPEL, a tool that guides specifiers through the process of creating understandable yet precise property specifications. Here we describe extensions to PROPEL that allow specifiers of a property to indicate what exceptions should be considered and what impact those exceptions should have on the acceptability of system behavior. Although the description is given in terms of the framework provided by PROPEL, the issues specifiers must consider would apply to other specification formalisms.