Impact of Requirements Elicitation Processes on Success of Information System Development Projects

Open access

Abstract

Requirements articulating user needs and corresponding to enterprise business processes are a key to successful implementation of information system development projects. However, the parties involved in projects frequently are not able to agree on a common development vision and have difficulties expressing their needs. Several industry experts have acknowledged that requirements elicitation is one of the most difficult tasks in development projects. This study investigates the impact of requirements elicitation processes on project outcomes depending on the applied project development methodology.

[1] H. Liao, “Requirement elicitation of Enterprise Informationization from view of VCA,” in INC2010: 6th International Conference on Networked Computing, Gyeongju, Korea (South), 2010, pp. 390-395.

[2] R. Stanley and L. Uden, “Why projects fail, from the perspective of service science”, 7th International Conference on Knowledge Management in Organizations: Service and Cloud Computing, (Advances in Intelligent Systems and Computing). Berlin, Germany: Springer, vol. 172, 2013, pp. 421-429. https://doi.org/10.1007/978-3-642-30867-3_38

[3] A. Przybyłek, “A business-oriented approach to Requirements Elicitation,” in ENASE 2014 - Proceedings of the 9th International Conference on Evaluation of Novel Approaches to Software Engineering, 2014, pp. 152-163.

[4] S. Liu, B. Wu and Q. Meng, “Critical affecting factors of IT project management,” in ICIII 2012 - Proceeding of 2012 International Conference on Information Management, Innovation Management and Industrial Engineering, Sanya, 2012, pp. 494-497. https://doi.org/10.1109/ICIII.2012.6339710

[5] I. Attarzadeh and H. O. Siew, “Project management practices: Success versus failure,” in ITSim 2008 - Proceedings of International Symposium on Information Technology 2008, Kuala Lumpur, 2008, pp. 1-8. https://doi.org/10.1109/itsim.2008.4631634

[6] C. P. Noraini and M. Z. Abdullah, “Requirement elicitation: identifying the communication challenges between developer and customer,” International Journal on New Computer Architectures and Their Applications, pp. 371-383, 2011.

[7] B. R. Shubhamangala, L. M. Rao, A. Dakshinamurthy and C. G. L. Singh, “Ability based domain specific training: A pragmatic solution to poor requirement engineering in CMM level 5 companies,” in CSAE 2012 - Proceedings, 2012 IEEE International Conference on Computer Science and Automation Engineering, Zhangjiajie, 2012, pp. 459-464. https://doi.org/10.1109/CSAE.2012.6272993

[8] The Standish Group, CHAOS Report, 2014. [Online]. Available: https://www.versionone.com/assets/img/files/CHAOSManifesto2013.pdf

[9] A. Azadegan, K. N. Papamichail and P. Sampaio, “Applying collaborative process design to user requirements elicitation: A case study,” Computers in Industry, pp. 798-812, Sept. 2013. https://doi.org/10.1016/j.compind.2013.05.001

[10] G. Stepanek, “Software project secrets: Why software projects fail,” in Software Project Secrets: Why Software Projects Fail, pp. 1-166, 2005. https://doi.org/10.1007/978-1-4302-0055-0

[11] D. Siahaan and F. Irhamni, “Advanced methodology for requirements engineering technique solution (AMRETS),” International Journal of Advancements in Computing Technology, vol. 4, issue 5, pp. 75-80, March 2012.

[12] E. Colonese, “Agile: The human factors as the weakest link in the chain,” Proceedings of 4th International Conference in Software Engineering for Defence Applications (Advances in Intelligent Systems and Computing). pp. 59-73, 2016. https://doi.org/10.1007/978-3-319-27896-4_6

[13] Shams-Ul-Arif, Q. Khan, S. A. K. Gahyyur, “Requirements engineering processes, tools/technologies, & methodologies,” International Journal of Reviews in Computing, pp. 41-56, 2009-2010.

[14] S. N. Kumari and A. S. Pillai, “Requirements elicitation issues and project performance: A test of a contingency model,” in SAI 2015 - Proceedings of the 2015 Science and Information Conference, London, 2015, pp. 889-896. https://doi.org/10.1109/sai.2015.7237247

[15] M. Yousuf and M. Asger, “Comparison of various requirements elicitation techniques,” International Journal of Computer Applications, vol. 116, issue 4, pp. 8-15, Apr. 2015. https://doi.org/10.5120/20322-2408

[16] C. Mauger, T. Schwartz, J.-Y. Dantan and L. Harbouche, “Improving users satisfaction by using requirements engineering approaches in the conceptual phase of construction projects: The elicitation process,” in IEEM2010 - IEEE International Conference on Industrial Engineering and Engineering Management, Macao, 2010, pp. 310-314. https://doi.org/10.1109/IEEM.2010.5674471

[17] S. Tiwari, S. S. Rathore and A. Gupta, “Selecting requirement elicitation techniques for software projects,” in CONSEG 2012 - 2012 CSI 6th International Conference on Software Engineering, Indore, 2012, pp. 1-10. https://doi.org/10.1109/conseg.2012.6349486

[18] W. J. Lloyd, M. B. Rosson and J. D. Arthur, “Effectiveness of elicitation techniques in distributed requirements engineering", Proceedings of the IEEE International Conference on Requirements Engineering, 2002, pp. 311-318. https://doi.org/10.1109/ICRE.2002.1048544

[19] S. G. Gunda, “Requirements engineering: elicitation techniques,” M.S. thesis, Department of Technology, Mathematics and Computer Science, University West, Sweden, 2008.

[20] W. Helmy, A. Kamel and O. Hegazy, “An evaluation framework for requirements elicitation in Agile methods,” ICSEA 2012 - The Seventh International Conference on Software Engineering Advances, Lispon, Portugal, 2012, pp. 588-593.

[21] S. Balaji and M. S. Murugaiyan, “Waterfall vs v-model vs agile: a comparative study on sdlc,” International Journal of Information Technology and Business Management, vol. 2, no. 1, pp. 26-30, June 2012.

[22] Forrester Research, The Root of The Problem: Poor Requirements, 2006. [Online]. Available: http://www.techworld.com/resources/white-paper/itmanagement/root-problem-poor-requirements-5104/

[23] D. Duka, “Agile experiences in software development,” MIPRO 2012 -35th International Convention on Information and Communication Technology, Electronics and Microelectronics - Proceedings, Opatija, 2012, pp. 692-697.

[24] M. Hasanzadeh, Z. Tavakolirad and P. Abbasi, “Review of affective factors on cost, time and quality of construction projects in developing countries,” ICEMMS 2011 - Proceedings: 2011 2nd IEEE International Conference on Emergency Management and Management Sciences, Beijing, 2011, pp. 858-861. https://doi.org/10.1109/icemms.2011.6015818

[25] B. Davey and C. Cope, “Requirements elicitation - what’s missing?” Issues in Informing Science and Information Technology- vol. 5, pp. 543-551, 2008.

[26] Project Management Institute 2014, PMI’s Pulse of the Profession: Requirements Management - A Core Competency for Project and Program Success. [Online]. Available: http://www.pmi.org/learning/pulse.aspx

[27] S. Sheppard, “The Principles of Product Development FLOW: Second Generation Lean Product Development,” 2016. [Online]. Available: http://labs.blogs.com/its_alive_in_the_lab/2016/04/book-the-principlesof-product-development-flow-second-generation-lean-productdevelopment-by-donald.html

Information Technology and Management Science

The Journal of Riga Technical University

Journal Information

Metrics

All Time Past Year Past 30 Days
Abstract Views 0 0 0
Full Text Views 161 161 52
PDF Downloads 111 111 50