{'fraction_non_alphanumeric': 0.02336028751123091, 'fraction_numerical': 0.0, 'mean_word_length': 5.188888888888889, '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}}
Preconceptual-schema-based representation of KAOS goal diagram

Goal diagram helps in linking stakeholder requirements and expectations to software requirements. In addition, the diagram establishes the actor duties and justifies them the importance of the future software. Despite the usefulness of the goal diagram, the projects for specifying or using it do not link it to the stakeholder discourse. Instead, the goal diagram is manually and subjectively created by the analyst based on the information provided by the stakeholder and any help for conceptualizing the diagram is not provided. Also, some elements, like goals, tasks, and requirements are confused. The above reasons lead us to propose, in this paper, a novel way to represent KAOS goal diagram in the so-called pre-conceptual schemas, which allow a closer approximation to the stakeholder discourse. In doing so, we add new elements to pre-conceptual schemas and we define heuristic rules for linking together the goal diagram elements: stakeholder requirements and goals. Furthermore, we present a lab study for reviewing the obtained results.