{'fraction_non_alphanumeric': 0.013513513513513514, 'fraction_numerical': 0.0, 'mean_word_length': 5.073770491803279, '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}}
The Simulator; Another, Elementary Problem Frame?

Problem framing is recognised as an important new technique for describing the problem context in order to identify and then apply the most appropriate modelling and description techniques to developing different kinds of software system. Jackson has proposed five distinct problem frames and variants on them. However, Jackson makes no claim that this is an exhaustive list. In order to better model certain problem domains, an addition to the published set of elementary problem frames is proposed. We present the Simulator problem frame and describe through example why the Simulator is not solely a variant of the other frames and should be considered a problem frame in its own right.