SuccessFactors of Requirement Elicitation: A Comprehensive Survey
Requirements elicitation is an important phase of the requirement engineering process. A complete and accurate collection of user requirement can reach to the success of the project. This paper studied and discussed the success factors of requirements elicitation task. First, some important previous works related to the requirement elicitation process are presented. Then, the researchers extract a list of most effective success factors of the requirement elicitation. A new list of the collected success factors is proposed that includes two dimensions; success factors should be considered before beginning the requirement elicitation process, and success factors should be considered during the process.
P. Vitharana, F. Zahedi andH. K. Jain.“Enhancing Analysts’ Mental Models for Improving Requirements Elicitation: A Two-stage Theoretical Framework and Empirical Results”. Journal of the Association for Information Systems, 17(12), (2016), 1.
I.Hadar, P. Soffer and K. Kenzi. “The role of domain knowledge in requirements elicitation via interviews: an exploratory study”. Requirements Engineering, 19(2), (2014), 143-159.
F. Paetsch, A. Eberlein and F. Maurer. “Requirements engineering and agile software development”. In Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003. WET ICE (2003). Proceedings. Twelfth IEEE International Workshops on (pp. 308-313). IEEE.
D. Zowghi andC. Coulin. Requirements elicitation: A survey of techniques, approaches, and tools. In Engineering and managing software requirements, (2005), (pp. 19-46). Springer Berlin Heidelberg.
C. Rosenkranz, H. Vranesic andR. Holten. “Boundary interactions and motors of change in requirements elicitation: a dynamic perspective on knowledge sharing”. Journal of the Association for Information Systems, 15(6),(2014), 306.
S. Chakraborty, S. Sarker andS. Sarker. “An exploration into the process of requirements elicitation: A grounded approach”. Journal of the Association for Information Systems, 11(4),(2010), 212-249.
M. Maguire and N. Bevan. User requirements analysis. In Usability , (2002) , (pp. 133-148). Springer US.s
G. J. Browne and M. B. Rogich. “An empirical investigation of user requirements elicitation: Comparing the effectiveness of prompting techniques”. Journal of Management Information Systems, 17(4), (2001),223-249.
H. F. Hofmann and F. Lehner. “Requirements engineering as a success factor in software projects”. IEEE software, 18(4), (2001), 58.
J. Verner, K. Cox, S. Bleistein and N. Cerpa. “Requirements engineering and software project success: an industrial survey in Australia and the US”. Australasian Journal of information systems,13(1),(2005).
G.B. Davis.“Strategies for information requirements determination”. IBM Systems Journal, 21, 1(1982), 4-3
W.Stacy, and J. Macmillan. “Cognitive bias in software engineering”. Communications of the ACM, 38, 6 (1995), 57-6
J.R. Valusek and D.G. Fryback.“Information requirements determination: obstacles within, among and between participants”. In R. Galliers (ed.), Information Analysis: Selected Readings. Reading, MA: Addison Wesley, (1987), pp 139 -151.
B. Nuseibeh and S. Easterbrook. “Requirements Engineering: A Roadmap”.Proceedings of the Conference on The Future of Software Engineering, (2000), pp. 35 -46, Limerick, Ire land.
G.J. Browne, S. P. Curleyand P. G.Benson. “Evoking information in probability assessment: knowledge maps and reasoning-based directed questions”. Management Science, 43, 1 (1997), 1-14.
Nagy R. Darwish and S. Megahed. “Requirements Engineering in Scrum Framework”. Requirements Engineering, 149(8), (2016). 24-29.
H. E.Elsherbeiny, A. A. El-Aziz, and Nagy R. Darwish, “A Survey on Attempts to Enhance Requirements Engineering Process”. Software Engineering and Technology, 8(6), (2016).135-139.
- There are currently no refbacks.
This work is licensed under a Creative Commons Attribution 3.0 License.