Requirement elicitation: identifying the communication challenges between developer and customer

Eliciting requirements for a system is an important activity in requirement engineering. This process occur at the early stages in system development which involves communication between customers and developers. Researchers have identified that poor communication is one of the most common problem in identifying and defining customer’s requirements. This problem will contribute to bad result e.g. poor system, failure of the system and budget overruns. The communication is challenging and difficult as this process also includes cognitive aspect, personalities, techniques and tools. A study was carried out to explore the communication challenges that are faced by developers and customers during software requirement elicitation in Malaysia. The results of this study had shown that there are some important communication challenges during software requirements elicitation process in Malaysia. In addition, most of the practitioners were pursuing the practices that have been traditionally used by the organizations. Consequently, the results of this study have given us a good incentive to expand our research in the area of software requirements elicitation.

[1]  Francisca Losavio,et al.  Identifying Quality-Based Requirements , 2003, Inf. Syst. Manag..

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

[3]  Robert M. Hayes,et al.  Systems analysis and design , 1970, ACM '70.

[4]  Wei-Tek Tsai,et al.  Approach and case study of requirement analysis where end users take an active role , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

[5]  A.E.K. Sahraoui,et al.  Towards a collaborative and combinational approach to requirements elicitation within a systems engineering framework , 2005, 18th International Conference on Systems Engineering (ICSEng'05).

[6]  Stefan Biffl,et al.  Integrating Collaborative Processes and Quality Assurance Techniques: Experiences from Requirements Negotiation , 2004, J. Manag. Inf. Syst..

[7]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[8]  Joseph A. DeVito,et al.  Communicology: An introduction to the study of communication , 1978 .

[9]  서정목,et al.  문화적 차이에 따른 Business Communication , 1996 .

[10]  Phillip V. Lewis.  Organizational Communication: The Essence Of Effective Management , 1975 .

[11]  Harold Kerzner,et al.  SUMMER 2011 TEXTBOOKS EM 536 Project Management Project Management: A System Approach to Planning, Scheduling, and Controlling , 2011 .

[12]  Venkataraman Ramesh,et al.  Improving information requirements determination: a cognitive perspective , 2002, Inf. Manag..

[13]  Scot Ober,et al.  Contemporary Business Communication , 1991 .

[14]  Alan M. Davis,et al.  A Unified Model of Requirements Elicitation , 2004, J. Manag. Inf. Syst..

[15]  Jay F. Nunamaker,et al.  Setting a foundation for collaborative scenario elicitation , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[16]  Starr Roxanne Hiltz,et al.  An exploratory comparison of four modes of communication for determining requirements: results on creativity, quality and satisfaction , 1997, Proceedings of the Thirtieth Hawaii International Conference on System Sciences.

[17]  Joey F. George,et al.  Modern Systems Analysis and Design , 1996 .

[18]  Paul Grünbacher,et al.  Tool Support for Distributed Requirements Negotiation , 2003 .

[19]  Cathy Urquhart,et al.  Analysts and clients in conversation: cases in early requirements gathering , 1998, ICIS '98.

[20]  Frank Maurer,et al.  Requirements engineering and agile software development , 2003, WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003..

[21]  Joey F. George,et al.  Modern Systems Analysis and Design (4th Edition) , 2004 .

[22]  Claes Wohlin,et al.  Engineering and Managing Software Requirements , 2005 .