최소 단어 이상 선택하여야 합니다.
최대 10 단어까지만 선택 가능합니다.
다음과 같은 기능을 한번의 로그인으로 사용 할 수 있습니다.
NTIS 바로가기한국인터넷방송통신학회 논문지 = The journal of the Institute of Internet Broadcasting and Communication, v.12 no.2, 2012년, pp.233 - 241
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 ...
* AI 자동 식별 결과로 적합하지 않은 문장이 있을 수 있으니, 이용에 유의하시기 바랍니다.
핵심어 | 질문 | 논문에서 추출한 답변 |
---|---|---|
소프트웨어 개발 성공 요인인 4중 제약조건은 무슨 사항인가? | 소프트웨어 개발 성공 요인인 4중 제약조건은 모두 고객 관점에서 평가되는 사항이다. 즉, 고객이 투자한 일정과 비용내에서 고객이 요구하는 기능과 품질 수준을 만족시키는 제품을 개발하느냐 여부로 결정된다. | |
프로젝트 관리의 목표는? | 프로젝트 관리의 목표는 프로젝트를 성공하기 위함이다. 그러나 프로젝트 수행 결과가 성공이라고 명확히 판단할 수 있는가? 또한 판단 결과에 고객과 개발자 모두 동의하는가? 성공과 실패에 대한 정의와 판단 척도들에 대해 다양하게 제시되고 있으나 명확한 분류 기준이 없다. | |
프로젝트 성공 판단은 어떠한 경우 가능한가? | 그러면 프로젝트 성공을 어떻게 정의할 수 있으며, 성공하였다고 판단할 수 있는 척도는 무엇인가? 또한, 프로젝트 성공과 실패를 명확히 구분하는 기준은 존재하는가? 이 모든 관심사항에 대해 많은 연구가 수행되었지만 아직까지 명확하게 정의된 결과가 없는 실정이다. 최종적으로는 이해당사자들 (Stakeholders)인 고객 (획득자)과 개발자 (공급자) 모두 만족하였을 경우 프로젝트가 성공하였다고 판단할 수 있을 것이다. 즉, 프로젝트 개발에 투입된 비용 (Cost)과 일정 (Time)으로 고객이 원하는 제품을 개발 완료하고 이를 통해 고객은 투자이익률 (ROI, Return-On-Investment)을, 개발자는 개발 이익 (Profit)을 얻을 수 있어야 한다. |
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.
R. B. Sheridan, "Regarding Executive Sponsorship," Menlo Institute, 2005.
G. P. Kessler, "Why Technical Projects fail: Avoiding Disaster," Project Management, Vol. 1, No. 2, Elementk Journals, 2001.
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
Standish group, "The CHAOS Report," http://www.standishgroup.com/sample/PDFpages/chaos1994.pdf, 1994.
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.
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.
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.
Welcom, "PM Glossary, Project Management Solutions, Internet," Deltek Systems Inc, 1998.
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.
J. Marasco, "The Project Pyramid," http://www-128.ibm.com/developerworks/rational/library/4291.html, 2004.
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.
D. Fenny, "Managing Large Information Techno logy Projects in the Public Sector," OECD Meeting, 2000.
K. Dugardyn, "Develop High Quality e-business Applications - Test Smarter, Finish Faster," QWE, 2002.
S. K. Baker, "On Time/On Budget," Prentice Hall, Englewood Cliffs, NJ, 1992.
M. J. Hillelsohn, "Been There, Done That: Some Lessons Learned on Software Development Contracts," Software Management, 5th ed., IEEE Computer Society, 1997.
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.
E. Burris, 'Project Management," School of Interdisplinary Computing and Engineering, Univer sity of Missouri, 1984.
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.
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.
K. E. Wiegers, "Creating a Software Engineering Culture." Dorset House Publishing, 1996.
M. B. Patel and P. M. G. Morris, "Centre for Research in the Management of Projects (CRMP)," University of Manchester, UK, 1999.
Project Management (UK), "A Bridged Glossary of Project Management Terms," APMP Syllabus, 2nd Edition, 2000.
British Standard Institute (BSI), "BS6079: Standard Guide to Project Management, 1996.
R. M. Wideman, "Cost Control of Capital Projects," BiTech Publishers Ltd, Richmond, BC, Canada, 1995.
Private BC Corporation, "Project Management Guidelines," 1995.
PMI, "Project Management Body of Knowledge Glossary of Terms," Project Management Institute, 1987.
D. M. Cartwright, "Success and Failure in IT Projects," School of Design, Engineering & Computing Business Information Technology, Bournemouth University, 2004.
B. Baker, "Great Expectations: Turning Failure into Success - and Visa Versa," PM Network, pp. 25 - 28, 1997.
Standish group, "CHAOS: A Recipe for Success," http://www.standishgroup.com/sample/PDFpages/chaos1999.pdf, 1999.
Standish group, "Extreme CHAOS," http://www.sta ndishgroup. com/sample/PDFpa ges/extreme_chaos.pdf, 2001.
Standish group, "CHAOS Demographics and Project Resolution," http://www.standishgrou p.com/sample/PDFpages/ q3_spo tlight.pdf, 2004.
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.
B. Lewis, "The 70-Percent Failure," Infoworld. http:// archive.infowor ld.com/articles/op/xml /01/10/29/011029/opservival.html, 2003.
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.
D. Leffingwell, "Features, Use cases, Requirements, Oh My!," The Rational E-zine, 2000.
M. R. Hulme, "Procurement Reform and MIS Project Success", Journal of Supply Chain Management, Winter 1997; 33, 1; pg 2., 1997.
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.
Mangione, "Software Project Failure: The Reasons, The Costs," http://w ww.cioupdate.co m/reports/article.php/ 1563701, Jupitermedia Corporation, 2003.
Projectnet, "What is Project Management?," Project Management Today, 2005.
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
*원문 PDF 파일 및 링크정보가 존재하지 않을 경우 KISTI DDS 시스템에서 제공하는 원문복사서비스를 사용할 수 있습니다.
출판사/학술단체 등이 한시적으로 특별한 프로모션 또는 일정기간 경과 후 접근을 허용하여, 출판사/학술단체 등의 사이트에서 이용 가능한 논문
※ AI-Helper는 부적절한 답변을 할 수 있습니다.