The KIPS Transactions:PartD (정보처리학회논문지D)

Korea Information Processing Society (한국정보처리학회)
권호 표지
DOI QR코드

DOI QR Code

Software Equation Based on Function Points

기능점수 기반 소프트웨어 공식

  • 이상운 (강릉원주대학교 멀티미디어공학과)
  • Received : 2010.03.10
  • Accepted : 2010.04.06
  • Published : 2010.10.31
Download PDF
⟨ Previous Next ⟩

Abstract

This paper proposed software equation that is relation with effort and duration based on function point (FP) software size. Existent software equation based on lines of code (LOC). LOC sees big difference according to development language and there are a lot of difficulties in software size estimation. First, considered method that change LOC to FP. But, this method is not decided definitely conversion ratio between LOC and FP by development language. Also, failed though the conversion ratio motives software formula because was not presented about specification development language. Therefore, we derived software formula directly to large project data that was developed by FP. Firstly, datas that reasonable development period is set among development projects. Secondly, FP through regression analysis about this data and effort, motived relation with FP and duration. Finally, software equation was derived from these relation. Proposed model solves application problems that LOC-based model has and has advantage that application is possible easily in business.

본 논문은 기능점수 소프트웨어 규모에 기반하여 개발노력과 일정과의 관계를 유도하는 소프트웨어 공식을 제안하였다. 기존의 소프트웨어 공식은 라인수에 기반을 두고 있다. 라인수는 개발언어에 따라 큰 차이를 보여 소프트웨어 규모 추정에 어려움이 많이 지적되고 있다. 먼저 라인수를 기능점수로 변환하는 방법을 고려하였다. 그러나 이 방법은 개발언어별로 라인수와 기능점수간 변환비율이 명확히 결정되지 않고 있고, 또한 특정 개발언어에 대해서는 변환비율이 제시되어 있지 않아 소프트웨어 공식을 유도하는데 실패하였다. 따라서 기능점수에 기반하여 개발된 대용량의 프로젝트 데이터를 대상으로 소프트웨어 공식을 직접 유도하였다. 첫 번째로 개발 프로젝트들 중에서 타당한 개발기간이 설정된 데이터들을 분류하였다. 두 번째로, 이 데이터에 대해 회귀분석을 통해 기능점수와 개발노력, 기능점수와 개발기간과의 관계를 유도하였다. 마지막으로 이들 관계로부터 소프트웨어 공식을 유도하였다. 제안된 모델은 라인수 기반의 모델이 갖고 있는 적용상 문제점들을 해결하여 실무에 쉽게 적용이 가능한 장점을 갖고 있다.

Keywords

References

  1. A. J. Shenher, “Improving PM: Linking Success Criteria to Project Type,” Project Management Institude, Creating Canadian Advantage through Project Management Symposium, Calgory, 1996.
  2. L. H. Putnam and W. Myers, "Familiar Metric Management-Time-to-Market, http://www.qsm.com/fmm_08.pdf
  3. L. H. Putnam and W. Myers, “Five Core Metrics: The Intelligence Behind Successful Software Management,” Dorset House Publishing, 2003.
  4. L. H. Putnam and W. Myers, “Measures of Excellence: Reliable Software on Time, Within Budget,” Yourdon Press, 1992.
  5. L. H. Putnam and W. Myers, “What We Have Learned,” The Journal of Defense Software Engineering, 2000.
  6. L. H. Putnam and W. Myers, “Familier Metric Management+,” http://www.qsm.com/ffmm_02.pdf
  7. J. E. Matson, B. E. Barrett and J. M. Mellichamp, “Software Development Cost Estimation Using Function Points,” IEEE Trans. on Software Eng., Vol.20, No.4, pp.275-287, 1994. https://doi.org/10.1109/32.277575
  8. C. Jones, “Programming Productivity,” New York, McGraw-Hill, 1986.
  9. G. C. Low and D. R. Jeffery, “Function Points in the Estimation and Evaluation of the Software Process,” IEEE Trans. on Software Eng., Vol.16, pp.64-71, 1990. https://doi.org/10.1109/32.44364
  10. R. D. Emrick, “In Search of a Better Metric for Measuring Productivity of Application Development,” Int. Function Point Users Group Conf. Proc., 1987.
  11. B. W. Boehm, “Software Engineering Economics,” Prentice Hall, 1981.
  12. M. Bradley, “Function Point Counting Practices Manual, Release 4.1,” International Function Point Users Group (IFPUG), 1999.
  13. C. Symons, “COSMIC-FFP Measurement Manual, Version 2.2 (The COSMIC Implementation Guide for ISO/IEC 19761: 2003),” Common Software Measurement International Consortium, 2003.
  14. ISO/IEC FDIS 19761, “Software Engineering - COSMIC - FFP - A Functional Size Measurement Method,” 2002.
  15. B. W. Boehm et al, “Software Cost Estimation with COCOMO II,” Prentice-Hall, 2000.
  16. K. Ribu, “Estimating Object-oriented Software Projects with Use Cases,” University of Oslo Department of Informatics, Master of Science Thesis, 2001.
  17. F. P. Brooks, “The Mythical Man-Month: Essays on Software Engineering,” Addison-Wesley, 1995.
  18. J. Nyman, “Metrics and Measures,” GlobalTester, TechQA, 2002.
  19. QSM, “Index Based Productivity Benchmarking,” QSM Associates, Inc. 1999.
  20. T. McGilbon, “Modern Empirical Cost & Schedule Estimation Tools,” DoD DACS Technical Reports, 1997.
  21. D, L, Hallowell, “Software Project Management Meets Six Sigma,” http://software.isixsigma.com/library/content/c030813a.asp
  22. ISBSG, “Worldwide Software Development - The Benchmark Release 8,” Victoria, Australia International Software Benchmarking Standards Group, 2004.
  23. S. J. Garg, “Software Engineering: Project Management Concepts, Software Metrics,” http://www.indyan.com/CS10.html 2003.
  24. QSM, “QSM Function Point Programming Languages Table,” Quantitative Software Management, Inc., 2002.
  25. D. Herron, “Software Sizing: There is an Easier Way,” David Consulting Group, ASM, 2002.
  26. C. Jones, “Applied Software Measurements,” McGraw Hill, 1996.
  27. T. McGilbon, “Modern Empirical Cost & Schedule Estimation Tools,” DoD DACS Technical Reports, 1997.
  28. G. Sifri, “Accurate Estimates Critical for Software Development Projects,” ESI International, Inc., 2001
  29. W. G. Cochran, “Sampling Techniques,” 3rd Edition, John Wiley & Sons, 1977.
  30. D. R. Jones, “Project Scheduling,” Augsburg College, 1999.
  31. C. Carbno, “Optimal Resource Allocation for Projects,” Project Management Journal, 1999.
  32. Y. Yang, Z. Chen, R. Valerd, and B. Boehm, “Effect of Schedule Compression on Project Effort,” 27th Annual Conference of the International Society of Parametric Analysis, Denver, Colorado, USA., 2005.
  33. C. Fakharzadeh, “CORADMO in 2001: A RAD Odyssey,” 16th International Forum on COCOMO and Software Cost Modeling, USC-CSE, 2001.
  34. B. Boehm, B. Clark, E. Horowitz, R. Modachy, R. Shelby, and C. Westland, “The COCOMO 2.0 Software Cost Estimation Model,” USC Center for Software Engineering, 1995.
  35. J. A. Ward, “Productivity Through Project Management: Controlling the Project Variables,” Information Management, 1994. https://doi.org/10.1080/10580539408964615
  36. R. Pressman, C. Jones, V. Basilli, and L. Putnam, “16 Critical Software Practices, Estimate Cost and Schedule Empirically,” http://www.iceinusa.com/16CSP/content/2-cost/anmetrgt.html, 2005.
  37. L. K. Richard, “Staff IT,” http://www.gantthead.com, 2005.
  38. M. Holtsinger, “CIS 4251/CIS 5930 Software Development,” 1999.
  39. C. Abts, A. W. Brown, S. Chulani, B. K. Clark, E. Horowitz, R. Madachy, D. Reifer, and B. Steece, “Software Cost Estimation with COCOMO II,” Prentice-Hall, 2000.
  40. Marin Consultancy, “Estimation,” Marin Solutions Technical Paper, 2001.
  41. C. Walston and C. Felix, “A Method of Programming Measurement and Estimation,” IBM Systems Journal, Vol. 16, No.1, 1977. https://doi.org/10.1147/sj.161.0054
  42. K. Johnson, “Software Cost Estimation: Metrics and Models,” Department of Computer Science, University of Calgary. 1998.