Framework for matching requirements elicitation techniques to project characteristics

One of the most difficult jobs for requirements engineers is to select an appropriate RE method for the project at hand. Good engineers make good choices and have skills in applying selected techniques appropriately. Poor engineers usually have a narrow choice range limited by their training and biased by their experience. Once a RE technique that does not fit the current project is selected, the project is doomed to fail. In this article, we propose a framework to characterize typical RE techniques and use it as a base for selecting appropriate techniques at the time a project is started, as well as at the time a change in the nature of the project is recognized, or an obstacle is encountered in defining a suitable set of requirements. Copyright © 2006 John Wiley & Sons, Ltd.

[1]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

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

[3]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.

[4]  Gordon B. Davis,et al.  Determining information requirements: A contingency method for selection of a requirements assurance strategy , 1984, J. Syst. Softw..

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

[6]  Bashar Nuseibeh,et al.  An Abductive Approach for Analysing Event-Based Requirements Specifications , 2002, ICLP.

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

[8]  Alan Padula.  Requirements engineering process selection at Hewlett-Packard , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[9]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

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

[11]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[12]  Gloria Mark,et al.  In situ requirements analysis: a deeper examination of the relationship between requirements determination and project selection , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[13]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[14]  Karl Cox,et al.  Requirements Engineering and Software Project Success: an industrial survey in Australia and the U.S , 2005, Australas. J. Inf. Syst..

[15]  Toshihiko Tsumaki.  Requirements engineering pattern structure , 2004, 11th Asia-Pacific Software Engineering Conference.

[16]  Rubén Prieto-Díaz,et al.  Domain analysis: an introduction , 1990, SOEN.

[17]  Teade Punter,et al.  The MEMA-model: towards a new approach for Method Engineering , 1996, Inf. Softw. Technol..

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

[19]  H. Holbrook,et al.  A scenario-based methodology for conducting requirements elicitation , 1990, SOEN.

[20]  Colette Rolland,et al.  Guiding Goal Modeling Using Scenarios , 1998, IEEE Trans. Software Eng..

[21]  Kyo Chul Kang,et al.  Issues in Requirements Elicitation , 1992 .

[22]  Henri Briand,et al.  An approach based on the concept of use case to produce dynamic object-oriented specifications , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

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

[24]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[25]  Daan B. B. Rijsenbrij,et al.  Flexibilization of the methodology of system development , 1995, Inf. Softw. Technol..

[26]  James M. Neighbors,et al.  The Draco Approach to Constructing Software from Reusable Components , 1984, IEEE Transactions on Software Engineering.

[27]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[28]  Michael A. Jackson,et al.  Problem Frames - Analysing and Structuring Software Development Problems , 2000 .