{'fraction_non_alphanumeric': 0.015133876600698487, 'fraction_numerical': 0.0, 'mean_word_length': 5.013986013986014, '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}}
The algorithms capture approach to Ada transition

The mandate for the use of the Ada language in Department of Defense software systems, as well as the growing interest in Ada that exists in the commercial software industry, has created the need for planned, systematic transition paths from existing programs to Ada programs. The demands that Ada places on the life-cycle development of software increases the need for careful planning in any Ada transition effort. At the same time, the desire to derive Ada systems from an existing non-Ada baseline also increases the need for careful control of the transition process. This paper examines the general issues behind such a transition, and describes a transition process geared toward maximizing the benefit of the use of the Ada language, while maintaining a tightly-controlled link with existing systems.