{'fraction_non_alphanumeric': 0.028985507246376812, 'fraction_numerical': 0.0, 'mean_word_length': 5.27972027972028, '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}}
Post-mortem assessment of interface changes for an evolving, object-oriented, “not-so-rapid” prototype

During the past six years, the MITRE Corporation has implemented a series of not-so-rapid prototypes demonstrating to the U.S. Air Force the application of object-oriented technology to tactical information processing problems. Not-so-rapid prototyping describes the development of software proofs of concept that demonstrate the look and feel of automated solutions, subject to a rigorous deadline. Much of the underlying functionality of the prototype must be developed, however, nearly to the level of a beta version, but within a relatively short time period. This enables intermediate versions of the software to be demonstrated and exercised in a real-time, operational environment to help identify system requirements that continue to grow and change even during the prototyping effort.