{'fraction_non_alphanumeric': 0.01568627450980392, 'fraction_numerical': 0.0, 'mean_word_length': 5.436974789915967, '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}}
Employing Enterprise Architecture for Applications Assurance

Before writing a single line of code, software engineers can increase application assurance by instituting the practice recommendations articulated in their enterprise architecture. Many Common Weakness Enumerations (CWEs) can be addressed in the architecture and design phases of the development life cycle. Architectural and design flaws found late in the SDLC can be costly to repair; often, these flaws are so baked into the application that they're resistant to code patches. The only viable response might be to catalogue their existence for a later redesign of the application. Moreover, patches to flaws can inject additional defects as well as alert adversaries to the existence of these flaws.