{'fraction_non_alphanumeric': 0.014074595355383532, 'fraction_numerical': 0.00422237860661506, 'mean_word_length': 5.405405405405405, '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}}
3.7.4 Validating a Commercial Product Architecture

Commercial products in existing industries have an architecture. The functional architecture is implicit from the domain, as envisioned by the founder of the company. The only representation of the functional architecture may be enveloped in the physical architecture. The physical architecture has evolved over time to keep up with innovation and changes in the marketplace. As technology is investigated and sometimes subsequently inserted, the occasion arises to more formally reassess the functional architecture and validate the evolved Physical architecture in regard to expanded functionality and new technology. Today, independent modifications in the various pieces of the product drive substantial changes in the physical architecture. This paper addresses the journey of one commercial company to validate the architecture of the flagship product. The methods and approach will subsequently be used with the other product lines. The goal is a modular architecture with standardized interfaces to enable significant decreases in time to market, and reduction in the cost of production and support. The paper addresses 1) the business drivers for taking the time and resources to do the validation, 2) the methods employed and 3) the plan for evolving the engineering and operations within the company to realize the advantages sought when starting the effort.