Skip to main content
SpringerLink
Log in

The role of domain knowledge in requirements elicitation via interviews: an exploratory study

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

Requirements elicitation is the first activity in the requirements engineering process. It includes learning, surfacing, and discovering the requirements of the stakeholders of the developed system. Various elicitation techniques exist to help analysts elicit the requirements from the different stakeholders; the most commonly used technique is the interview. Analysts may have domain knowledge prior to the elicitation process. Such knowledge is commonly assumed to have positive effects on requirements engineering processes, in that it fosters communication, and a mutual understanding of the needs. However, to a minor extent, some negative effects have also been reported. This paper presents an empirical study in which the perceived and actual effects of prior domain knowledge on requirements elicitation via interviews were examined. The results indicate that domain knowledge affects elicitation via interview in two main aspects: communication with the customers and understanding their needs. The findings provide insights as to both the positive and negative effects of domain knowledge on requirements elicitation via interview, as perceived by participants with and without domain knowledge, and show the existence of an actual effect on the course of the interviews. Furthermore, these insights can be utilized in practice to support analysts in the elicitation process and to form requirements analysis teams. They highlight the different contributions that can be provided by analysts with different levels of domain knowledge in requirements analysis teams and the synergy that can be gained by forming heterogeneous teams of analysts.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

Notes

  1. Note that, in this context, the term problem-solving refers to inference questions about the domain.

References

  1. Hickey AM, Davis A (2004) A unified model of requirements elicitation. J Manag Inf Syst 20:65–84

    Google Scholar 

  2. Nuseibeh B, Easterbrook S (2000) Requirements engineering: a roadmap. The future of software engineering. ACM Press, New York, USA, pp 37–46

  3. Pitts MG, Browne GJ (2007) Improving requirements elicitation: an empirical investigation of procedural prompts. Inf Syst J 17(1):89–110

    Article  Google Scholar 

  4. Agarwal R, Tanniru MR (1990) Knowledge acquisition using structured interviewing: an empirical investigation. J Manag Inf Syst 7:123–140

    Google Scholar 

  5. Bostrom RP (1984) Development of computer-based information systems: a communication perspective. Comput Pers 9(4):17–25

    Article  MathSciNet  Google Scholar 

  6. Browne GJ, Rogich MB (2001) An empirical investigation of user requirements elicitation: comparing the effectiveness of prompting techniques. J Manag Inf Syst 17:223–249

    Google Scholar 

  7. Davis GB (1982) Strategies for information requirements determination. IBM Syst J 21:4–30

    Article  Google Scholar 

  8. Friedrich WR, Van Der Poll JA (2007) Towards a methodology to elicit tacit domain knowledge from users. Interdiscip J Inf Knowl Manag 2:179–193

    Google Scholar 

  9. Hofmann H, Lehner F (2001) Requirements engineering as a success factor in software projects. IEEE Softw 18(4):58–66

    Article  Google Scholar 

  10. Watson HJ, Frolick MN (1993) Determining information requirements for an EIS. MIS Q 17:255–269

    Article  Google Scholar 

  11. Kassel N, Malloy BA (2003) An approach to automate requirements elicitation and specification. In: Proceedings of the 7th IASTED international conference on software engineering and applications, Marina del Rey, CA, USA, pp 544–549

  12. Coughlan J, Macredie RD (2002) Effective communication in requirements elicitation: a comparison of methodologies. Requir Eng 7(2):47–60

    Article  Google Scholar 

  13. Van Buren J, Cook D (1998) Experiences in the adoption of requirements engineering technologies, CROSSTALK. J Def Softw Engineering 11(12):3–10

    Google Scholar 

  14. Wiley J (1998) Expertise as mental set: the effects of domain knowledge in creative problem solving. Mem Cogn 26(4):716–730

    Article  MathSciNet  Google Scholar 

  15. Berry DM (1995) The importance of ignorance in requirements engineering. J Syst Softw 28(2):179–184

    Article  Google Scholar 

  16. Berry DM (2002) The importance of ignorance in requirements engineering: an earlier sighting and a revisitation. J Syst Softw 60:83–85

    Article  Google Scholar 

  17. Berry DM (2002) Formal methods: the very idea, some thoughts about why they work when they work. Sci Comput Program 42:11–27

    Article  MATH  Google Scholar 

  18. Buxto JN, Randell B (1969) Software engineering techniques: report on a conference

  19. Davis J, Fusfeld A, Scriven E, Tritle G (2001) Determining a project’s probability of success. Res Technol Manag 44(3):51–62

    Google Scholar 

  20. Anton AI, Potts C (1998) The use of goals to surface requirements for evolving systems. In: Proceedings of the ICSE-98: 20th international conference on software engineering, Kyoto, April 1998, pp 157–166

  21. Burton-Jones A, Weber R (1999) Understanding relationships with attributes in entity-relationship diagrams. In: De P, Degross J (eds) Proceedings of the 20th international conference of information systems. Atlanta, GA, pp 214–228

    Google Scholar 

  22. Curtis B, Krasner H, Iscoe N (1988) A field study of the software design process for large systems. Commun ACM 31(11):1268–1287

    Article  Google Scholar 

  23. Kahrti V, Vessey I, Ramesh V, Clay P, Park S (2006) Understanding conceptual schemas: exploring the role of application and IS domain knowledge. Inf Syst Res 17(1):81–99

    Article  Google Scholar 

  24. Rosemann M, Vessey I, Weber R, Raduescu C (2007) Aligning organizational requirements with enterprise systems capabilities: the role of domain-specific knowledge. In: Proceedings of the 13th Americas conference on information systems (AMCIS 2007), Keystone, Colorado, 8–12 Aug 2007

  25. Shaft TM, Vessey I (1995) The relevance of application domain knowledge: the case of computer program comprehension. Inf Syst Res 6(3):286–299

    Article  Google Scholar 

  26. Shaft TM, Vessey I (1998) The relevance of application domain knowledge: characterizing the computer program comprehension process. J Manag Inf Syst 15(1):51–77

    Google Scholar 

  27. Vessey I, Conger SA (1993) Learning to specify information requirements: the relationship between application and methodology. Res Comput Sci 1993:177–202

    Google Scholar 

  28. Blum B (1989) A paradigm for the 1990s validated in the 1980s. In: Proceedings of the AIAA conference, pp 502–511

  29. Kahrti V, Vessey I (2008) Information search process for a well-structured IS problem: the role of IS and application domain knowledge. In: Te’eni D, Rowe F (eds) ICIS 2008 Proceedings. International conference on information systems ICIS 2008, Paris, France, pp 1–15, 14–17 Dec 2008

  30. Ricks RR, Turley-Ames KJ, Wiley J (2007) Effects of working memory capacity on mental set due to domain knowledge. Mem Cogn 35(6):1456–1462

    Article  Google Scholar 

  31. Nguyen L, Carroll J, Swatman PA (2000) Supporting and monitoring the creativity of IS personnel during the requirements engineering process. In: Proceedings of the 33rd Hawaii international conference on system sciences

  32. Schenk KD, Vitalari NP, Davis KS (1998) Differences between novice and expert systems analysts: what do we know and what do we do? J Manag Inf Syst 15(1):9–50

    Google Scholar 

  33. Mich L, Anesi C, Berry DM (2005) Applying a pragmatics-based creativity-fostering technique to requirements elicitation. Requir Eng 10(4):262–275

    Article  Google Scholar 

  34. Chiesi HL, Spilich GJ, Voss JF (1979) Acquisition of domain-related information in relation to high and low domain knowledge. J Verbal Learn Verbal Behav 18:257–273

    Article  Google Scholar 

  35. Glenberg AM, Epstein W (1987) Inexpert calibration of comprehension. Mem Cogn 15:84–93

    Article  Google Scholar 

  36. Parsons J, Cole L (2004) An experimental examination of property precedence in conceptual modeling. In: First Asia-Pacific conference on conceptual modeling (APCCM 2004), Cunedin, New Zealand

  37. Siau K, Wand Y, Benbasat I (1997) The relative importance of structural constraints and surface semantics in information modeling. Inf Syst 22(2–3):155–170

    Article  Google Scholar 

  38. Buchman J, Ekadharmawan CH (2009) Barriers to sharing domain knowledge in software development practice in SMEs. In: Proceedings of the 3rd international workshop on knowledge collaboration in software development (KCSD2009), pp 2–16

  39. Guindon R (1990) Knowledge exploited by experts during software systems design. Int J Man Mach Stud 33:279–304

    Article  Google Scholar 

  40. McAllister CA (2006) Requirements determination of information systems: user and developer perception of factors contributing to misunderstandings. A Ph.D. dissertation, Capella University

  41. Pitts MG, Browne GJ (2004) Stopping behavior of systems analysts during information requirements elicitation. J Manag Inf Syst 21:203–226

    Google Scholar 

  42. Browne GJ, Ramesh V (2002) Improving information requirements determination: a cognitive perspective. Inf Manag 39:625–645

    Article  Google Scholar 

  43. Maiden N, Rugg G (1996) ACRE: selecting methods for requirements acquisition. Softw Eng J 11(3):183–192

    Article  Google Scholar 

  44. Moody JW, Blanton JE, Cheney PH (1998) A theoretically grounded approach to assist memory recall during information requirements determination. J Manag Inf Syst 15:79–98

    Article  Google Scholar 

  45. Davis A, Dieste O, Hickey A, Juristo N, Moreno AM (2006) Effectiveness of requirements elicitation techniques: empirical results derived from a systematic review. In: 14th IEEE international requirements engineering conference (RE’06) 2006

  46. LaFrance M (1987) The knowledge acquisition grid: a method for training knowledge engineers. Int J Man Mach Stud 26(2):245–255

    Article  Google Scholar 

  47. Strauss A, Corbin J (1990) Basics of qualitative research. Grounded theory procedures and techniques. Sage, Newbury Park

    Google Scholar 

  48. Strauss A, Corbin J (1998) Basics of qualitative research: techniques and procedures for developing grounded theory. Sage Publications, Newbury Park

    Google Scholar 

  49. Coughlan J, Lycett M, Macredie RD (2003) Communications issues in requirements elicitation: a content analysis of stakeholder experiences. Inf Softw Technol 45:525–537

    Article  Google Scholar 

  50. Kitchenham BA, Lawrence S, Lesley P, Pickard M, Jones PW, Hoaglin DC, Emam KE (2002) Preliminary guidelines for empirical research. IEEE Trans Softw Eng 28(8):721–734

    Article  Google Scholar 

  51. Svahnberg M, Aurum A, Wohlin C (2008) Using students as subjects—an empirical evaluation. ESEM’08, Kaiserslautern, Germany, 9–10 Oct 2008, ACM Press

Download references

Author information

Authors and Affiliations

  1. Department of Information Systems, University of Haifa, Carmel Mount., 31905, Haifa, Israel

    Irit Hadar & Pnina Soffer

  2. Department of Computer Sciences, University of Haifa, Carmel Mount., 31905, Haifa, Israel

    Keren Kenzi

Authors
  1. Irit Hadar
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Pnina Soffer
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Keren Kenzi
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Irit Hadar.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Hadar, I., Soffer, P. & Kenzi, K. The role of domain knowledge in requirements elicitation via interviews: an exploratory study. Requirements Eng 19, 143–159 (2014). https://doi.org/10.1007/s00766-012-0163-2

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-012-0163-2

Keywords

Search

Navigation