Elicitation technique selection: how do experts do it?

Requirements elicitation techniques are methods used by analysts to determine the needs of customers and users, so that systems can be built with a high probability of satisfying those needs. Analysts with extensive experience seem to be more successful than less experienced analysts in uncovering the user needs. Less experienced analysts often select a technique based on one of two reasons: (a) it is the only one they know, or (b) they think that a technique that worked well last time must surely be appropriate this time. We present the results of in-depth interviews with some of the world's most experienced analysts. These results demonstrate how they select elicitation techniques based on a variety of situational assessments.

[1]  Barry Bozeman.  Handbook of Interview Research: Context and Method , 2003 .

[2]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[3]  Valdis Berzins,et al.  Software prototyping , 2003 .

[4]  J. Daniel Couger,et al.  Evolution of Business System Analysis Techniques , 1973, CSUR.

[5]  T. Oko.  Interviewing as Qualitative Research: A Guide for Researchers in Education and the Social Sciences. , 1992 .

[6]  C. P. Goodman,et al.  The Tacit Dimension , 2003 .

[7]  Denise Silver,et al.  Joint Application Development , 1995 .

[8]  T. M. Rajkumar,et al.  Comparison of analysis techniques for information requirement determination , 1988, CACM.

[9]  Neil A. M. Maiden,et al.  ACRE: selecting methods for requirements acquisition , 1996, Softw. Eng. J..

[10]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .

[11]  Lawrence D. Pohlmann,et al.  Requirements By Collaboration , 2003 .

[12]  Alan M. Davis,et al.  Software requirements - analysis and specification , 1990 .

[13]  Alan M. Davis,et al.  Requirements elicitation and elicitation technique selection: model for two knowledge-intensive software development processes , 2003, 36th Annual Hawaii International Conference on System Sciences, 2003. Proceedings of the.

[14]  James Martin,et al.  Object-oriented analysis and design , 1992 .

[15]  Grant Mccracken.  The long interview , 1988 .

[16]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[18]  Roger Gates,et al.  Marketing Research Essentials , 1995 .

[19]  Alan M. Davis,et al.  Operational prototyping: a new development approach , 1992, IEEE Software.

[20]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[21]  Alan M. Davis,et al.  A Tale of Two Ontologies: The Basis for Systems Analysis Technique Selection , 2003, AMCIS.

[22]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[23]  Eva Hudlicka,et al.  Requirements elicitation with indirect knowledge elicitation techniques: comparison of three methods , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[24]  Robert L. Glass.  Searching for the holy grail of software engineering , 2002, CACM.

[25]  Jan van Dijk,et al.  Searching for the Holy Grail: Images of Interactive Television , 2001, New Media Soc..

[26]  Robert W. Zmud,et al.  A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques , 1992, MIS Q..

[27]  Gretchen B. Rossman,et al.  Designing qualitative research, 3rd ed. , 1999 .

[28]  Eugene Miya,et al.  On "Software engineering" , 1985, SOEN.

[29]  Mark Billinghurst,et al.  Crossing the Chasm , 2001 .

[30]  A. Berztiss,et al.  Requirements Engineering , 2002, J. Object Technol..

[31]  Edward Yourdon,et al.  Object-oriented analysis , 2012 .

[32]  Kathryn L. Heninger.  Specifying Software Requirements for Complex Systems: New Techniques and Their Application , 2001, IEEE Transactions on Software Engineering.

[33]  S. Lauesen.  Software Requirements Styles and Techniques , 2001 .

[34]  Jean-Marc Nerson,et al.  Object-Oriented Analysis and Design , 1992, TOOLS.

[35]  Peter P. Chen.  The entity-relationship model: toward a unified view of data , 1975, VLDB '75.

[36]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[37]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[38]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[39]  Alan M. Davis.  A taxonomy for the early stages of the software development life cycle , 1988, J. Syst. Softw..

[40]  Barbara Farbey,et al.  Exploring Requirements: Quality Before Design , 1991 .

[41]  Alan M. Davis,et al.  Software Prototyping , 1995, Adv. Comput..

[42]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[43]  D.R. Chand,et al.  Essential systems analysis , 1986, Proceedings of the IEEE.

[44]  Douglas T. Ross,et al.  Structured Analysis (SA): A Language for Communicating Ideas , 1977, IEEE Transactions on Software Engineering.