{'fraction_non_alphanumeric': 0.01606425702811245, 'fraction_numerical': 0.0, 'mean_word_length': 5.678571428571429, '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}}
Operational definitions for system requirements as the basis of design automation

This paper introduces formal definitions to system requirements as the basis of design automation. Semi‐formal requirements for real‐time systems are expressed in the form of system verification diagrams, and the graph model of behaviour represents the design, capturing three aspects of system behaviour—control, data and interpretation. The design model is considered operational as an underlying token machine governs its actual behaviour. To achieve automatic design synthesis, the semantics of each construct in the requirement model have to be formally defined. These definitions constitute the core of a knowledge base in an automatic design synthesis tool.