{'fraction_non_alphanumeric': 0.014054054054054054, 'fraction_numerical': 0.004324324324324324, 'mean_word_length': 5.859259259259259, '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}}
Avionics product line software architecture flow policies

In 1995, an initiative was launched to assess the, potential for reuse of operational flight program software across multiple fighter aircraft platforms, and to define and demonstrate a supporting system architecture based upon open commercial hardware, software, standards and practices. The following year, this validation of the product line approach led to broader application of the techniques to the tactical aircraft mission processing domain. Key aspects of the component based logical architecture developed have been previously described. This paper briefly restates principle results from the previously published work to set the context for discussion. It then describes the flow policies, to be subsequently defined, developed on the project that substantively affect the product line reusability and suitability of the developed application components.