DOI QR코드

DOI QR Code

Gompertz 성장곡선을 이용한 소프트웨어 프로젝트의 개발 성공률과 완료율 추정

Estimation of Software Project Success and Completion Rate Using Gompertz Growth Function

  • 이상운 (국립 원주대학 여성교양과)
  • 발행 : 2006.10.01

초록

소프트웨어 복잡도가 증가할수록 소프트웨어 성공률은 기하급수적으로 감소하며, 반대로 실패율은 증가한다. 소프트웨어 규모 증가에 따른 실패율은 성장곡선으로 표현할 수 있다. 이 현상에 따라, 본 논문은 Gompertz 성장곡선으로 개발 성공률과 완료율을 추정하였다. 먼저, 수치적으로 제시된 $10^n$의 소프트웨어 규모를 로그값으로 변환시켜 데이터 간격을 일정하게 하였다 로그값의 소프트웨어 규모 변화에 따른 개발 성공률과 완료율의 함수관계를 유도하고자 하였다. 그러나 이 관계를 적절히 표현하는 함수를 찾지 못하였다. 따라서 본 논문에서는 개발 성공률의 역 개념인 실패율과 완료율의 역 개념인 취소율을 도입하였다. 로그값의 소프트웨어 규모 변화에 따른 개발 실패율과 취소율 관계는 성장곡선 형태를 나타내었다. 결론적으로, 개발 취소율과 실패율을 적절히 표현하는 함수로 Gompertz 성장곡선을 적용한 결과 실측 데이터를 적절히 표현할 수 있었다. 본 모델을 적용하면 특정 규모의 소프트웨어에 대한 개발 성공률과 완료율을 보다 정확히 얻을 수 있을 것이다.

As the software complexity increases, the development success rate decreases and failure rate increases exponentially. The failure rate related to the software size can be described by a growth function. Based on this phenomenon, this paper estimates the development success and completion rate using the Gompertz growth function. At first, we transformed a software size of numerically suggested $10^n$ into a logarithm and kept the data interval constantly. We tried to derive a functional relationship between the development success rate and the completion rate according to the change of logarithmic software size. However, we could not find a function which can represent this relationship. Therefore, we introduced the failure rate and the cancel rate which are inverse to the development success rate and completion rate, respectively. Then, we indicated the relation between development failure rate and cancel rate based on the change of software size, as a type of growth function. Finally, as we made the Gompertz growth function with the function which describes the cancel rate and the failure rate properly. We could express the actual data suitably. When you apply the growth function model that I suggested, you will be able to get the success rate and completion rate of particular site of software very accurately.

키워드

참고문헌

  1. Standish group, 'The CHAOS Report,'http://www.standish group. com' sample/PDFpages/ chaos1994.pdf, 1994
  2. Standish group, 'CHAOS: A Recipe for Success,' http:// www.standishgroup.com/sample/PDFpages/ chaos1999.pdf, 1999
  3. Standish group, 'Extreme CHAOS,' http://www. standishgroup.com/sample/PDFpages/extreme_chaos.pdf, 2001
  4. Standish group, 'CHAOS Demographics and Project Resolution,' http://www.standishgroup.com/sample/PDFpa ges/ q3_spotlight.pdf, 2004
  5. K. Schwaber, 'Scaling Agile: It Depends on Common Sense,' CAMUG Meeting, 2003
  6. B. Lewis, 'The 70-Percent Failure,' Infoworld. http://archive. infoworld.com/ articles/op/xml/01/1 0/29/011029/opservival. html, 2003
  7. D. Garmus and D. Herron, 'Estimating Software Earlier And More Accurately,' David Consulting Group, http://www.davidconsultinggroup.com/articles/pbestart.html
  8. V. B. Misic, 'Software Size and Cost Estimation,' Department of Computer Science, University of Belgrade, 2003
  9. C. Mcphee, 'SENG 621-Software Process Management,' University of Calgary, 1999
  10. S. Sultanoglu, 'Software Measurement,' Department of Computer Science & Eng., Hacettepe University, 1998
  11. N. E. Fenton and S. L. Pfleegr, 'Software Metrics: A Rigoous and Practical Approach, 2nd Edition, PWS Publishing Company, 1997
  12. B. W. Boehm, 'Software Engineering Economics,' Prentice-Hall, 1981
  13. M. Bradley, 'Function Point Counting Practices Manual, Release 4.1,' International Function Point Users Group (IFPUG), 1999
  14. C. Symons, 'COSMIC-FFP Measurement Manual, Version 2.2 (The COSMIC Implementation Guide for ISO/IEC 19761: 2003),' Common Software Measurement International Consortium, 2003
  15. ISO/IEC FDIS 19761, 'Software Engineering- COSMICFFP-A Functional Size Measurement Method,' 2002
  16. B. W. Boehm et al, 'Software Cost Estimation with COCOMO II,' Prantice-Hall, 2000
  17. K. Ribu, 'Estimating Object-oriented Software Projects with Use Cases,' University of Oslo Department of Informatics, Master of Science Thesis, 2001
  18. J. Bach, 'SCRUM Software Development Process: Building The Best Possible Software,' Advanced development Methods, 1995
  19. C. Jones, 'Patterns of Software Systems Failure and Success,' International Thomson Press, 1996
  20. J. Capers, 'Why Flawed Software Projects Are Not Cancelled in Time,' Cutter IT Journal, Vol.16, No.12, pp.1217, 2003
  21. K. Orr, 'Pushing the Envelope: Managing Very Large Projects,' Cutter Agile Software Development & Project Management Advisory Service Executive Report, Vol.5, No.7, 2004
  22. C. Jones, 'Software Assessment, Benchmark, and Best Practices,' Information Technology Series, Addison-Wesley, 2000
  23. C. Henry, 'The Growth Curve,' http://www.anzpug.org/sp/index.jsp, PRIMA VERA Users Groups, Technology and Operations Management, California Polytechnic and State University
  24. R. Pearl, 'The Biology of Population Growth,' New York: Knopf, 1978
  25. B. Gompertz, 'On The Nature of The Function Expressive of The Law of Human Mortality, and on a New Mode of Determining the Value of Life Contingencies,' Phil. Trans. Roy. Soc. London. Vol.123, pp.513-585, 1832
  26. Weibull.com, 'Software Reliability Growth Model,' http://www.weibull.com/relgrowthwebcontents.html
  27. S. Conte, H. E. Dunsmore and V. Y. Shen, 'Software Engineering Metrics and Models,' Benjamin/Cummings., 1986