{'fraction_non_alphanumeric': 0.019553072625698324, 'fraction_numerical': 0.0, 'mean_word_length': 5.213872832369942, '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}}
A Systematic Approach to Choose the Data Warehouse Architecture

In the design phase of a data warehouse, an appropriate architecture must be selected. To this aim, the engineer assesses various alternatives, depending on the requirements of the specific context. Usually, he chooses it heuristically, based on his experience. However, it must be considered that there are many parameters to be taken into consideration. In this regard, many security problems are due to poor design, as well as the performance may not be appropriate to the reference context, or the expected costs and implementation times could be exceeded. A method of choosing the architecture based on heuristics does not always require a prior and systematic evaluation of all the parameters that distinguish the different architectures and, therefore, the system is easily exposed to various problems, the first of which is the system security. Instead, all these parameters should always be considered in a systematic way, without excluding anyone, to define the importance they have in the reference