{'fraction_non_alphanumeric': 0.010484927916120577, 'fraction_numerical': 0.0, 'mean_word_length': 5.211382113821138, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Development principles for evolving performance models

Systems Engineers at Ball Aerospace utilize System Performance Models to predict and track sensor hardware performance, and often to support requirements verification for many of the sensor systems we build. Models can evolve to serve a variety of purposes as sensor development priorities shift through the phases of the program. Consideration of the potential uses of a performance model at the very start of its development allows the evolution of the model to be efficient and effective over a program life cycle. In this paper, we describe performance model evolution over a program life-cycle, and point out some modeling methods that make our performance models key elements of our technical success.