Measuring Requirements Complexity to Increase the Probability of Project Success

The widespread adoption of Information Technology has helped reduce market problems caused by geographical separation and allow collaboration between organisations who are physically distributed around the globe. However, despite the successful strategic benefits brought by the evolution of the Internet and other web based services, this has not led to a higher project success rate. The biggest reason for project failure is cited as ‘incomplete requirements’ which suggests that research must be done into the requirements analysis to solve this reoccurring problem. This paper aims to highlight and analyse the current work done in the software complexity and requirements engineering field and demonstrate how measuring requirements complexity will lead to less project failures.

[1]  Ellis Horowitz,et al.  Software Cost Estimation with COCOMO II , 2000 .

[2]  Chris F. Kemerer,et al.  A Metrics Suite for Object Oriented Design , 2015, IEEE Trans. Software Eng..

[3]  Joseph A. Goguen,et al.  Techniques for requirements elicitation , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[4]  Kecheng Liu Semiotics in Information Systems Engineering: LEGOL applications in the CRIS case , 2000 .

[5]  Hans van Vliet,et al.  Two case studies in measuring software maintenance effort , 1998, Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272).

[6]  Michael J. Prietula,et al.  Software-Effort Estimation: An Exploratory Study of Expert Performance , 1991, Inf. Syst. Res..

[7]  Richard E. Fairley Making Accurate Estimates , 2002, IEEE Softw..

[8]  Sarah Jane Delany,et al.  The Limits of CBR in Software Project Estimation , 1998 .

[9]  Karen Holtzblatt,et al.  Requirements gathering: the human factor , 1995, CACM.

[10]  H. Simon,et al.  Making Management Decisions: the Role of Intuition and Emotion , 1987 .