{'fraction_non_alphanumeric': 0.016625916870415647, 'fraction_numerical': 0.00293398533007335, 'mean_word_length': 5.982935153583618, '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}}
Integrated Diagnostics: Operational Missions, Diagnostic Types, Characteristics, and Capability Gaps

Abstract : The Acquisition Support Program at the Carnegie Mellon Software Engineering Institute assists organizations that develop Department of Defense hardware/software hybrid systems by participating in technical reviews and other validation activities. During recent customer engagements, it has been noted that some development teams do not demonstrate a consistent understanding of integrated diagnostic system needs. In particular, software engineers seem to lack the experience needed in this area. Since software engineers frequently derive the low-level requirements for developing diagnostic systems, a lack of knowledge about deployed testing environments can have a significant impact. Failure to adequately address the integrated testing needs of a system profoundly impacts its supportability and, consequently, the cost of that system throughout its life cycle. This report attempts to fill in these gaps in knowledge and experience by presenting an overview of the operational diagnostic life cycle of a system. In addition, it outlines how a system's operational profile impacts diagnostic tradeoffs. Section 1 presents the motivation for the paper and the intended scope and audience. Section 2 defines types of operational diagnostic missions and presents a diagnostic mission life-cycle model. The diagnostic missions discussed are Verification of Operational Readiness, Fault Detection and Characterization, Fault Isolation, Diagnosis and Repair of Repairables, and Other Maintenance Actions. Section 3 defines testing terms and environments. Section 4 defines characteristics that integrated diagnostic environments should have to support diagnostic missions. Section 5 outlines capability gaps that exist in current diagnostic environments. Section 6 addresses advanced topics in integrated diagnostics, such as the embedding of Interactive Electronic Technical Manuals and the concept of Prognostic Health Management.