Browse > Article
http://dx.doi.org/10.7236/JIWIT.2012.12.2.233

A Definition and Evaluation Criteria for Software Development Success  

Lee, Sang-Un (Dept. of Multimedia Engineering, Gangnung-Wonju National University(Wonju Campus))
Choi, Myeong-Bok (Dept. of Multimedia Engineering, Gangnung-Wonju National University(Wonju Campus))
Publication Information
The Journal of the Institute of Internet, Broadcasting and Communication / v.12, no.2, 2012 , pp. 233-241 More about this Journal
Abstract
The object of the project management is to succeed in the project. However, could you definitely judge that the result of project performance is a success? In addition, do both customer and developer agree with the result of your judgement? There are a lot of definitions and measure for the success and failure of the software development suggested, but there is no definite standard for the classification. This paper examines the measures in order to decide the development success and re-defines the success and the failure of the project. We suggest the measure and the standard that judge the project achievement based on these definitions. Applying the suggested measure and standard, it is possible to reduce arguments between the customer and the developer on the classification of the success and the failure.
Keywords
Success and Failure; Success Measures; Project Constraints; Return-on-investment; Development Profit;
Citations & Related Records
Times Cited By KSCI : 2  (Citation Analysis)
연도 인용수 순위
1 J. Marasco, "Software Development Productivity and Project Success Rates: Are We Attacking the Right Problem?," http://www-128.ibm.com/ developerworks/rational/ library/feb06 /marasco/in dex.html, 2006.
2 R. B. Sheridan, "Regarding Executive Sponsorship," Menlo Institute, 2005.
3 G. P. Kessler, "Why Technical Projects fail: Avoiding Disaster," Project Management, Vol. 1, No. 2, Elementk Journals, 2001.
4 R. M. Wideman, "Progressive Acquisition and the RUP Part II: Contracts That Work," The Rational Edge E-zine on-line magazine, 2003, http://www.maxwideman.com/papers/ acquisition/overview.htm
5 Standish group, "The CHAOS Report," http://www.standishgroup.com/sample/PDFpages/chaos1994.pdf, 1994.
6 R. Frese and V. Sauter, "Project Success and Failure: What is Success, What is Failure, and How Can You Improve Your Odds for Success?," http://www.umsl.edu/-sauter/analy sis/6840_f03_papers/frese/, 2003.
7 J. Johnson, K. D., Boucher, K. Connors, and J. Robinson, "Collaboration: Development & Manage ment: Collaborating on Project Success," http://www.SOFT WAREMAG.COM/ ARCHIVE/2001FEB/Collaborativemgt.html, Software Magazine and Wiesner Publishing, 2001.
8 K. R. Linberg, "Software developer perceptions about software project failure: a case study," The Journal of Systems and Software, Elsevier, www.lelsevier.com/locate/ jss, 1999.
9 Welcom, "PM Glossary, Project Management Solutions, Internet," Deltek Systems Inc, 1998.
10 R. Atkinson, "Project management: cost, time and quality, tow best guesses and a phenomenon, its time to accept other success criteria," International Journal of Project Management, Elsevier Science Ltd and IPMA, vol17, No 6, pp 337-342, 1999.   DOI   ScienceOn
11 J. Marasco, "The Project Pyramid," http://www-128.ibm.com/developerworks/rational/library/4291.html, 2004.
12 S. Keogh, "What is Success and Failures in Computing," http://computin g.unn.ac.uk/staff/cglh1/balck hole of lost resource s.doc, School of Informatics, 2001.
13 D. Fenny, "Managing Large Information Techno logy Projects in the Public Sector," OECD Meeting, 2000.
14 K. Dugardyn, "Develop High Quality e-business Applications - Test Smarter, Finish Faster," QWE, 2002.
15 S. K. Baker, "On Time/On Budget," Prentice Hall, Englewood Cliffs, NJ, 1992.
16 M. J. Hillelsohn, "Been There, Done That: Some Lessons Learned on Software Development Contracts," Software Management, 5th ed., IEEE Computer Society, 1997.
17 D. F. Redmiles, "UC IRVINE - ICS 121 Software Tools and Methods," Department of Information and Computer Science, University of California, http://www.ics.uci.edu/ -redm iles/ics121-FQ99/lecture/one/sld001.htm, 1999.
18 E. Burris, 'Project Management," School of Interdisplinary Computing and Engineering, Univer sity of Missouri, 1984.
19 J. Marasco, "The Project Pyramid," The Rational Edge E-zine on-line magazine, http://www-128.ibm.com/ developerw orks/ration al/library/4291.html, 2004.
20 R. M. Wideman, "Progressive Acquisition and the RUP Part I: Defining the Problem and Common Terminology," The Rational Edge E-zine on-line magazine, http://www. maxwideman.com/pap ers/acquisition/intro.htm, 2002.
21 K. E. Wiegers, "Creating a Software Engineering Culture." Dorset House Publishing, 1996.
22 M. B. Patel and P. M. G. Morris, "Centre for Research in the Management of Projects (CRMP)," University of Manchester, UK, 1999.
23 Project Management (UK), "A Bridged Glossary of Project Management Terms," APMP Syllabus, 2nd Edition, 2000.
24 British Standard Institute (BSI), "BS6079: Standard Guide to Project Management, 1996.
25 R. M. Wideman, "Cost Control of Capital Projects," BiTech Publishers Ltd, Richmond, BC, Canada, 1995.
26 B. Baker, "Great Expectations: Turning Failure into Success - and Visa Versa," PM Network, pp. 25 - 28, 1997.
27 Private BC Corporation, "Project Management Guidelines," 1995.
28 PMI, "Project Management Body of Knowledge Glossary of Terms," Project Management Institute, 1987.
29 D. M. Cartwright, "Success and Failure in IT Projects," School of Design, Engineering & Computing Business Information Technology, Bournemouth University, 2004.
30 Standish group, "CHAOS: A Recipe for Success," http://www.standishgroup.com/sample/PDFpages/chaos1999.pdf, 1999.
31 Standish group, "Extreme CHAOS," http://www.sta ndishgroup. com/sample/PDFpa ges/extreme_chaos.pdf, 2001.
32 Standish group, "CHAOS Demographics and Project Resolution," http://www.standishgrou p.com/sample/PDFpages/ q3_spo tlight.pdf, 2004.
33 R. Frese and V. Sauter, 'Project Success and Failure: What is Success, What is Failure, and How can You Improve Your Odds for Success?," http://www.umsl.edu/ -sauter/a nalysis/6840_f03_papers/frese/, 2003.
34 B. Lewis, "The 70-Percent Failure," Infoworld. http:// archive.infowor ld.com/articles/op/xml /01/10/29/011029/opservival.html, 2003.
35 A. J. Shenhar and J. J. Renier, "Improving PM: Linking Success Criteria to Project Type," Southern Alberta Chapter, Project Management Institute, Symposium "Creating Canadian Advantage Through Project Management", Calgary, 1996.
36 D. Leffingwell, "Features, Use cases, Requirements, Oh My!," The Rational E-zine, 2000.
37 M. R. Hulme, "Procurement Reform and MIS Project Success", Journal of Supply Chain Management, Winter 1997; 33, 1; pg 2., 1997.
38 Projectnet, "What is Project Management?," Project Management Today, 2005.
39 S. Gurlen, "Scope Creep," IS 6840-Information Systems Analysis Section G01 Syllabus, University of Missouri, http://www.ums l.edu/-sauter/a nalysis/6840_f03_papers/gurlen/, 2003.
40 Mangione, "Software Project Failure: The Reasons, The Costs," http://w ww.cioupdate.co m/reports/article.php/ 1563701, Jupitermedia Corporation, 2003.
41 Sang-Won Kang, Pyung-Hyung Park, Hae-Sool Ynag "Security Quality Measurement Model of M-Commerce software" Proceedings of the KAIS Fall Conference, pp.789-792, 2009
42 Suk-Hee Kim1, Jong-Hun Kim "The Development of an easy a simple of Parameter Estimation Method for Reliability Evaluation of Application Software System"Journal of the Korea Academia-Industrial Cooperation Society, v.11, no.2, pp.540-549, 2010   DOI
43 Dae-Soung Kim, Hee-Cheul Kim2 "The Study of Software Reliability Model from the Perspective of Learning Effects for Burr Distribution" Journal of the Korea Academia-Industrial Cooperation Society, v.12, no.10, pp.4543-4549, 2011   DOI   ScienceOn