Ambiguity as a resource to disclose tacit knowledge
Authors:
- 1 August 2015
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 26-35
Abstract
Interviews are the most common and effective means to perform requirements elicitation and support knowledge transfer between a customer and a requirements analyst. Ambiguity in communication is often perceived as a major obstacle for knowledge transfer, which could lead to unclear and incomplete requirements documents. In this paper, we analyse the role of ambiguity in requirements elicitation interviews. To this end, we have performed a set of customer-analyst interviews to observe how ambiguity occurs during requirements elicitation. From this direct experience, we have observed that ambiguity is a multi-dimensional cognitive phenomenon with a dominant pragmatic facet, and we have defined a phenomenological framework to describe the different types of ambiguity in interviews. We have also discovered that, rather than an obstacle, the occurrence of an ambiguity is often a resource for discovering tacit knowledge. Starting from this observation, we have envisioned the further steps needed in the research to exploit these findings.Keywords
This publication has 29 references indexed in Scilit:
- The role of domain knowledge in requirements elicitation via interviews: an exploratory studyRequirements Engineering, 2012
- Relevance-based abstraction identification: technique and evaluationRequirements Engineering, 2011
- Analysing anaphoric ambiguity in natural language requirementsRequirements Engineering, 2011
- On the Systematic Analysis of Natural Language Requirements with CIRCEAutomated Software Engineering, 2006
- The syntactically dangerous all and plural in specificationsIEEE Software, 2005
- Market research for requirements analysis using linguistic toolsRequirements Engineering, 2004
- Effective Communication in Requirements Elicitation: A Comparison of MethodologiesRequirements Engineering, 2002
- Requirements engineering: making the connection between the software developer and customerInformation and Software Technology, 2000
- NL-OOPS: from natural language to object oriented requirements using the natural language processing system LOLITANatural Language Engineering, 1996
- ACRE: selecting methods for requirements acquisitionSoftware Engineering Journal, 1996