NASA's TReK project: a case study in using the spiral model of software development

Software development projects face numerous challenges that threaten their successful completion. Whether it is not enough money, too little time, or a case of "requirements creep" that turns into a full sprint, projects must meet these challenges or face possible disastrous consequences. The funds needed to purchase supporting software tools or computing hardware may not be available, or they may be available for so short a period that informed purchase decisions become infeasible. Personnel resources are often limited, and it is difficult to adjust to personnel fluctuations during the project. The composition of the team personnel also offers potential challenges. A new software development team may begin with some members unfamiliar with the software development environment and project tools, and their learning curve can affect early productivity.

[1]  W. W. Royce,et al.  Managing the development of large software systems: concepts and techniques , 1987, ICSE '87.

[2]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[3]  Barry Boehm,et al.  A collaborative spiral software process model based on Theory W , 1994, Proceedings of the Third International Conference on the Software Process. Applying the Software Process.

[4]  Robert Plant,et al.  A survey of current practice in aerospace software development , 1995, Inf. Softw. Technol..

[5]  Barry W. Boehm,et al.  Using the WinWin Spiral Model: A Case Study , 1998, Computer.

[6]  Paolo Nesi,et al.  Managing OO Projects Better , 1998, IEEE Softw..