{'fraction_non_alphanumeric': 0.020181634712411706, 'fraction_numerical': 0.0, 'mean_word_length': 5.012121212121212, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Some Structural Relationships among Models in the Development of Software-Intensive Systems

In a software-intensive system the requirement is located in the problem world, at some distance from its interface with the machine. The lift-control machine can monitor the request buttons and sensors, and it can switch the motor current for the doors and for the hoisting mechanism; but the requirement is about the arrival of the lift car at a floor, the entry and exit of passengers, and the travel of the car to a floor that has been requested. To take another example, consider the control of a complex traffic intersection with lights, controlled pedestrian crossings, and vehicle sensors built into the road surface. The control computer can monitor the vehicle sensors and pedestrian request buttons, and it can switch lights on and off; but the requirement is about orderly, safe and efficient traffic flow—that is, about the relative movements and positions of vehicles and pedestrians.