{'fraction_non_alphanumeric': 0.024080267558528427, 'fraction_numerical': 0.006688963210702341, 'mean_word_length': 5.338983050847458, '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}}
Toward a Consistent and Strictly Model-Based Interpretation of the ISO/IEC/IEEE 29119 for Early Testing Activities

Effective and sufficient testing has always been a challenging task in software development. The ongoing increase of software complexity forces developers and testers to make extensive use of the concept of abstraction, thereby leading to model-based approaches. Further, standardization organizations aim forion, thereby leading to model-based approaches. Further, standardization organizations aim for harmonized process templates to assure a certain quality level of the processes behind. In order to combine the process-level advice as well as the concept-level advice, we aim for a consistent and strict application of model-based methodologies throughout the testing processes, introduced by the ISO/IEC/IEEE 29119 standard for software testing. After a brief introduction to the standards content and a critical view on it, we focus on our model-based interpretation of the postulated processes. Thereby, we extend the original idea of model-based testing, incorporating the separation of concerns on the model-level, to form a broad information basis. Subsequent activities are aligned with these concepts, in order to make sure a purely model-based testing life cycle, with respect to consistency and quality of development artifacts. Following the related work of impacted research areas, we end up with a conclusive statement on the intended combination of approaches.