{'fraction_non_alphanumeric': 0.01993067590987868, 'fraction_numerical': 0.0, 'mean_word_length': 5.754385964912281, '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}}
Mapping Functional Requirements: From Natural Language to Conceptual Schemata

Natural language requirements specifications for complex application systems are difficult to analyze and to validate. Consequently, a more formal language for requirements representation is needed that is, for the purpose of validation, understood by endusers (i.e. the requirements owners), as well as by system analysts and developers. Often, the Unified Modeling Language UML is proposed for that purpose. But it is the authors’ experience that especially in non-technical environments UML does not meet the capabilities and interests of end-users so that many development projects still suffer from an incomplete requirements validation. We therefore propose an approach that is based on a more end-user oriented modeling language and that provides mechanisms for both: an automatic transformation of natural language requirements specifications into that modeling language, and after validation, an automatic transformation to UML or other conceptual languages. This paper concentrates on how our approach deals with requirements concerning information system behavior.