{'fraction_non_alphanumeric': 0.01564245810055866, 'fraction_numerical': 0.0, 'mean_word_length': 5.492753623188406, '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}}
From Goal-Oriented Requirements to Architectural Prescriptions: The Preskriptor Process

The step from the requirements for a software system to an Architecture for the system has traditionally been the most complex one in the software development process. This step goes from what the system has to achieve, to how it achieves it. In order to make this step easier, we propose the use of Preskriptor, a prescriptive architectural specification language, and of its associated process, the Preskriptor process. Architectural prescriptions consist in the specification of the system’s basic topology and of the constraints associated with it and its components and interactions. The Preskriptor process provides a systematic way to satisfy both the functional and non functional requirements from the problem domain, as well to integrate architectural structures from well known solution domains.