{'fraction_non_alphanumeric': 0.01415929203539823, 'fraction_numerical': 0.0, 'mean_word_length': 5.389830508474576, '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}}
Using Domain-Specific Modeling to Develop Software Defined Radio Components and Applications

For the past twenty years, there has been a continuous evolution in electronic communications equipment. The evolution can be described as one of moving the radio functionality from being located in the hardware platform running with proprietary processors and circuitry to being located in firmware running on programmable logic and then to being located in software running on general purpose processors. The driving force behind this evolution has been the need to leverage the inherent greater malleability and configurability of software versus that of hardware. As radio functionality continues to move into software, or looking at it another way, as that software moves “closer to the antenna”, it becomes more commercially viable to maintain, configure, test and reuse communications algorithms and functionality as well as the hardware on which it runs. This evolution is very similar to that of the computer itself with today's PCs running applications, the bulk of which exist as software running on general purpose hardware.