Requirements Elicitation Techniques: Analyzing the Gap between Technology Availability and Technology Use

Many software development projects fail because the resulting software does not satisfy user needs. The process of determining user needs is generally termed requirements elicitation. Although there are many possible reasons for software failures, if analysts practiced more effective requirements elicitation, fewer projects would fail. Although hundreds of requirements elicitation techniques have been developed by researchers to aid analysts in effectively determining user needs, few have ever been used by practitioners. This paper reports on research to study the nature of the gap between requirements elicitation technique availability and use, identifies the major factors that impact the transfer of elicitation techniques to practice, and explores how to improve the transfer of elicitation techniques from research to practice.

[1]  Capers Jones,et al.  Patterns of Large Software Systems: Failure and Success , 1995, Computer.

[2]  Robert W. Zmud,et al.  The Effectiveness of External Information Channels in Facilitating Innovation Within Software Development Groups , 1983, MIS Q..

[3]  Alan M. Davis,et al.  Elicitation technique selection: how do experts do it? , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[4]  Richard J. Parmentier,et al.  After Tylor: British Social Anthropology 1888-1951 , 1997 .

[5]  Alan M. Davis,et al.  The Design of a Family of Application-Oriented Requirements Languages , 1982, Computer.

[6]  Geoffrey A. Moore,et al.  Crossing the Chasm , 1991 .

[7]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[8]  Capers Jones.  Why Is Technology Transfer so Hard? , 1995, Computer.

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

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

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

[12]  Tibor Kremic,et al.  Technology Transfer: A Contextual Approach , 2003 .

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

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

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

[16]  Floyd J. Fowler,et al.  Survey Research Methods , 1984 .

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

[18]  Jane Wood,et al.  Joint application development (2. ed.) , 1995 .

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

[20]  Colin Potts,et al.  Software-engineering research revisited , 1993, IEEE Software.

[21]  William E. Riddle,et al.  Software technology maturation , 1985, ICSE '85.

[22]  Laurent Bally,et al.  A prototype approach to information system design and development , 1977, Inf. Manag..

[23]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[24]  M. K. Raja,et al.  Quality function deployment usage in software development , 1996, CACM.

[25]  E. Rogers,et al.  Diffusion of Innovations , 1964 .

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

[27]  Michael A. Greiner,et al.  Barriers and Bridges for Successful Environmental Technology Transfer , 2003 .

[28]  Gerald M. Weinberg,et al.  Exploring Requirements: Quality Before Design , 1989 .

[29]  C. Eden.  BookOn systems analysis : David Berlinski 186 pages, £ 10.25 (Cambridge, Mass, and London, MIT Press, 1976)☆ , 1978 .

[30]  Capers Jones,et al.  Applied software measurement: assuring productivity and quality , 1991 .

[31]  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.

[32]  Louise A. Heslop,et al.  Development of a Technology Readiness Assessment Measure: The Cloverleaf Model of Technology Transfer , 2001 .