IJSER Home >> Journal >> IJSER
International Journal of Scientific and Engineering Research
ISSN Online 2229-5518
ISSN Print: 2229-5518 2    
Website: http://www.ijser.org
scirp IJSER >> Volume 2, Issue 2, February 2011
Software Process Models and Analysis on Failure of Software Development Projects
Full Text(PDF, 3000)  PP.  
Rupinder Kaur, Dr. Jyotsna Sengupta
process model, software failure rate, project failure, software development.
The software process model consists of a set of activities undertaken to design, develop and maintain software systems. A variety of software process models have been designed to structure, describe and prescribe the software development process. The software process models play a very important role in software development, so it forms the core of the software product. Software project failure is often devastating to an organization. Schedule slips, buggy releases and missing features can mean the end of the project or even financial ruin for a company. Oddly, there is disagreement over what it means for a project to fail. In this paper, discussion is done on current process models and analysis on failure of software development, which shows the need of new research.
[1] Barry Boehm, “Anchoring the Software Process”, IEEE Transaction on Software Engineering, pp. 79-82, July 1996.

[2] B.Boehm, “A Sprial Model of Software Development and Enhancement”, IEEE Computer, Volume 21, Issue 5, pp. 61-72, 1988.

[3] B.Boehm and D.Port, “Escaping the software tar pit: model clashes and how to avoid them”, Software Engineering Note, Volume 24, Issue 1, pp. 36-48, 1999.

[4] B.Boehm and P.Bose, “A Collaborative Spiral Software Process Model Based on Theory W.Processing of ICSP”, 3, New York: IEEE Press, 1994.

[5] Dan Galorath, “Software Project Failure Costs Billions-Better Estimation & Planning Can Help”, June 7, 2008.

[6] Dines Bjørner, “Role of Software Engineering in Software Development: Why Current Requirements Engineering is Flawed”, Springer, Scotland, October 2009.

[7] George Tilmann and Joshua Weinberger, “Technology never fails, but project can”, Baseline, Volume 1, Issue 26, pp 28, 2004.

[8] I. Jacobson, G. Booch, and J. Rumbaugh, “The Unified Software Development Process”, Addison-Wesley, 1999.

[9] J. Martin, “Rapid Application Development”, Prentice-Hall Publication, 1991.

[10] Joshua Kerievsky, “Industrial XP: Making XP Work in Large Organizations”, vol. 6, issue 2, Cutter Consortium Agile Product and Project Management.

[11] Kent Beck, “Extreme Programming Explain: Embrace Change”, Addison- Wesley, First Edition-1999, Second Edition- 2004.

[12] O.Nierstrasz, S. Gibbs, and D. Tsichritzis, “Component-Oriented Software Development,” CACM, vol. 35, no. 9, pp. 160–165, September 1992.

[13] Survey of System Development Process Models CTG.MFA -003, Center for Technology in Government 1998, University at Albany.

[14] Walt Scacchi, “Process Models in Software Engineering”, Institute for Software Research, University of California, Irvine, October, 2001.

[15] Watts S. Humphrey and Marc I. Kellner, “Software Process Modeling: Principles of Entity Process Models”, Technical Report, New York: ACM Press, pp. 331-342, February 1989.

Untitled Page