{'fraction_non_alphanumeric': 0.029003783102143757, 'fraction_numerical': 0.0, 'mean_word_length': 5.5850622406639, '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}}
"Worlds" in Requirements Acquisition and Modelling

The approach presented here is based on the concept of Enterprise Modelling, where different modelling "worlds", or sub-models, are used. The objectives submodel describes, the "why", the long term intention or vision of the enterprise we are discussing or designing. The concept sub-model describes what "things" (phenomena) developers are talking about, using a conceptual modelling technique. The activities of the enterprise as well as the actors involved in these activities, are described in corresponding sub-models of the requirements specification. These models may describe an existing situation, or a future, desired situation. The requirements, functional as well as non-functional, regarding the supporting information system, are described in the information system requirements as two additional sub-models of the specification. A requirements specification is not developed in a simple, straightforward fashion. Many intermediate, and sometimes alternative design versions may exist. In order to deal with this, models to describe different configurations of designs and specifications are needed. Finally, it is necessary to link the requirements descriptions to the formal design specifications of the information system, the information systems sub-model. This give eight interrelated sub-models to be developed and maintained in requirements acquisition. In this paper also the process of modelling is discussed and the Enterprise Modelling approach is assessed by comparing it with a number of related approaches.