The state-of-practice in requirements elicitation: an extended interview study at 12 companies

Requirements engineering remains a discipline that is faced with a large number of challenges, including the implementation of a requirements elicitation process in industry. Although several proposals have been suggested by researchers and academics, little is known of the practices that are actually followed in industry. Our objective is to investigate the state-of-practice with respect to requirements elicitation, by closely examining practitioners’ current practices. To this aim, we focus on the techniques that are used in industry, the roles that requirements elicitation involves, and the challenges that the requirements elicitation process is faced with. As method, we conducted an interview-based survey study involving 24 practitioners from 12 different Swedish IT companies, and we recorded the interviews and analyzed these recordings by using quantitative and qualitative methods. Several results emerged from the studies. Group interaction techniques, including meetings and workshops, are the most popular type of elicitation techniques that are employed by the practitioners, except in the case of small projects. Additionally, practitioners tend to use a variety of elicitation techniques in each project. We noted that customers are frequently involved in the elicitation process, except in the case of market-driven organizations. Technical staff (for example, developers and architects) are more frequently involved in the elicitation process compared to the involvement of business or strategic staff. Finally, we identified a number of challenges with respect to stakeholders. These challenges include difficulties in understanding and prioritizing their needs. Further, it was noted that requirements instability (i.e., caused by changing needs or priorities) was a predominant challenge. These observations need to be interpreted in the context of the study. We conclude that the relevant observations regarding the survey participants’ experiences should be of interest to the industry; experiences that should be analyzed in the practitioners’ context. Researchers may find evidence for the use of academic results in practice, thereby inspiring future theoretical work, as well as further empirical studies in the same area.

[1]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[2]  B. J. Oates,et al.  Researching Information Systems and Computing , 2005 .

[3]  Natalia Juristo Juzgado,et al.  Systematizing requirements elicitation technique selection , 2014, Inf. Softw. Technol..

[4]  Andy P. Field,et al.  Discovering Statistics Using SPSS , 2000 .

[5]  Natalia Juristo Juzgado,et al.  Systematic review and aggregation of empirical studies on elicitation techniques , 2011, IEEE Transactions on Software Engineering.

[6]  Colin Robson,et al.  Real World Research: A Resource for Social Scientists and Practitioner-Researchers , 1993 .

[7]  Irit Hadar,et al.  The role of domain knowledge in requirements elicitation via interviews: an exploratory study , 2012, Requirements Engineering.

[8]  Claes Wohlin,et al.  Experimentation in Software Engineering , 2012, Springer Berlin Heidelberg.

[9]  Lin Liu,et al.  Security Requirements Engineering in the Wild: A Survey of Common Practices , 2011, 2011 IEEE 35th Annual Computer Software and Applications Conference.

[10]  P. Lachenbruch Statistical Power Analysis for the Behavioral Sciences (2nd ed.) , 1989 .

[11]  Marjo Kauppinen,et al.  Challenges of the Customer Organization's Requirements Engineering Process in the Outsourced Environment - A Case Study , 2015, REFSQ.

[12]  Natalia Juristo Juzgado,et al.  Systematizing requirements elicitation technique selection , 2014, Inf. Softw. Technol..

[13]  Michael Felderer,et al.  Preventing Incomplete/Hidden Requirements: Reflections on Survey Data from Austria and Brazil , 2016, SWQD.

[14]  Roel Wieringa,et al.  Quality requirements challenges in the context of large-scale distributed agile: An empirical study , 2019, Inf. Softw. Technol..

[15]  A. de Grip,et al.  Skill Obsolescence, Lifelong Learning and Labor Market Participation , 2005 .

[16]  Michael Felderer,et al.  Requirements Engineering Practice and Problems in Agile Projects: Results from an International Survey , 2016, WER.

[17]  Norbert Seyff,et al.  How cloud providers elicit consumer requirements: An exploratory study of nineteen companies , 2013, 2013 21st IEEE International Requirements Engineering Conference (RE).

[18]  June M. Verner,et al.  Case study: factors for early prediction of software development success , 2002, Inf. Softw. Technol..

[19]  Wayne G. Lutters,et al.  Revealing actual documentation usage in software maintenance through war stories , 2007, Inf. Softw. Technol..

[20]  Björn Regnell,et al.  Requirements are slipping through the gaps — A case study on causes & effects of communication gaps in large-scale software development , 2011, 2011 IEEE 19th International Requirements Engineering Conference.

[21]  M. Patton Qualitative research & evaluation methods , 2002 .

[22]  Mark T True,et al.  Software Requirements , 2005 .

[23]  Ivan A. Garcia,et al.  Requirements elicitation techniques: a systematic literature review based on the maturity of the techniques , 2018, IET Softw..

[24]  Anna Perini,et al.  Crowdsourcing for Software Engineering The Crowd in Requirements Engineering The Landscape and Challenges , 2017 .

[25]  Oscar Ljungkrantz,et al.  Organisation and communication problems in automotive requirements engineering , 2018, Requirements Engineering.

[26]  Roel Wieringa,et al.  Naming the pain in requirements engineering , 2016, Empirical Software Engineering.

[27]  Jane Cleland-Huang,et al.  What Questions do Requirements Engineers Ask? , 2017, 2017 IEEE 25th International Requirements Engineering Conference (RE).

[28]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[29]  Tomi Männistö,et al.  Challenges of requirements engineering — A case study in nuclear energy domain , 2011, 2011 IEEE 19th International Requirements Engineering Conference.

[30]  Bashar Nuseibeh,et al.  Leveraging Inconsistency in Software Development , 2000, Computer.

[31]  Maleknaz Nayebi,et al.  Data-Driven Requirements Engineering - An Update , 2019, 2019 IEEE/ACM 41st International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP).

[32]  Tony Gorschek,et al.  Quality Requirements in Industrial Practice—An Extended Interview Study at Eleven Companies , 2012, IEEE Transactions on Software Engineering.

[33]  Naveed Ikram,et al.  Empirical research in requirements engineering: trends and opportunities , 2016, Requirements Engineering.

[34]  T. Maurer Career-relevant learning and development, worker age, and beliefs about self-efficacy for development , 2001 .

[35]  Johnny Saldaña,et al.  The Coding Manual for Qualitative Researchers , 2009 .

[36]  Nisar Hussain,et al.  Requirement Elicitation Methods for Cloud Providers in IT Industry , 2018, International Journal of Modern Education and Computer Science.

[37]  Anitha S. Pillai,et al.  The Effects of Requirements Elicitation Issues on Software Project Performance: An Empirical Analysis , 2014, REFSQ.

[38]  Roel Wieringa,et al.  Quality Requirements Challenges in the Context of Large-Scale Distributed Agile: An Empirical Study , 2018, REFSQ.

[39]  Roel Wieringa,et al.  Status Quo in Requirements Engineering: A Theory and a Global Family of Surveys , 2021, Software Engineering.

[40]  Michael Felderer,et al.  On Evidence-Based Risk Management in Requirements Engineering , 2018, SWQD.

[41]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[42]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[43]  Mohamad Kassab,et al.  The changing landscape of requirements engineering practices over the past decade , 2015, 2015 IEEE Fifth International Workshop on Empirical Requirements Engineering (EmpiRE).

[44]  Stefan Wagner,et al.  Naming the pain in requirements engineering: design of a global family of surveys and first results from Germany , 2013, EASE '13.

[45]  Roel Wieringa,et al.  Status Quo in Requirements Engineering , 2018, ACM Trans. Softw. Eng. Methodol..

[46]  Axel van Lamsweerde,et al.  Requirements Engineering: From System Goals to UML Models to Software Specifications , 2009 .

[47]  Maleknaz Nayebi,et al.  Toward Data-Driven Requirements Engineering , 2016, IEEE Software.

[48]  Fei Peng,et al.  Why Requirements Engineering Fails: A Survey Report from China , 2010, 2010 18th IEEE International Requirements Engineering Conference.