{'fraction_non_alphanumeric': 0.011538461538461539, 'fraction_numerical': 0.0, 'mean_word_length': 5.347560975609756, '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}}
Problem frames and business strategy modelling

Requirements engineering describes how an IT implementation will support business functions. Most IT systems are operational in nature and typical requirements engineering techniques and methods are usually adequate in capturing and documenting the requirements for such systems. Jackson's problem frames is a technique that is suitable for straightforward IT systems descriptions. However, when an organization deploys an IT system that must deliver upon its competitive business strategy, then an appropriate technique or method needs to be used to capture that business strategy in order to connect it to business-critical IT requirements. Here we provide an overview of the use and adaptation of problem frames to connect requirements to business strategy. We found that a simplification of the problem frames notation was necessary and that to be really effective, we had to integrate problem fames with goal modelling and Map, a method that helps describe the evolution of IT over time.