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

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

DOI QR Code

A Predictive Model for Software Development Team Size and Duration Based on Function Point

기능점수 기반 소프트웨어 개발팀 규모와 개발기간 예측 모델

  • 박석규 (강원도립대학 컴퓨터응용과) ;
  • 이상운 (강원도립대학 컴퓨터응용과)
  • Published : 2003.12.01
Download PDF
⟨ Previous Next ⟩

Abstract

Estimation of software project cost, effort and duration in the early stage of software development cycle is a difficult and key problem in software engineering. Most of models estimate the development effort using the function point that is measured from the requirement specification. This paper presents optimal team size and duration prediction based on function point in order to provide information that can be used as a guide in selecting the most Practical and productive team size for a software development project. We introduce to productive metrics and cost for decision criteria of ideal team size and duration. The experimental is based on the analysis of 300 development and enhancement software project data. These data sets are divide in two subgroups. One is a development project; the other is a maintenance project. As a result of evaluation by productivity and cost measured criteria in two subgroups, we come to the conclusion that the most successful projects has small teams and minimum duration. Also, I proposed that predictive model for team sire and duration according to function point size based on experimental results. The presented models gives a criteria for necessary team site and duration according to the software size.

소프트웨어 개발 초기에 개발비용, 소요 인력과 기간을 추정하는 것은 소프트웨어공학 분야의 주요한 요소이며, 어려운 문제이다. 소프트웨어 개발 소요 인력을 추정하기 위한 대부분의 모델들은 소프트웨어 요구사항 명세서로부터 측정된 기능점수를 이용하였다. 본 논문은 기능점수에 기반하여 프로젝트에 대한 가장 실제적이고 생산적인 팀 규모와 개발기간을 선택하는 지침으로 사용될 수 있는 정보를 제공하기 위해 생산성 척도와 비용 척도를 도입하였다. 소프트웨어 개발과 유지보수를 수행한 300개 프로젝트 데이터 집합을 2개의 서브 그룹인 개발 프로젝트와 유지보수 프로젝트로 분류하였다. 생산성과 비용 측도 기준에 의해 분석한 결과 작은 팀 규모와 최소한의 개발기간이 소요되었을 때, 프로젝트가 성공적으로 수행됨을 보였다. 또한, 연구 결과에 근거하여 기능점수 규모에 따른 개발팀의 규모와 개발기간을 추정할 수 있는 모델을 제안하였다. 본 제안 모델은 소프트웨어 규모에 따라 필요한 개발팀의 규모와 개발기간 평가 기준을 제공한다.

Keywords

References

  1. L. J. Arthur, 'Measuring Programmer Productivity and Software Quality,' New York, Jon Wiley, 1985
  2. K. H. Moller and D. J. Paulish, 'Software Metrics-A Practitioners Guide to Improved Product Development,' Chapman & Hall Co., New York, 1993
  3. B. A. Kitchenham, 'Empirical Studies of Assumptions That Underlie Software Cost-estimation Models,' Information and Software Technology, Vol.34, No.4, pp.211-218, 1992 https://doi.org/10.1016/0950-5849(92)90077-3
  4. S. Oligny, P. Bourque and A. Abran, 'An Empirical Assessment of Project Duration Models in Software Engineering,' In The Eight European Software Control and Metrics Conferene (ESCOM'97), Berlin Germany, 1997
  5. S. Oligny, P. Bourque, A. Abran and B. Fournier, 'Exploring the Relation Between Effort and Duration in Software Engineering Projects,' World Computer Congress 2000, Beijing, China, pp.175-178, August, 2000
  6. ISBSG, 'Worldwide Software Development - The Bench - mark Release 4,' Vicoria, Australia International Software Benchmarking Standards Group, 1997
  7. P. C. Semprevivo, 'Teams in Information Systems Development,' Yordon, p.85, 1980
  8. L. H. Putnam, 'A General Empirical Solution to the Macro Software Sizing and Estimationg Problem,' IEEE Trans. on Software Eng., Vol.SE-4, No.4, 1978
  9. ISBSG, 'Worldwide Software Development - The Bench - mark Release 6,' Vicoria, Australia International Software Benchmarking Standards Group, 2000
  10. D. V. Ferens, B. A. Daly, 'A Comparison of software Scheduling Methods,' In Reifer D. ed. Software Management. 4th ed. Washington : IEEE Computer Society Press, 1993
  11. B. A. Kitchenham, 'Empirical Studies of Assumptions That Underlie Software cost-estimation Models,' Information and Software Technology, Vol.34, No.4, pp.211-218, 1992 https://doi.org/10.1016/0950-5849(92)90077-3
  12. C. Jones, 'Determining Software Schedules,' Computer, Vol.28, No.2, pp.73-75, 1995 https://doi.org/10.1109/2.348003
  13. R. E. Park, W. B. Goethert and J. T. Webb, 'Software Cost and Schedule Estimating : A Process Improvement Initiative,' Pittsburgh, PA Software Engineering Institute, 1994
  14. 'Six, not the Ideal Project Team Size,' A Weekly Column on software Design, http://www.sum-it.nl/en199947.html, 1999
  15. 이상운, '소프트웨어 개발팀 규모 추정 모델,' 한국정보과학회논문지B, 제29권 제12호, pp.873-882, 2002
  16. 이상운, 박중양, 박재흥, '개발과 유지보수 프로젝트의 이상적인 팀 규모,' 정보처리학회논문지D, 제10-D권 제1호, pp.77-84, 2003 https://doi.org/10.3745/KIPSTD.2003.10D.1.077
  17. K. Pillai, V. S. sukumaran Nair, 'A Model for software Development Effort and Cost Estimation,' IEEE Trans. on Software Engineering, Vol.23, No.8, pp.485-497, 1997 https://doi.org/10.1109/32.624305
  18. L. C. Briand and I. Wieczorek, 'Resource Estimation in Software Engineering,' International Software Engineering Research Network, Technical Report, ISERN 00-05, 2000
  19. A. Abran, C. Symons and S. Oligny, 'An Overview of COSMIC-FFP Field Trial Results,' ESCOM 2001, London, England, 2001
  20. L. C. Briand, K. E. Elmam, D. Surmann, I. Wieczork and K. D. Maxwell, 'An Assessment and Comparision of Common Software Cost Estimation Modeling Techniques,' International Software Engineering Research Network, Technical Reprot, ISERN-98-27, 1998