{'fraction_non_alphanumeric': 0.021379310344827585, 'fraction_numerical': 0.0, 'mean_word_length': 5.364035087719298, '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}}
Guiding Technology Deployment Decisions using a Quantitative Requirements Analysis Technique

Successful and convincing operation of a prototype, deployed in a real setting, is a key step in advancement of many a new technology from research laboratory to real-world use. Often, however, such a deployment must be interjected into a pre-existing context of ongoing activities, established designs and standard practices. That context can pose a number of obstacles, which if unaddressed can preclude success. Careful selection of what demonstration opportunities to pursue, and determination of how best to pursue them, are therefore crucial. A study was conducted to select and plan for deployment of prototypes of integrated system health management (ISHM) software on NASA spacecraft. The study itself utilized our seasoned technology maturation assessment process, based on a quantitative requirements analysis technique. However, this process is typically applied to scrutinize a single technology application at once. In this case there were a number of candidate deployment opportunities. Since it would have been tedious and time-consuming to consider each of them one-by-one, we adapted our assessment process to accommodate their simultaneous consideration. We relate our experience in doing this - the shortcuts we took, the similarities we exploited, and the workarounds we adopted to complete this study in a timely yet effective manner.