{'fraction_non_alphanumeric': 0.011345218800648298, 'fraction_numerical': 0.0032414910858995136, 'mean_word_length': 5.574468085106383, '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}}
Overcoming communication obstacles in user-analyst interaction for functional requirements elicitation

The importance of requirement engineering in the software development process has been widely recognised by the scientific community. One of the major error sources that arise in this phase is represented by ineffectual communication between users and analysts.Valusek and Fryback in [32] identify three classes of communication obstacles to a successful elicitation of requirements. Purpose of this paper is to discuss these obstacles and to identify the structure of a CASE tool that may allow to overcome them.