Effective Requirements Development-A Comparison of Requirements Elicitation techniques

Requirements engineering process is a human endeavor. People who hold a stake in a project are involved in the requirements engineering process. They are from different backgrounds and with different organizational and individual goals, social positions, and personalities. They have different ways to understand and express the knowledge, and communicate with others. The requirements development processes, therefore, vary widely depending on the people involved. In order to acquire quality requirements from different people, a large number of methods exit. However, because of the inadequate understanding about methods and the variability of the situations in which requirements are developed, it is difficult for organizations to identify a set of appropriate methods to develop requirements in a structured and systematic way. The insufficient requirements engineering process forms one important factor that cause the failure of an IT project [29].

[1]  Enid Mumford,et al.  A participative approach to forward planning and system change , 1978, ECI.

[2]  David W. Conrath,et al.  The Use of Cognitive Mapping for Information Requirements Analysis , 1986, MIS Q..

[3]  E. Hippel,et al.  Lead users: a source of novel product concepts , 1986 .

[4]  George Wright,et al.  Eliciting and modelling expert knowledge , 1987, Decision Support Systems.

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

[6]  Kyo Chul Kang,et al.  CMU / SEI-92-TR-0 12 ESC-TR-92-012 Issues in Requirements Elicitation , 1992 .

[7]  Joseph A. Goguen,et al.  Techniques for requirements elicitation , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[8]  Karen Holtzblatt,et al.  Making customer-centered design work for teams , 1993, CACM.

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

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

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

[12]  Galal H. Galal-Edeen,et al.  Stakeholder identification in the requirements engineering process , 1999, Proceedings. Tenth International Workshop on Database and Expert Systems Applications. DEXA 99.

[13]  Jay F. Nunamaker,et al.  Establishing a foundation for collaborative scenario elicitation , 1999, DATB.

[14]  Ian Sommerville,et al.  Social analysis in the requirements engineering process: from ethnography to method , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[15]  Michael D. Myers,et al.  Investigating Information Systems with Ethnographic Research , 1999, Commun. Assoc. Inf. Syst..

[16]  Jacob L. Cybulski,et al.  Requirements Classification and Reuse: Crossing Domain Boundaries , 2000, ICSR.

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

[18]  William N. Robinson,et al.  Reuse of scenario specifications using an automated relational learner: a lightweight approach , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[19]  Mary Beth Rosson,et al.  Effectiveness of elicitation techniques in distributed requirements engineering , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[20]  Georgios A. Dafoulas,et al.  Investigating Cultural Differences in Virtual Software Teams , 2002, Electron. J. Inf. Syst. Dev. Ctries..

[21]  Gordon Rugg,et al.  Eliciting information about organizational culture via laddering , 2002, Inf. Syst. J..

[22]  Barbara Paech,et al.  Systematic requirements recycling through abstraction and traceability , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[23]  Dean Leffingwell,et al.  Managing Software Requirements: A Use Case Approach , 2003 .