DOI QR코드

DOI QR Code

소프트웨어 개발 라이프사이클 인력 프로파일

A Software Manpower Profile for Software Development Life Cycle

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

초록

성공적인 프로젝트 계획은 프로젝트를 개발하는데 요구되는 인력을 얼마나 정확히 추정하느냐에 달려있다. 이 정보들은 Putnam의 Rayleigh 모델이나 Phillai et al.의 Gamma 모델들로 부터 유도된다. 그러나 이들 모델들은 투입 인력이 지수적으로 계속적으로 증가하여 개발이 종료되는 시점에서 투입되는 인력이 절정에 도달하는 소프트웨어 생명주기 전체에 대한 인력분포를 대상으로 하고 있다. 그러나 실제 프로젝트에서는 대부분의 인력이 개발에 투입되고 단지 적은 규모의 인력만이 유지보수에 할당된다. 또한, 대표적인 개발 프로세스인 폭포수 모델이나 단일화된 프로세스도 개발단계만을 대상으로 하고 있다 이러한 개발환경에는 개발완료시점에서 절정에 도달하는 기존 인력분포 모델의 투입인력 분포 곡선을 적용할 수 없다 본 논문은 이러한 문제점을 해결하기 위해 개발단계에 적합한 인력분포 모델을 제시한다. 먼저, Putnam이 제시한 인력분포로부터 폭포수 모델의 개발단계 투입 인력 분포를 유도하고, 다음으로, 단일화된 프로세스에 대한 개발단계 투입인력 분포를 유도하였다. 두 프로세스 투입인력을 비교한 결과 개발 각 시점에 대한 투입인력의 양, 수행 업무 단계는 차이가 발생하지만 총 투입 인력분포는 유사한 형태를 나타내었다. 이 결과로부터 두 개발 프로세스 모두에 적용할 수 있는 단일화된 개발인력 분포 모델을 유도하였다.

Successful project planning relies on a good estimation of the manpower required to complete a project. The good estimation can be derived from Rutnam's Rayleigh Model or Phillai et al.'s Gamma Model. These models only can be applied for the projects which the need of manpower is increased exponentially and the highest of manpower is required at the end of development phase. However, in a practical project, most manpower is required during development phase and a small amount of manpower is assigned during maintenance phase. In addition, the Waterfall Model and Unified Process only can be adopted for development phase. So the current development environments cannot be adopted into the existing manpower distribution models which the highest manpower is required at the end of development phase. This paper suggests an appropriate model for development phase to solve this problem. First, the appropriate manpower distribution for development phase of the Waterfall model was derived from Putnam's manpower distribution and then manpower distribution of development phase was derived for Unified Process. After comparing the required manpower of two Processes, total manpower distribution is similar each other even though the required manpower and task is different for each point of development phase. From this result, a unified model is derived and it can be applied for both development processes.

키워드

참고문헌

  1. J. Verner and G. Tate, 'A Software Size Model,' IEEE Trans. on Software Eng., Vol.18, No.4, pp.265-278, 1992 https://doi.org/10.1109/32.129216
  2. 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
  3. KRM, 'Project Management Glossary,' Key Results Management, Inc., 2004
  4. L. H. Putnam, 'A General Empirical Solution to the Macro Software Sizing and Estimating Problem,' IEEE Trans. on Software Eng., Vol.SE-4, No.4, 1978 https://doi.org/10.1109/TSE.1978.231521
  5. K. Pillai and V. S. Sukumaran Nair, 'A Model for Software Development Effort and Cost Estimation,' IEEE Trans. on Software Eng., Vol.23, No.8, pp.485-497, 1997 https://doi.org/10.1109/32.624305
  6. J. Lattanze, 'Managing Software Development: The Software Development Lifecycles,' Carnegie Mellon University School of Computer Science, Pittsburge, 2000
  7. P. Noe, 'The Unified Software Development Process,' San Antonio SPIN, 2000
  8. P. Kruchten, 'Software Maintenance Cycles with the RUP,' http://www.therationaledge.com/content/ aug_01/LsoftwareMaintenance_pk.html
  9. G. T. Heineman and W. T. Councill, 'Component-Based Software Engineering - Putting the Pieces Together,' Addison-Wesley, 2001
  10. P. Kruchten, Going Over the Waterfall with the RUP, http://www.therationaledge.comlcontent/sep_01/t_waterfall_pk.html
  11. W. Royce, 'The Rational Unified Process : A Commercially Available Spiral Model lmplementation,' http:www. sei.cmu.edul cbs/spiral2000/february2000/Royce/
  12. B. W. Boehm, 'Software Engineering Economics,' Prentice Hall, 1981
  13. P. V. Norden, 'Curve Fitting for a Model of Applied Research and Development Scheduling,' IBM J Research and Development, Vol.3, No.2, pp.232-248, 1958
  14. P. V. Norden, 'Project Life Cycle Modeling: Background and Application of the Life Cycle Curves,' U. S. Army Computer System Command, 1977
  15. R. D. H. Warburton, 'Managing and Predicting the Costs of Real-Time Software,' IEEE Trans. on Software Eng., Vol.SE-9, No.5, pp.562-569, 1983 https://doi.org/10.1109/TSE.1983.235115
  16. A Rational Software Corporation White Paper, 'Rational Unified Process : Best Practices for Software Development earns,' Rational Software Corporation, 1998
  17. P. Kruchten, 'Planning an Iterative Project,' The Rational Edge e-zine for the Rational Community, http://www.therationaledge.com/content/oct_02/f_iterativePlanning-pk.jsp, Oct., 2002
  18. Mejias, 'Project Management Overview,' http://www.enterprise-works.com/ProjMgmt.html, Enterprise-Works.com, 2001
  19. DSW Group, 'The Software Estimation Story,' http://ww w.dswgroup.com/html/reference/SoftwareEst.html, 2003
  20. M. T. Hargan, H. B. Demuth and M. Beale, 'Neural Network Design,' PWS Publishing Company, 1996
  21. http://users.computerweekly.net/robmorton/projects/neural/sogmoid.html
  22. Y. Thoma, K. Tokunaga, S. Nagase and Y. Murata, 'Structural Approach to the Estimation of the Number of Residual Software Faults Based on the Hyper-Geometric Distribution,' IEEE Trans. on Software Eng., Vol.15, No.3, pp.345-355, 1989 https://doi.org/10.1109/32.21762
  23. Y. Thoma and K. Tokunaga, 'A Model for Estimating the Number of Software Faults,' Inst. Electron. Commun. Eng., (IECE) Japan. Tech. Rep., FTS 86-14, pp.41-46, 1986
  24. Y. Tohma, R. Jacoby, Y. Murata and M. Yamamoto, 'Hyper-Geometric Distribution Model to Estimate the Number of Residual Software Faults,' COMPSAC 89, Orland, Florida, pp.610-617, 1989 https://doi.org/10.1109/CMPSAC.1989.65155
  25. J. D. Musa, A. lannino and K. Okumoto, 'Software Reliability Measurement, Prediction, Application,' McGraw-Hill Book Company, 1987