Requirements: Towards an understanding on why software projects fail

Requirement engineering is at the foundation of every successful software project. There are many reasons for software project failures; however, poorly engineered requirements process contributes immensely to the reason why software projects fail. Software project failure is usually costly and risky and could also be life threatening. Projects that undermine requirements engineering suffer or are likely to suffer from failures, challenges and other attending risks. The cost of project failures and overruns when estimated is very huge. Furthermore, software project failures or overruns pose a challenge in today’s competitive market environment. It affects the company’s image, goodwill, and revenue drive and decreases the perceived satisfaction of customers and clients. In this paper, requirements engineering was discussed. Its role in software projects success was elaborated. The place of software requirements process in relation to software project failure was explored and examined. Also, project success and failure factors were also discussed with emphasis placed on requirements factors as they play a major role in software projects’ challenges, successes and failures. The paper relied on secondary data and empirical statistics to explore and examine factors responsible for the successes, challenges and failures of software projects in large, medium and small scaled software companies.

[1]  Dhirendra Pandey,et al.  REQUIREMENT ENGINEERING PARADIGM , 2014 .

[2]  Betty H. C. Cheng,et al.  Current and Future Research Directions in Requirements Engineering , 2009 .

[3]  Azham Hussain,et al.  Investigation of the current requirements engineering practices among software developers at the Universiti Utara Malaysia Information Technology (UUMIT) Centre , 2016 .

[4]  Azham Hussain,et al.  Eliciting user satisfying requirements for an e-health awareness system using Kano Model , 2015 .

[5]  Inam Abdullah Lafta.  A study of requirements engineering practices among software developers at UUM Information Technology (UUMIT) , 2015 .

[6]  Emmanuel O. C. Mkpojiogu,et al.  Understanding the relationship between Kano model’s customer satisfaction scores and self-stated requirements importance , 2016, SpringerPlus.

[7]  Gerald M. Weinberg,et al.  Exploring Requirements: Quality Before Design , 1989 .

[8]  Tejas Shah,et al.  A Review of Requirement Engineering Issues and Challenges in Various Software Development Methods , 2014 .

[9]  Azham Hussain,et al.  Assessing the influence of self-reported requirements importance on the perceived quality of proposed software products , 2018 .

[10]  Ralph Young,et al.  The requirements engineering handbook , 2003 .

[11]  Huma Hayat Khan,et al.  FACTORS GENERATING RISKS DURING REQUIREMENT ENGINEERING PROCESS IN GLOBAL SOFTWARE DEVELOPMENT ENVIRONMENT , 2014 .

[12]  Sunitha Mary Thomas.  Requirement Gathering for small Projects using Agile Methods , 2011 .

[13]  S SwarnalathaK,et al.  SOFTWARE REQUIREMENT COLLECTION ENHANCEMENT USING SAMPLING TECHNIQUE AND APPLYING T-DISTRIBUTION , 2014 .

[14]  P Morris,et al.  Why IT Projects Fail , 1997 .

[15]  Mohd Nasrun Mohd Nawi,et al.  Requirements model for an e-Health awareness portal , 2016 .

[16]  Karl E. Wiegers.  Creating a Software Engineering Culture , 1996 .

[17]  Emmanuel O. C. Mkpojiogu,et al.  Quality Based Prioritization: An Approach for Prioritizing Software Requirements , 2017 .

[18]  Santhosh Kumar Kamuni.  Study of Factors that Induce Software Project Overrun Time , 2015 .

[19]  Azham Hussain,et al.  Predicting the Perceived Worth of Software Product Requirements with Customer Satisfaction , 2017 .