{'fraction_non_alphanumeric': 0.024361948955916472, 'fraction_numerical': 0.0, 'mean_word_length': 5.712062256809339, '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}}
Non-technical aspects of using Ada

Since the beginnings of the drive to install Ada as the predominant Department of Defense mission-critical high order language, the primary emphasis has been placed on resolving the technical issues confronting the software engineering community. While emphasis on items such as compiler validation, compiler efficiencies, and programming support environment capabilities has been valid, it has tended to mask several other, critical, non-technical aspects of Ada use" tool and environment uniqueness, environmental complexity, data disclosure, and software licensing. Significantly new to most software managers, these non-technical aspects are equally and in some cases more important to successful Ada-based project performance than the more well-known and widely discussed technical ones. The non-technical aspects of Ada use arise for several reasons. Most notable is the multi-source, ultra-competitive compiler development and procurement process encouraged by the ultimate Ada-based software users; particularly the United States Department of Defense. When coupled with recent concomitant changes in software protection policies and procedures, non-technical areas of software acquisition and management previously requiting only modest activity have, by virtually unknowing default, been expanded to require major efforts by procurement and legal specialists. The challanges confronting Ada-based software managers are critical; in many cases having the potential to sway the balance between a successful, profitable program and a failure. This paper discusses the more significant non-technical aspects of using Ada; aspects which, for the most part, continue to be overlooked.