{'fraction_non_alphanumeric': 0.024390243902439025, 'fraction_numerical': 0.0, 'mean_word_length': 5.6746411483253585, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Application Lifecycle Management While Developing Consumer Electronics Software Using A-SPICE

Electronic Program Guide (EPG) engine software module is developed as a self-contained product. It is characterized by stability, high performance and configurability. It is made to satisfy the wide range of digital television standards and complete set of hardware platforms. Considering that this module can be used in automotive infotainment systems, it has to be in compliance with the Automotive Software Process improvement and Capability Determination (A-SPICE) standard and Hersteller Initiative Software - Manufacturer's software initiative (HIS) metrics. To ensure that all procedures according to A-SPICE were followed and to simplify project management, authors used Application Lifecycle Management (ALM) tool. In static code analysis, code was tested to verify if it's consistent and compliant with the Motor Industry Software Reliability Association (MISRA-C) rules and coding guidelines. Dynamic code testing included unit testing, integration testing and software and system testing. Additional code analysis was done through the code coverage analysis with runtime performance analysis tool. During the project lifecycle there were several problems found and solved concerning complying with A-SPICE standard while using ALM tool, testing procedures and quality of code in general.