Using Argumentation to Explain Ambiguity in Requirements Elicitation Interviews

Abstract

The requirements elicitation process often starts with an interview between a customer and a requirements analyst. During these interviews, ambiguities in the dialogic discourse may reveal the presence of tacit knowledge that needs to be made explicit. It is therefore important to understand the nature of ambiguities in interviews and to provide analysts with cognitive tools to identify and alleviate ambiguities. Ambiguities perceived by analysts are sometimes triggered by specific categories of terms used by the customer such as pronouns, quantifiers, and vague or under-specified terms. However, many of the ambiguities that arise in practice cannot be rooted in single terms. Rather, entire fragments of speech and their relation to the mental state of the analyst need to be considered. In this paper, we show that particular types of ambiguities can be characterised by means of argumentation theory. Argumentation is the study of how conclusions can be reached through logical reasoning. In an argumentation theory, statements are represented as arguments, and conflict relations among statements are represented as attacks. Based on a set of ambiguous fragments extracted from interviews, we define a model of the mental state of the analyst during an interview and translate it into an argumentation theory. Then, we show that many of the ambiguities can be characterized in terms of 'attacks' on arguments. The main novelty of this work is in addressing the problem of explaining fragment-level ambiguities in requirements elicitation interviews through the formal modeling of the analyst's mental model using argumentation theory. Our contribution provides a data-grounded, theoretical basis to have a more complete understanding of the ambiguity phenomenon, and lays the foundations to design intelligent computer-based agents that are able to automatically identify ambiguities.

Requirements Smells como indicadores de má qualidade na especificação de requisitos: Um Mapeamento Sistemático da Literatura

“…Os tipos de Requirements Smells descritos por [20,21] Observa-se que algumas pesquisas estão investigando problemas de má qualidade na especificação de requisitos e fazendo uso do catálogo de Requirements Smells proposto por [20] e apresentado em [21]. Também, outras anomalias que não estão presentes no catálogo proposto por [20] [4,15,19,22,25,26,27,28,29,33,36,41,43,45,47,50,51] 17 Utilizam ferramentas de terceiros [3,8] 2…”

RationalGRL: A framework for argumentation and goal modeling

“…Thus, a generic argument is any element in the RationalGRL model that is not an intentional element or an actor. In the example, some of the generic arguments are (13, GenArg, Redundant) and (14,GenArg,Necessary). Note that a constraint of a GRL model (Definition 6) is that GRL links should connect IEs, which means that in generic arguments cannot be connected with GRL links.…”

“…Dung's semantics [13] are then used to determine the risks that are still valid, and those that have been successfully rejected. Elrakaiby et al [14] use argumentation to explain ambiguity. They define when a statement by a client who is being interviewed about the requirements of a system presents an inconsistency or an insufficiency.…”

Conceptualising, extracting and analysing requirements arguments in users' forums: The CrowdRE‐Arg framework

“…Also, by identifying the key arguments, they are able to find user's concerns and preference. 24 Issue: the code of 'issue' is assigned to a user comment in the forum if it submits a problem or challenge to the software under discussion. As…”