{'fraction_non_alphanumeric': 0.02883506343713956, 'fraction_numerical': 0.0, 'mean_word_length': 5.575757575757576, '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}}
On Some Epistemological Problems of Software Engineering

The paper addresses some misconceptions of Software Engineering, requirements analysis and modelling in particular, due to underlying epistemological flaws., e.g. the believe that the system analyst's task be simlar to that of a natural scientist's. The fundamental issues, constitution of objects and signs, conceptualization and definability, are discussed. It comes out that the paradoxical situation of software engineering is having to formalize what cannot be formalized. This is reflected in the fuzzy notion of 'model' in general as well as in the epistemological presumptions of 'object oriented modelling' in particular. The paradigm of 'objective modelling' has to be replaced by a paradigm of 'purposive description' shifting the focus of Software Engineering research to non-formal methodologies.