Achieving Effective Communication during Requirements Elicitation - A Conceptual Framework

Requirements elicitation is one of the most important and critical phase in software development. It is the moment in which the users’ needs of a software system are captured, understood and validated. This is achieved through two-way communications between users and requirement analysts. The process however is not so straightforward to accomplish. The problem of poor communication among requirement analysts and users exists since both parties are different in many ways besides the environment in which the process happens. They face significant challenges to achieve common understandings and agreements on requirements. This paper discusses the contributing factors that affect communications between both parties during requirements elicitation phase. The factors were identified through reviews of related work. The data were analysed through content analysis. The collated factors form a conceptual framework of effective communication activity for requirements elicitation process. The aim of the framework is to ensure the produced requirements are comprehensible and thus leads to the production of a software system that satisfies its intended users.

[1]  Mark Lycett,et al.  Communication issues in requirements elicitation: a content analysis of stakeholder experiences , 2003, Inf. Softw. Technol..

[2]  Gary Klein,et al.  Communication skills importance and proficiency: perception differences between IS staff and IS users , 2005, Int. J. Inf. Manag..

[3]  Seyed Hadi Mirisaee,et al.  Combining Use Case Diagram and Integrated Definition's IDEFO — A preliminary study , 2010, The 2nd International Conference on Software Engineering and Data Mining.

[4]  Marcos R. S. Borges,et al.  A Collaborative Approach to Requirements Elicitation , 2007, 2007 11th International Conference on Computer Supported Cooperative Work in Design.

[5]  Ivan A. Garcia,et al.  Effectiveness of Stakeholder Identification Methods in Requirements Elicitation: Experimental Results Derived from a Methodical Review , 2009, 2009 Eighth IEEE/ACIS International Conference on Computer and Information Science.

[6]  Sabrina Ahmad.  Negotiation in the Requirements Elicitation and Analysis Process , 2008 .

[7]  R. Weber.  Basic Content Analysis , 1986 .

[8]  Robert D. Macredie,et al.  The assessment of usability of electronic shopping: A heuristic evaluation , 2005, Int. J. Inf. Manag..

[9]  Jacob L. Cybulski,et al.  Requirements Engineering for Web-Based Information Systems , 2005 .

[10]  Hossein Saiedian,et al.  Requirements engineering: making the connection between the software developer and customer , 2000, Inf. Softw. Technol..

[11]  Theresa Beaubouef,et al.  The sometimes harsh reality of real world computer science projects , 2010, INROADS.

[12]  Austen Rainer,et al.  the neglected technical skill? , 2007, SIGMIS CPR '07.

[13]  Steven Hornik,et al.  Communication skills of IS providers: an expectation gap analysis from three stakeholder perspectives , 2003 .

[14]  John A. van der Poll,et al.  Towards a Methodology to Elicit Tacit Domain Knowledge from Users , 2007 .

[15]  Theerasak Thanasankit,et al.  Cultural Context and its Impact on Requirements Elicitation in Thailand , 2000, Electron. J. Inf. Syst. Dev. Ctries..

[16]  E. Mirza,et al.  Requirement elicitation barriers to software industry of Pakistan (impact of cultural and soft issues) , 2010, 2010 IEEE International Conference on Management of Innovation & Technology.

[17]  Abdul Azim Abdul Ghani,et al.  Adoption of Requirements Engineering Practices in Malaysian Software Development Companies , 2010, FGIT-ASEA.

[18]  Colin F. Snook,et al.  Comprehensibility of UML-based formal model: a series of controlled experiments , 2007, WEASELTech '07.

[19]  Marcos R. S. Borges,et al.  Athena: A collaborative approach to requirements elicitation , 2009, Comput. Ind..

[20]  Jorge J. Gómez-Sanz,et al.  Understanding the human context in requirements elicitation , 2010, Requirements Engineering.

[21]  Giuseppe Scanniello,et al.  Assessing communication media richness in requirements negotiation , 2010, IET Softw..

[22]  Colin F. Snook,et al.  Experimental Comparison of the Comprehensibility of a UML-based Formal Specification versus a Textual One , 2007, EASE.

[23]  Saonee Sarker,et al.  An Exploration into the Process of Requirements Elicitation: A Grounded Approach , 2010, J. Assoc. Inf. Syst..

[24]  Hui Zhang,et al.  Research on Knowledge Creation in Software Requirement Development , 2010, J. Softw. Eng. Appl..

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

[26]  LeMai Nguyen,et al.  Understanding Problem Solving in Requirements Engineering: Debating Creativity with IS Practitioners , 2003, PACIS.

[27]  Steve Easterbrook,et al.  Communication Problems in Requirements Engineering: A Field Study , 1996 .

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

[29]  David Tuffley.  Exploring the IT-User Gap: towards developing communication strategies , 2005 .

[30]  Monica Chiarini Tremblay,et al.  Communication Challenges in Requirements Elicitation and the Use of the Repertory Grid Technique , 2006, J. Comput. Inf. Syst..

[31]  Noraini Che Pa,et al.  Measuring communication gap in software requirements elicitation process , 2009, ICSE 2009.

[32]  Ian Sommerville,et al.  Requirements engineering with viewpoints , 1996, Softw. Eng. J..

[33]  Cathy Urquhart,et al.  Analysts and clients in organisational contexts: a conversational perspective , 2001, J. Strateg. Inf. Syst..

[34]  Jacob L. Cybulski,et al.  Consensus Making in Requirements Negotiation: the communication perspective , 2005, Australas. J. Inf. Syst..

[35]  Adriano Bessa Albuquerque,et al.  Relevant Skills to Requirement Analysts According to the Literature and the Project Managers Perspective , 2010, 2010 Seventh International Conference on the Quality of Information and Communications Technology.

[36]  Gary Klein,et al.  User and developer common knowledge: Effect on the success of information system development projects , 2009 .

[37]  Deniss Kumlander.  Communication gaps and requirements uncertainties in the information systems design , 2006 .

[38]  Richard L. Gissel.  Information system requirements determination: Factors impeding stakeholders from reaching common understandings and agreements on requirements , 2010 .