Call for Paper - April 2023 Edition
IJCA solicits original research papers for the April 2023 Edition. Last date of manuscript submission is March 20, 2023. Read More

Managing Risks in the System Analysis and Requirements Definition Phase

International Journal of Computer Applications
© 2014 by IJCA Journal
Volume 99 - Number 3
Year of Publication: 2014
Shihadeh Alqrainy
Haneen Hijazi

Shihadeh Alqrainy and Haneen Hijazi. Article: Managing Risks in the System Analysis and Requirements Definition Phase. International Journal of Computer Applications 99(3):23-29, August 2014. Full text available. BibTeX

	author = {Shihadeh Alqrainy and Haneen Hijazi},
	title = {Article: Managing Risks in the System Analysis and Requirements Definition Phase},
	journal = {International Journal of Computer Applications},
	year = {2014},
	volume = {99},
	number = {3},
	pages = {23-29},
	month = {August},
	note = {Full text available}


System analysis and requirements definition is a risky phase. It is susceptible to different types of risk factors from the initial preliminary investigation till the final delivery of the requirements document. Risks reside in this phase are considered the ones with the highest severity among other phases. Being the first phase in the development process, the occurrence of risks in this phase negatively influences subsequent phases, affects project progress, and has a negative impact on the project outcomes. Thus, managing probable risks in this phase deadly helps project managers control the majority of risks that might arise later in the subsequent phase. In order to manage risks properly, probable risks need to be identified early, then, risk management strategies have to be proposed and followed in order to avoid and mitigate their occurrence. In this paper, a total number of 28 risk factors have been introduced. For each risk factor, a set of management strategies is proposed. The identified factors and strategies were the harvest of brainstorming sessions with senior software practitioners, comprehensive literature survey, plus ready-made checklist and taxonomies. In order to validate our results, correlation analysis had been conducted through a web-based survey. The results confirmed our assumptions in that all of the identified risk factors have positive correlation with project failure.


  • Harry J. Systems Analysis and Design. 10th. Boston : Rosenblatt, (2014).
  • I, Sommerville. Software Engineering. 9th. USA : Addison Wesley, (2011).
  • K. E. Wiegers. Software Requirements. 2nd. Washington : Microsoft Press, (2003).
  • Board for Software Standardisation and Control. Guide to the user requirements definition. ESA, 1995.
  • H. Hijazi, S. Alqrainy, H. Muaidi, and T. Khdour. Risk Factors in Software Development Phases. European Scientific Journal, Vol. 10, No. 3, pp. 213-232, (2014).
  • J. Dhlamini, I. Nhamu, and A. Kachepa, Intelligent Risk Management Tools for Software Development. Proceedings of the 2009 Annual Conference of the Southern African Computer. pp. 33-40, (2009) June 29-July 1. Eastern Cape, South Africa.
  • J. Miler and J. Górski. Risk-driven Software Process Improvement - A Case Study. Proceedings of the 11th European Software Process Improvement Conference. (2004) November 10-12. Trondheim, Norway.
  • S. Zardari . Software Risk Management. Proceedings of the 3rd International Conference on Information Management and Engineering. pp. 375-379. (2009). Kuala Lumpur, Malaysia.
  • B. Shahzad, and S. A. Safvi. Risk Mitigation and Managemen Scheme based on Risk Priority. Global Journal of Computer Science and Technology, Vol. 10, No. 4, pp. 108-113, (2010).
  • M. Keil, P. E. Clue, K. Lyytinen, and R. S. Schmidt. A framework for Identifying Software Project Risks. Communications of the ACM, Vol. 41, No. 11, pp. 76-83, (1998).
  • T. Addison and S. Vallabh. Controlling Software Project Risks: An Empirical Study of Methods used by Experienced Project Managers. Proceedings of SAICSIT. pp. 128-140. (2002) September 16-18. South Africa
  • B. Shahzad and J. Iqbal. Software Risk Management Prioritization of Frequently Occurring Risk in Software Development Phases using Relative Impact Risk Model. Proceedings 2nd International Conference on Information and Communication Technology. pp. 110-115. (2007) December 16-17. IBA, Karchi.
  • B. Shahzad, A. S. Al-Mudimigh. Ullah. Risk Identification and Preemptive Scheduling in Software Development Life Cycle. Global Journal of Computer Science and Technology, Vol. 10, No. 2, pp. 55-63, (2010).
  • B. Shahzad and S. A. Safvi. Effective Risk Mitigation: A User Prospective. International Journal of Mathematics and Computers In Simulation, Vol. 2, No. 1, pp. 70-80, (2008).
  • B. Shahzad, I. Ullah, and N. Khan. Software Risk Identification and Mitigation in Incremental Model. Proceedings of the International Conference on Information and Multimedia Technology. pp. 366-370. (2009) December 16-18. Jeju Island, Korea.
  • BIBLIOGRAPHY l 1033 Cherry, K. (n. d. ). Correlational Studies. Retrieved May 25, 2014, http://psychology. about. com/od/researchmethods/a/correlational. htm
  • Islam, Sh. Software Development Risk Management Model – agoal – driven approach. Phd thesis. Technische Universit Munchen : Germany, (2011).