{'fraction_non_alphanumeric': 0.019652305366591082, 'fraction_numerical': 0.0007558578987150416, 'mean_word_length': 5.396135265700483, '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}}
Needs Analysis and Technology Alignment Method

Our research (reported in two parts) improved software for a NASA Mission Controller group for the International Space Station and provided evidence for a key factor we believed contributed to the expected improvement. This factor is the degree of alignment of the technology to the structure of the work it is intended to support, or its fitness-for-purpose. This paper, Part 1, reports our needs analysis and software redesign, which provide specific and more general contributions. The specific contribution was new prototype software for planning work of the Attitude Determination and Control Officer group, who schedules trajectory and orientation changes of the International Space Station, with its Russian counterparts. The general contribution was a new needs analysis method, product-document analysis, a general design-process benefit. Product document analysis is a method complementary to task analysis and work domain analysis. Our needs analysis method characterized the high-level structure required of acceptable plans in terms of the plan components and their relations and constraints. The redesigned software was better aligned with the structure of work, as captured by needs analysis. We discuss conditions when product-document analysis may be useful.