摘要
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.
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.