{'fraction_non_alphanumeric': 0.019165727170236752, 'fraction_numerical': 0.0, 'mean_word_length': 6.4, '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}}
Evaluating Software Architectures Against Requirements-level Scenarios

Scenarios have been used to express requirements and system behavior throughout software development. Scenarios are used with different representation and semantics across software phases, and these can be related. This paper argues for exploring scenarios as one means for mapping requirements to architecture as well as evaluating architectures against requirements-level scenarios. Additionally, our approach facilitates consistency-checking between requirements and architectures. In our approach, software requirements take the form of ontology-based scenarios, while architectures are described using both structural and behavioral models. Mapping from requirements to architectures is modeled explicitly, then the mapping-model is used to evaluate architectures against original requirements-level scenarios.