{'fraction_non_alphanumeric': 0.007537688442211055, 'fraction_numerical': 0.0, 'mean_word_length': 5.602209944751381, '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}}
Maintaining verification test consistency between executable specifications and embedded software in a virtual system integration laboratory environment

The root causes of the majority of software defects discovered during the integration test phase of an embedded system development project have been attributed to errors in understanding and implementing requirements. The independence that typically exits between the system and software development processes provides ample opportunity for the introduction of these types of faults. This paper shows a viable method of verifying object software using the same tests created to verify an executable specification-based system design from which the software is developed. If the object software passes the same tests used to verify the system design, it can be said that the software has correctly implemented all of the known system requirements. This method enables the discovery of functional faults prior to the system integration test phase of a project. Previous research has shown that finding software faults early in the development cycle not only improves software assurance, but also reduces software development expense and time.