{'fraction_non_alphanumeric': 0.0110803324099723, 'fraction_numerical': 0.0, 'mean_word_length': 5.455357142857143, '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}}
Defining business requirements as concerns in data warehouse

This paper discusses the business requirements as concerns in a data warehouse in general and derives the specific information requirements for the AOSDDL (Aspect Oriented Software Development Design Language) design language architecture to implement a data warehouse that is proposed within this work. Research into aspect based business requirements so far has shown that no single solution will meet all possible requirements of aspect oriented data warehouse, and thus, multiple systems for domains with different demands must be able to co-exist and interoperate. The goal is to thoroughly define what the users must have to satisfy their business needs.