{'fraction_non_alphanumeric': 0.012732615083251714, 'fraction_numerical': 0.0009794319294809011, 'mean_word_length': 5.269938650306749, '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}}
Requirements Specification with Petri Nets Using the Cube Tool Methodology

Abstract : The distributed nature of command and control requires the consideration of both processes and communications in the formulation of requirements. Cube Tool is a methodology used to derive the processing and communication needs for each system function. An approach is introduced for extending the applicability of Cube Tool to the determination of requirements for C3I systems. First, using Cube Tool for each function, a Petri Net is derived that models all processes and communications for the correct execution of the function. Then, for a given scenario, these nets are interconnected and the steps of the methodology are applied again to derive the Petri Net that represents the mission-dependent requirements for the system. For different modes of operation are considered, different Petri Net are obtained which can then be folded together to obtain a Colored Petri Net representation of the processes and communications needs.