A Review of the Impact of Requirements on Software Project Development Using a Control Theoretic Model

Anthony White
DOI: 10.4236/jsea.2010.39099                

Abstract

Software projects have a low success rate in terms of reliability, meeting due dates and working within assigned budgets with only 16% of projects being considered fully successful while Capers Jones has estimated that such projects only have a success rate of 65%. Many of these failures can be attributed to changes in requirements as the project progresses. This paper reviews several System Dynamics models from the literature and analyses the model of Andersson and Karlsson, showing that this model is uncontrollable and unobservable. This leads to a number of is-sues that need to be addressed in requirements acquisition.

Keywords

Requirements Models, System Dynamics, Control Systems, Observability, Controllability

Conflicts of Interest

The authors declare no conflicts of interest.

References

[1]	J. Smith, “The 40 Root Causes of Troubled IT Projects,” Computing and Control Journals, June 2002, pp.109-112.
[2]	K. T. Yeo, “Critical Failure Factors in Information System Projects,” International Journals of Project Management, Vol. 20, 2002, pp. 241-246.
[3]	Royal Academy of Engineering, “The Challenges of Complex IT projects,” Report of working group of RAE and BCS, 2004.
[4]	The Standish Group International Inc., Standard Group CHAOS Report. 1998
[5]	The Standish Group International Inc., Standard Group CHAOS Report, 25 March 2003
[6]	T. Abdel-Hamid and S. E. Madnick, “Software Project Dynamics: An Integrated Approach,” Englewood Cliffs, Prentice Hall, New York, 1991.
[7]	C. Jones, “Large Software System Failures and Successes,” American Programmer, April 1996, pp.3-9.
[8]	L. J. May, “Major Causes of Software Project Failures,” Crosstalk, July 1998.
[9]	B. Deifel and C. Salzmann, “Requirements and Conditions for Dynamics in Evolutionary Software Systems,” Proceedings of the International Workshop on the Principles of Software Evolution, IWPSE99, Fukuoka, 1999.
[10]	C. Coulin, D. Zowghi and A. Sahraoui, “A Situational Method Engineering Approach to Requirements Elicitation Workshops in the Software Development Process,” Software Process Improvement and Practice, Vol. 11, No. 5, 2006, pp.451-465.
[11]	B. Boehm and P. N. Pappacio, “Understanding and Controlling Software Costs,” IEEE Transactions on software engineering, Vol. 14, 1988, pp.1462-1477.
[12]	J. F. Hoorn, M. E. Breuker and E. Kok, “Shifts in Foci and Priorities. Different Relevance of Requirements to Changing Goals Yields Conflicting Prioritizations and Its Viewpoint,” Software Process Improvement and Practice, Vol. 11, No. 5, 2006, pp. 465-485.
[13]	G. Kotonya and I. Sommerville, “Requirements Engineering Processes and Techniques,” Wiley, 1988.
[14]	E. Wolstenholme, “A Current Overview of System Dynamics, Transactions on Institute MC, Vol. 114, No. 4, 1989, pp. 171-179.
[15]	J. Forrester, “Industrial Dynamics,” MIT press, Boston, 1961.
[16]	R. Madachy and B. Khoshnevis, “Dynamic Simulation Modeling of an Inspection-Based Software Lifecycle Process,” Simulation, Vol. 69, No.1, 1997, pp.35-47.
[17]	T. Haberlein, “Common Structures in System Dynamics Models of Software Acquisition Projects,” Software Process Improvement and Practice, Vol. 9, No. 2, 2004, pp. 67-80.
[18]	D. Williams, “Challenges of System Dynamics to Deliver Requirements Engineering Projects: Faster, Better, Cheaper,” 21st System Dynamics Conference, New York, 2003.
[19]	C. Andersson and L. Karlsson, “A System Dynamics Simulation Study of a Software Development Process,” Lund Institute of Technology Report, March, 2001.
[20]	J. W. Cangussu, R. A. DeCarlo and A. P Mathur, A For-mal Model for the Software Test Process, IEEE Transac-tions on Software Engineering, vol. 28, no.8, August 2002, pp.782-796.
[21]	A. S. White, “Control Engineering Analysis of Software project Management,” BCS SQM Conference, Stafford, Section 3, April 2007.