{'fraction_non_alphanumeric': 0.016170212765957447, 'fraction_numerical': 0.002553191489361702, 'mean_word_length': 5.758620689655173, '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}}
8.6.1 Integrating Failure Modes and Effects with the System Requirements Analysis

Assessing failure modes and effects as part of the system requirements analysis activity provides specific benefits. Using the concept of functional failure, the requirements analyst, whose primary focus is system functionality, can address the failure of any identified function to be performed as part of the functional analysis. The requisite behavior is documented as a new route to an existing function, or may be a new function altogether. Such integration reduces rework later in the program, since all conditions (nominal and fault) can be identified while requirements are being formulated, well ahead of integration testing. We find also that focusing on conditions associated with requirements stimulates better requirements analysis and documentation, leading to better implementation by designers. In addition, identifying all functional failure modes and their effects during the requirements analysis activity allows the requirements analyst to verify requirements completeness. This provides a management metric for measuring completeness of the requirements analysis process.